4 ms·

I disagree on principle. Readability is not even close to the top of the list of why I want the code running on my systems to be "clean". Clean software demonst

I disagree on principle. Readability is not even close to the top of the list of why I want the code running on my systems to be "clean". Clean software demonstrates good faith by the developers and a competent, ground up understanding of the problem I am trying to tackle by running your software. Clean, to me, means the code is generally not doing more than it has to, resulting in lower attack surface, better performance, lower power usage and thus less environmental impact at scale, and just a tighter, more sensible, reasonable, easy to understand user experience. Maybe this doesn't matter much at your job, which seems to be where they're trying to replace people with these parrots, but it matters a lot on your computer, and it matters even more the other three billion computers.

a456463 9mo ago
YAASS!! Readability is not the only reason to write maintainable, refactorable code that will not page you in the middle of the night with customers complaining about unknown bugs This is the dumbest take that the author wants to believe and is stating it like fact and arguably exposes that author knows so little about reliable maintainable software
- robot-wrangler 9mo ago
  The conclusion perfectly and concisely states the straw-man: > If your job is only to write beautiful code, you have a problem. Definitely no one at senior or even mid thinks this is what their job is about. Something like modularity is beautiful because it works and because of what it enables.. we don't try to shove it into place because it's beautiful. Talking about it the other way around sounds like a manager who does not understand engineering trying to paraphrase stuff that engineers are saying, poorly. Indeed quoting from this self-described entrepreneur's "About Me" page: > While I was there, I took a couple computer science courses, decided I was terrible at it and swore to never write software again. I guess that's thought-leadership for you.
  - falloutx 9mo ago
    Yeah, I think good code allows modularity and future development without turning into frankenstein's monster . Readability isn't the main goal, but future adaptability is. Also a big issue with AI imo is: It allows people to write who stopped writing code ages ago because they think they somehow can work at higher level.

a456463 9mo ago

YAASS!! Readability is not the only reason to write maintainable, refactorable code that will not page you in the middle of the night with customers complaining about unknown bugs This is the dumbest take that the author wants to believe and is stating it like fact and arguably exposes that author knows so little about reliable maintainable software

robot-wrangler 9mo ago
The conclusion perfectly and concisely states the straw-man: > If your job is only to write beautiful code, you have a problem. Definitely no one at senior or even mid thinks this is what their job is about. Something like modularity is beautiful because it works and because of what it enables.. we don't try to shove it into place because it's beautiful. Talking about it the other way around sounds like a manager who does not understand engineering trying to paraphrase stuff that engineers are saying, poorly. Indeed quoting from this self-described entrepreneur's "About Me" page: > While I was there, I took a couple computer science courses, decided I was terrible at it and swore to never write software again. I guess that's thought-leadership for you.
- falloutx 9mo ago
  Yeah, I think good code allows modularity and future development without turning into frankenstein's monster . Readability isn't the main goal, but future adaptability is. Also a big issue with AI imo is: It allows people to write who stopped writing code ages ago because they think they somehow can work at higher level.