News for hackers. Stuff that matters.

A comment on /story/47587953. Parent comment

Re: by skydhash on Tuesday March 31, 2026 @04:04PM (#47592712)
Unless you’re producing demos for sales presentation (internally or externally), it’s always worth it to produce something good. Bad code will quickly slow you down and it will be a never ending parade of bug tickets.
[ Parent | on HN ]
Re: by steveBK123 on Tuesday March 31, 2026 @04:34PM (#47593114)
indeed, being on-call cleanses many developers of slopulist habits
[ Parent | on HN ]
Re: by abelitoo on Tuesday March 31, 2026 @08:02PM (#47595094)
That depends on how quick the feedback loop is for your decisions. If it takes weeks or months to find the impact of your changes, or worse, if you're insulated somehow from those changes, you may not be pushed toward improving the quality of your code.
[ Parent | on HN ]
Re: by jimbokun on Tuesday March 31, 2026 @08:46PM (#47595403)
A company where it takes weeks and months to deploy a code change is not a company with a long term success horizon.
[ Parent | on HN ]
Re: by pixl97 on Wednesday April 01, 2026 @10:09AM (#47601123)
Lolololol, sorry, I can't help but laugh a bit because some of the most entrenched companies are also the slowest moving.
[ Parent | on HN ]
Re: by gjadi on Tuesday March 31, 2026 @05:38PM (#47593800)
It depends on their sleep habit, work-life requirements and compensation when they need to be on-call.

When you get a fatter check because your code break, the incentives are not in favor of good code.

[ Parent | on HN ]