3 ms·
Yeah, it's crazy to me how common it is to just let basic dev environment polish languish. In a small enough place, I usually will just fix whatever is slowest
by sushisource 6y ago
Yeah, it's crazy to me how common it is to just let basic dev environment polish languish.
In a small enough place, I usually will just fix whatever is slowest and most annoying about it myself.
At bigger places... good luck. Sometimes you can get away with hacking together some scripts that do things for your personal setup, but if there isn't buy in to fix the problem you're often out of luck.
- blablabla123 6y agoBut I think this one point is the one item that ultimately decides on the lifetime of a project and whether it will turn legacy. If the README doesn't even describe how to start the project or successfully invoke a single unit test, how is anyone going to deploy this or change anything of the core code? Also not having this usually means unreliable deployments, broken CIs and constant firefighting. This might be considered acceptable for 1-person-projects until that one person might change projects or jobs.