engineering philosophy – Erlang is a fabulous demonstration that by embracing failure you can make more reliable softwareīut when you fail to address any of the above, you end up with today's software quality crisis – crashes, bloat and more.
development practices – things like test driven development and pair programming (stop arguing on pair programming we can debate this later I'll wager I've spent more time actively pairing than you) that demonstrably improve code quality.'Friends don't let friends use C++' or 'Practice safe computing my son' technology platform – some technologies are inherently riskier than others i.e.I think all of us gray beards know that software crashes, generally, are a choice of the developer in terms of his: The older I get and remain an active software engineer, the less accepting I am of poor software quality. Authored: in a post crash state of despair.Updated: updated with additional info on Lapce and Zed thanks to input from people related to those projects on Twitter (thank you) Updated: added Neovide, a description of each editor, github start count and more.I got some good information on Lapce from - maybe - the author and I've updated that. Note: This has now appeared on Hacker News – thank you for the upvotes I'm very flattered.
