4 ms·
Yeah, I'm not a subscriber to the "YOLO/MVP" school of software development, which basically makes me persona non grata in many tech crowds. When I write softw
by ChrisMarshallNY 3y ago
Yeah, I'm not a subscriber to the "YOLO/MVP" school of software development, which basically makes me persona non grata in many tech crowds.
When I write software, I use what I call "Constant Beta." Basically, my software is at a release level of Quality, from the very start. It may be incomplete (thus, unshippable), but what's there, is ready for its closeup (Mr. DeMille).
Basically, before moving to the next feature, I make sure the one I'm working on, is complete. It may require coming back, after other parts of the program are done, but I always make sure that the API is clear, the documentation is done, and things like error handling and localization are in place, as early as possible.
Surprisingly, I work very, very quickly, despite taking so much care. There's a number of reasons, which would require a series of blog posts, but the results speak for themselves.
- bacon_waffle 3y agoThis sort of approach seems common in the Rust community, it's so much more professional/humane/sustainable/performant than any other corner of the industry that I've come across.