I got two lines of code done today, and they were just changing numeric defines. Time to do that: 2 seconds.

Time for analysing the measurement data of various runs in order to know which numbers will work out: the rest of the day.

Nice

Me: writing a fuck ton of boilerplate 😫

This is the one thing that I truly do LOVE about my side of the field.

"Is Al busy??" - they walk to my office, see 3 screens with a bunch of HTML.

"Oh shit that is lots of code, he really must be busy"

Win

Feel like the comments section missed the point. Or I'm interpreting wrong. But I've been thinking this lately too. Especially when I maintain old codebases a lot of the time is actually spent on analysis of the whole system and actual code changes can be as few as 2-3 lines.

@AlgoRythm I definitely got the gist of it but kinda deviated from the main point

Mea culpa

1 hour to implement feature and 1 day to make tests coverage and Rubocop shut up.

That's life.