The problem with the "Don't hack things together" advice is that it's invariably written by developers who like to write code, enjoy writ...
The problem with the "Don't hack things together" advice is that it's invariably written by developers who like to write code, enjoy writing about code, and want to be seen as thoughtful and influential people in their development community. Those sorts of people tend to gravitate towards the projects that have the scale where code quality is critical because what they work on lasts for years with thousands of people building on it. If you're a developer who throws code together in a few months for clients who aren't paying for a quality product, and maybe you'll come back to it a couple of times in the future when it needs a new field added or a page title changed, then a hack is perfectly valid and can hugely improve your business's bottom line over spending even just another 10% making sure you've got tests and documentation and defensive code and so on. Spending time on the maintainability of code that no one will ever maintain is a waste of time.
Posted by onion2k on Jan 22, 2015, 3:30 PM
Tags
Related issues
- The biggest problem with having an LLM do this, from what I've observed of at least frontier models, is that the way they are trained...
- The biggest problem with MOND is that it was hand-crafted with additional parameters simply to fit the data.
- (My comment is about detached houses).
- The biggest problem with this is that I can't run my company's own internal benchmarks against this API, because they will be trained int...
- > steer Claude away from over-engineering parts of the system in response to hypothetical concerns.
- Why is there no comparison with FLUX 3 Image?
Raise real-world problems, find people facing the same issue, and discuss solutions.8,000 issues0 comments
hackernews (Other)
The biggest problem with having an LLM do this, from what I've observed of at least frontier models, is that the way they are trained...
The biggest problem with MOND is that it was hand-crafted with additional parameters simply to fit the data.
(My comment is about detached houses).
The biggest problem with this is that I can't run my company's own internal benchmarks against this API, because they will be trained int...
> steer Claude away from over-engineering parts of the system in response to hypothetical concerns.
Why is there no comparison with FLUX 3 Image?
> our Git monorepo was developing an annoying problem Sentences like this are so common from people using monorepos that I am convinced ...
Why is there no contact form?
The problem with the "Don't hack things together" advice is that it's invariably written by developers who like to write code, enjoy writ...
The problem with the "Don't hack things together" advice is that it's invariably written by developers who like to write code, enjoy writing about code, and want to be seen as thoughtful and influential people in their development community. Those sorts of people tend to gravitate towards the projects that have the scale where code quality is critical because what they work on lasts for years with thousands of people building on it. If you're a developer who throws code together in a few months for clients who aren't paying for a quality product, and maybe you'll come back to it a couple of times in the future when it needs a new field added or a page title changed, then a hack is perfectly valid and can hugely improve your business's bottom line over spending even just another 10% making sure you've got tests and documentation and defensive code and so on. Spending time on the maintainability of code that no one will ever maintain is a waste of time.
Comments (0)
No comments yet. Start the discussion.