>If a company (like Microsoft with Excel) is slow but eventually gets there, then they are successful.
>If a company (like Microsoft with Excel) is slow but eventually gets there, then they are successful. Excel was successful because Lotus decided 123 had so much technical debt it would be a good idea to "upgrade" the old assembler code to C. This took at least a year longer than planned, and introduced a lot of bugs and incompatibilities. Meanwhile Windows had arrived, and the planned Windows rewrite of 123 never happened as scheduled. So it wasn't so much that technical debt killed 123. But poor management of technical debt certainly did. Effectively the C rewrite was a complete waste of time, and Lotus should have aimed for a Windows release as soon as they could. It's nice to be able to say this with hindsight, but it was doubtless much less obvious at the time, when Windows was barely considered a mediocre visual DOS shell, and certainly not a serious OS. Bottom line - you have to be smart, prescient, and a little lucky to manage technical debt. It's not just about getting the code right - it's making decisions with educated guesses about where you may be a year or two from now. And that's hard.
Posted by TheOtherHobbes on May 14, 2015, 1:15 AM
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.6,500 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?
>If a company (like Microsoft with Excel) is slow but eventually gets there, then they are successful.
>If a company (like Microsoft with Excel) is slow but eventually gets there, then they are successful. Excel was successful because Lotus decided 123 had so much technical debt it would be a good idea to "upgrade" the old assembler code to C. This took at least a year longer than planned, and introduced a lot of bugs and incompatibilities. Meanwhile Windows had arrived, and the planned Windows rewrite of 123 never happened as scheduled. So it wasn't so much that technical debt killed 123. But poor management of technical debt certainly did. Effectively the C rewrite was a complete waste of time, and Lotus should have aimed for a Windows release as soon as they could. It's nice to be able to say this with hindsight, but it was doubtless much less obvious at the time, when Windows was barely considered a mediocre visual DOS shell, and certainly not a serious OS. Bottom line - you have to be smart, prescient, and a little lucky to manage technical debt. It's not just about getting the code right - it's making decisions with educated guesses about where you may be a year or two from now. And that's hard.
Comments (0)
No comments yet. Start the discussion.