3 ms·
The product I’m building since 15 years evolved from a 32 bit desktop app (with dependencies from the early 90s) into a heavier 64 bit desktop app 10 years (hun
by alkonaut 7y ago
The product I’m building since 15 years evolved from a 32 bit desktop app (with dependencies from the early 90s) into a heavier 64 bit desktop app 10 years (hundreds of man years) later, and further into cloud services that weren’t even a term when development started.
When you build something that will have new requirements in ten years, implemented by different developers, then you can motivate spending time on code hygiene.
For a game anything that won’t be in the next game you can duct tape. The parts that will go into hundreds of games over a decade is the “engine” and I suppose in that you’d find the same sort of discipline and hygiene as in any other long term code base.
- scruple 7y ago> The product I’m building since 15 years evolved from a 32 bit desktop app (with dependencies from the early 90s) into a heavier 64 bit desktop app 10 years (hundreds of man years) later, and further into cloud services that weren’t even a term when development started. My employer, as well. We have three teams where the main code bases were started ~2001, when the company founded. One of these teams has code that started as Java applets that are now .NET Core. We have another ASP.NET system that they are currently migrating today. The other two teams, building Windows desktop applications, are now invested in web technologies, like browser engines and WebRTC on our A/V side. I cut my teeth in the embedded industry, and we were supporting at least one product that I recall working on there that had code that had started in the early 90s. It's incredible to think about. There was a nice thread yesterday that touched on this topic, as well. [0] [0]: https://news.ycombinator.com/item?id=22042186 https://news.ycombinator.com/item?id=22042186