4 ms·
For that you need a management that actually lets you use the token budget for stuff like refactoring, fixes, and test coverage. Unfortunately I'd wager that's
by Sharlin 2mo ago
For that you need a management that actually lets you use the token budget for stuff like refactoring, fixes, and test coverage. Unfortunately I'd wager that's an exception and the rule is (still) that to most managers LLMs are "feature machine go BRRRRT", leaving even less time for anything else besides pushing out features at a breakneck speed because you're supposed to be 10x more efficient now.
- KronisLV 2mo agoDon’t ask for permission then? Implement features at a viable pace and drown any unrealistic expectations in reports of CVE fixes - usually a version bump of dependencies, but quite often also some migration work within the app; write tools to make that work visible like I did with scanning and reports, and enjoy living without having to complain about how you can’t keep up with releases while letting your software rot until it’s a multi-year migration. Alongside that, do the same for test coverage as well because it’s the humans that have been sloppy for years and didn’t work enough on the test harnesses or good enough coverage, introduce Testcontainers and load testing tools and anything else that makes sense. Use their money for tokens to build software that is actually good and make your life easier and ensure that their shortsightedness won’t sink the product on a few years. Of course you could also get fired if they’re stupid, but then I don’t imagine that working for those that are delusional is exactly great either, unless the goal is explicitly to make slop to get investor money in which case the whole thing will probably need to be rewritten from scratch anyways so who cares.