191–194 of 194 posts
Earlier quoted context omitted.
Are you working on complex systems that serve many users in production? Do you actually save time?
Yes, I can't say exactly what but the backbone of cloud computing and/or infra, think databases, distributed storage, filesystems, ...
Earlier quoted context omitted.
Mechanics I've been to generally have no idea about how things actually in the car work - from what I could understand, area is full of recurring problems, and this exactly benefits mechanics to solve them through trial and error approach rather than understanding much how underlying things work. Pretty much close to what I would say SWE will turn into, there's no other choice IMO in foreseeable future.
I think you underestimate the skill of more experienced mechanics. Tractor (as in 18 wheeler) and master mechanics tend to know what’s going on under the hood in detail.
Earlier quoted context omitted.
Yes, I can't say exactly what but the backbone of cloud computing and/or infra, think databases, distributed storage, filesystems, ...
I mean, AWS did just recently go down due to a vibe-coding / agent-run-amuck incident, didn’t it?
Earlier quoted context omitted.
> Lint rules, type errors, commit lint, anything These are basic: they work for human coders and are typically quick to setup. But gates at this level are far from enough for agentic coding. You need an extensive test suite/e2e suite/benchmark suite. Typically much larger than the code base itself: This is what enables those "i ported bun to rust in a weekend" headlines. Where ever such extensive 'gates', high qualit…
I mean, from my training long ago, a good test suite is usually / always a few multiples in size of the codebase. 100k lines of app code? 300-500k lines of test, sort of thing.
I am now looking at 9 to 10x the app code, for non trivial stuff. And this is not just the usual unit/integration/e2e suites too. Extensive deadcode, field use, code shape tests (ast walking) - god objects, 15-param helpers, wrapper-piled-upon-wrapper, badly named (a skill) functions/methods/objects, path-dependent artifacts, etc. There is no way I could have written all this manually.
It doesn't guarentee high quality OR reliability or readability or maintainability, but does reduce churn and makes me feel a bit more confident about deploying route A work product in prod.