←back to thread

Software development topics I've changed my mind on

(chriskiehl.com)
873 points belter | 2 comments | 05 Feb 25 09:50 UTC | HN request time: 0s | source
Show context
ZaoLahma ◴[05 Feb 25 12:38 UTC] No.42947654[source]▶
> Most programming should be done long before a single line of code is written

Nah.

I (16+ years developer) prefer to iteratively go between coding and designing. It happens way too often that when you're coding, you stumble across something that makes you go "oh f me, that would NEVER work", which forces you to approach a problem entirely differently.

Quite often you also have eureka moments with better solutions that just would not have happened unless you had code in front of you, which again makes you approach the problem entirely differently.

replies(16): >>42947849 #>>42948402 #>>42948536 #>>42948683 #>>42948786 #>>42949252 #>>42949429 #>>42949588 #>>42950167 #>>42950238 #>>42950409 #>>42953785 #>>42955243 #>>42956358 #>>42957524 #>>42964457 #
davidw ◴[05 Feb 25 14:53 UTC] No.42949252[source]▶
Yeah, the other stuff seems sensible or at least "Ok, I can see that", but I definitely disagree with this one.

You should spend time thinking about stuff beforehand, sure, but getting your hands dirty is also going to reveal things.

replies(1): >>42949302 #
1. pinoy420 ◴[05 Feb 25 14:56 UTC] No.42949302[source]▶
Very surprised at this attitude.

Or am I. The typical engineering savant omniscient to all future past and present engineering roadblocks fixed by “Just”(TM) thinking about it beforehand. I expect this from bay area mid level not someone with credentials.

Strange because I agree with so much more of the article

replies(1): >>42949827 #
2. davidw ◴[05 Feb 25 15:27 UTC] No.42949827[source]▶
TBH, I think it's more of a 'manager' attitude. A lot of actual "hacker" type people are very much in the "rough consensus and working code" category where you see what works by doing it.