I appreciate the sentiment, but "There is no stupid code" is the dumbest sentence I've ever read.
[deleted]
Go ahead, write the “stupid” code
11–20 of 157 posts
Re: Go ahead, write the “stupid” code
#12The Kernighan law says debugging code is twice as hard as creating it.
Therefore, if you push yourself to the limit of your abilities to create the most clever code you can, you won't be able to debug it.
Re: Go ahead, write the “stupid” code
#13> Fast forward to today. I’ve been doing a dive on JavaScript/TypeScript and different runtimes like NodeJS and Deno, That's why. If all codes in a project are stupid, there's no stupid code indeed relatively. Go read Linux kernel mailing list.
And reading the Linux kernel mailing list would allow him to... do what exactly? And by when? Compared to writing simple, working, usable apps in TypeScript, immediately after reading about how Deno/TypeScript/etc. work?
Re: Go ahead, write the “stupid” code
#14Where did you study games? Seems like we have similar trajectories.
Re: Go ahead, write the “stupid” code
#15I appreciate the sentiment, but "There is no stupid code" is the dumbest sentence I've ever read.
[deleted]
Re: Go ahead, write the “stupid” code
#16I appreciate the sentiment, but "There is no stupid code" is the dumbest sentence I've ever read.
I think the people who think there is no stupid code don't actually ever witness truly bad code. The worst code that they come across is, at worst, below average. And since that's the worst they see, it gets mentally defined as bad.
Re: Go ahead, write the “stupid” code
#17I appreciate the sentiment, but "There is no stupid code" is the dumbest sentence I've ever read.
Maybe you don't read much, but it's obvious they weren't making some universal statement about code. They are referring to the code you write when you are just experimenting by yourself, for yourself. The point is to not let irrelevant things like usefulness, quality, conventions, etc. limit just tinkering and learning.
Re: Go ahead, write the “stupid” code
#18I appreciate the sentiment, but "There is no stupid code" is the dumbest sentence I've ever read.
I think the people who think there is no stupid code don't actually ever witness truly bad code. The worst code that they come across is, at worst, below average. And since that's the worst they see, it gets mentally defined as bad.
That’s a charitable interpretation. The other more pessimistic one is that they only see stupid code, which cannot be made any stupider.
Re: Go ahead, write the “stupid” code
#19The Kernighan law says debugging code is twice as hard as creating it. Therefore, if you push yourself to the limit of your abilities to create the most clever code you can, you won't be able to debug it.
> The Kernighan law says debugging code is twice as hard as creating it.
> Therefore, if you push yourself to the limit of your abilities to create the most clever code you can, you won't be able to debug it.
If only advocates of LLM-based code generation understood this lemma.
Re: Go ahead, write the “stupid” code
#20> Fast forward to today. I’ve been doing a dive on JavaScript/TypeScript and different runtimes like NodeJS and Deno, That's why. If all codes in a project are stupid, there's no stupid code indeed relatively. Go read Linux kernel mailing list.
And reading the Linux kernel mailing list would allow him to... do what exactly? And by when? Compared to writing simple, working, usable apps in TypeScript, immediately after reading about how Deno/TypeScript/etc. work?
It would allow him to brutally roast anyone who submits a sub-optimal merge request.