4 ms·
I've found, in recently returning to writing software as the main role, that I spend more time thinking about what to write and maybe doodling out some diagram-
by matt_s 9y ago
I've found, in recently returning to writing software as the main role, that I spend more time thinking about what to write and maybe doodling out some diagram-like pictures then actually typing characters.
Now that may be different if you are starting a greenfield project or banging out a prototype.
There are a lot of repetitive things we do, which can drain your brain, and like any other job you are also likely doing the work for a company/someone else which means they define what it is you are building/fixing. So make sure you are motivated to be a professional about programming. That means being able to grind through the "this is just like that other thing, but slightly different enough that I can't re-use that other thing", etc.
- codefined 9y agoThe reason I became a programmer was to not have a repetitive lifestyle and I think it's pretty easy to accomplish that. I always have new problems to solve which require new techniques to be used and anything that gets done repetitively? Just automate it. Although I do completely agree that about 90% of my work is actually thinking about how to implement a problem as opposed to actually implementing it. If you're rewriting tens of functions that are almost identical, you should probably consider finding a different way of organising your code (even if there are minor differences between the functions).
- matt_s 9y agoI was more referring to the repetitive nature of CRUD apps and how work sort of repeats at a high level but details are different enough that it feels a little repetitive. Also keeping tests isolated tends to lead to repetition since you don't really want dependencies there.