3 ms·
> Where are the amazing digital products/stuff? I've done amounts of refactoring and fixes and written tooling that just wouldn't have happened before. I'm no
by KronisLV 2mo ago
> Where are the amazing digital products/stuff?
I've done amounts of refactoring and fixes and written tooling that just wouldn't have happened before.
I'm not sure what amazing new stuff y'all expect but the amount of technical debt in my projects is actually going down, cause I can finally get good enough test coverage, including E2E/load tests that actually prove whether the software works and scales or doesn't - just last week I diagnosed issues with SeaweedFS failing under concurrent writes when backing Sentry and could swap it out for Garage in a day, caught by a monitoring tool I slopped together that integrates with the Sentry API, no issues since.
The environment around me has gone from drowning in tech/ops debt to sort of swimming and at least holding above water for now (cause nobody will pay for 5x more tokens).
It's also insanely good for prototyping and being able to actually explore various ideas and shoot the bad ones down quickly instead of handwaving and looking at a loaded calendar, alongside being able to address well bounded tasks in parallel, better than human developers can - like I can give 5 GitHub issues to the slop machine and have it fix all of the annoying bugs. Issue with how some data shows up? Just feed it the DB dump and let it find out what's up.
Some projects have gone from around 500 code tests to around 4000, and before anyone says they're meaningless, at least 5% of those have caught real issues and helped a bunch, alongside linters and other tooling (including some tools I wrote myself). I've also written both native utilities and some web platforms for myself, side projects that I never would have gotten around to.
I'm measurably more productive than I've ever been (since I did measure that, looking at my commits over the last 2 years) but also burnt out. Still, it's the kind of burnout that's the consequence of context switching and lots of work, rather than the kind that I had years ago, where I had to manually untangle deeply nested Spring Boot service logic all over the place at like 2 AM cause the made up deadlines were kicking my butt.
In contrast to others, I don't need to move the goalposts - the productivity for me is here and now. Any future models will just make it better, unless we experience model collapse.
Disclaimer: you do need a LOT of code tests and validations, otherwise it all goes to shit. Maybe I'm just extending how much time it will be until it goes to shit for me as well, but go figure. You also have to babysit the models more than anyone would like or should, most of my work usually has 20-60 minutes of planning before dispatching the agent.
- Sharlin 2mo agoFor 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.
- chrislusf 2mo agoHi, KronisLV, I work on SeaweedFS and would like to know about the "issues with SeaweedFS failing under concurrent writes when backing Sentry". You can reply here or create a github issue for this. Appreciate it!
- chrislusf 2mo agoActually, I managed to reproduce this. It was caused by upstream grpc connection pool (https://github.com/grpc/grpc-go/issues/9330 https://github.com/grpc/grpc-go/issues/9330). Fixing it now.