Tech Industry
6h
1599
Are tech workers as rich as they think we are?
Tech Industry
4h
1015
How can my idiot brother who does real estate afford this
World Conflicts
Yesterday
514
Remember folks, all Israel wants is the hostages back
Today I Learned
Yesterday
999
My understanding of the Holocaust was incorrect!
Health & Wellness
Yesterday
2192
I hate my f***** life
Incremental coding or blindly coding everything at once.
Option A, but also write unit tests.
I also like bouncing ideas off people I respect over lunch before digging in so they’re not confused and even feel some ownership when it’s code review time.
Write code, compile once. Done. My code never has bugs and is self documenting. I just write it and it works.
Sometimes to challenge myself I write code like 10110110110101101010101101011000111011111100010010101111011000101001... To make my code as efficient as possible.
Depends on build time. If I'm waiting an hour for my build to complete I'm writing way more between compile. There should be a third option in this poll for write one line of code at a time and see what it does. That's the true option for I don't know what I'm doing.
The question is what do leetcoders do? I heard every problem needs to be memorized so you never have to worry about anything other than FIRE.
I've seen experienced developers do both
I tend towards option A, but sometimes the minimal viable piece of code is quite large.