News for hackers. Stuff that matters.
Re:Lua: Good, Bad, and Ugly Parts (2012) by strenholme on Monday December 27, 2021 @08:32AM (#29702351)
Indeed. Unmanageable code bases come from conversations like this between management and developers:

“Look, we need you to implement this feature within the next 24 hours.”

“Based on my scrum analysis, I need about a week to implement it.”

“Sorry, if it’s not done within the next 24 hours, you will be out of a job.”

“OK....”

At which point, we get a hideous rush job. I have seen this happen time and time again. There is no language in the world which isn’t going to be able to force clean, manageable code under these kinds of circumstances, which alas can and do happen too often in the caffeine and work obsessed tech culture.

Re:Lua: Good, Bad, and Ugly Parts (2012) by crispyalmond on Monday December 27, 2021 @01:34PM (#29705251)
I recently started working at a place which is like this, and the code really shows it. It really does not matter what language is used, it's not going to very maintainable if written so quickly.
Re:Lua: Good, Bad, and Ugly Parts (2012) by cies on Monday December 27, 2021 @05:45PM (#29707820)
Have you coded with Haskell or Elm? Im confident that re-factoring that mess that surely comes out of the 24h sprint will be re-factorable without too much pain in these languages.

Just a feeling, but coding with them feels like they are refactor-optimized langs.

Re:Lua: Good, Bad, and Ugly Parts (2012) by zepto on Monday December 27, 2021 @09:16PM (#29709558)
If you keep having to do 24 hour sprints without refactoring it doesn’t matter.