how to be good at your job
- realize this one thing is actually made up of two separate things
- realize instead of solving the direct problem you can solve a broader problem
- instead of implementing thing, implement other thing that makes it easier to implement thing
this is mostly a guardrails problem:
- teams can't keep up with code review
- existing testing is mostly "fake"
- the good ICs care, most don't give a shit. tokens amplify this problem
the paradox of ai adoption at tech companies is that individuals are getting way more done but teams as a whole are not shipping products any faster. in large part this is because the things that were previously low roi / not worth doing are getting automated, but the core business is still too complex to yeet without following the pdlc.
some companies are better at maintaining quality at scale
but the secret to doing so has nothing to do with the code itself
its maintaining a culture where embarrassment is still a valid signal
when nobody feels embarrassed by a bad release
thats when quality starts to fade
landed my first PR where the agent was able to demo the feature it built in the Electron app and put the screenshots in the PR description. https://t.co/6JpzLA7Ul1
@ctatedev you are a madman
@claudeai I super dislike that you removed the active worktree (and ability to copy it) from the UI. It was a big part of my workflow on some apps to kick work off in the terminal based on that
@zeeg@bcherny For a long time it would be basic shit like the messages in the desktop Claude code being all out of order, it was like a classic index as key type bug that seems extremely avoidable, a whole lot of that type of jank, stale state, etc