Ranter
Join devRant
Do all the things like
++ or -- rants, post your own rants, comment on others' rants and build your customized dev avatar
Sign Up
Pipeless API
From the creators of devRant, Pipeless lets you power real-time personalized recommendations and activity feeds using a simple API
Learn More
Comments
-
Voxera113886yAt least 90 % thinking or reading or discussing.
There are bursts of writing when there is a clear goal but planning pays of in the long run many times over. -
dmoa4196yFor me it used to be 90-10, but know I’ve made a real effort to take my time. Before, I used to just vomit into my editor mindlessly, and just go through the bugs one by one until it works. Now, thinking about it before hand, the proportion of code that works correctly first try is much higher.
I would say now 60-40 -
depends on what i'm doing.
some easy many times before done thing in relative isolation from most other stuff? can be even 100% writing because i manage the thinking fully in parallel as there isn't much of it.
some actually interesting challenging thing with numerous future implications for how the whole system is built?
sometimes i step away from thr computer and just draw and think and then delete previous 2 hours of work and start typing over, when i get back, and sometimes this repeats several times until i arrive at a solution/approach that clicks, and then i'm back to the first mode. -
vangelis256yLast project I broke record for think-coding ratio. And it was my best project ever !! I would propably say 40% thinking , 60 % coding !
Related Rants
When coding, what percentage of your time is spent fluently typing your code vs thinking about what you're coding?
question
time
focus
fluent
coding