Comment by emadabdulrahim
3 hours ago
A lot of words, but essentially says nothing useful.
If GitHub is the wrong shape for this new world. Well, show me a hint of what the new world should look like?
To me it seems like everyone is frustrated, mostly at how fast things are changing, but not necessary because the existing tools suddenly became trash/irrelevant.
A lot of us are still contending with the fact that large amount of code is being produced and we don't know what the fuck to do about it. And we're less intimate with the code and product we ship than we were before.
My personal take is that if you want to scale in engineering you really only have 2 options.
1) you start acting like a senior staff level engineer and you stop caring so much about implementation and start caring about the things that actually matter, the architecture, the performance profile, the scalability, the test coverage, the monitoring, the velocity of development, etc etc.
Or 2) you don't scale.
LLMs can write 10k lines of code per day like its nothing. You can't review that with a jade handled magnifying glass and keep all that in your mind. After a few months, you could easily have 250k lines of dense production code + much more in tests and tooling etc.
You either have a team of people to watch over that, or you don't. You're not scaling yourself to be able to review all that and keep it all in your mind.
If other people are scaling, and you're not, you're unlikely to do as well as them. BUT, it's not impossible if you're really good. Being really good scales way less than using LLMs effectively.
Google doesn't work because they rely on hope that every person they hire doesn't do things they shouldn't. It works because they make it nearly impossible to do things you shouldn't. You need to build systems as well. Or you don't. Just do it the old way.
Pick your poison.
The problem I see is that in a traditional company a senior engineer would push back on complexity and know when to do due diligence.
AI seldom pushes back, embraces complexity, does a lot of due diligence (however often superficial), and then completely misses the point and lays a trap on the code.
It’s not nearly as trustworthy as an actual team of humans.
> you stop caring so much about implementation and start caring about the things that actually matter, the architecture, the performance profile, the scalability, the test coverage, the monitoring, the velocity of development
What architecture doesn’t care about implementation? What performance profile doesn’t care about the details of the implementation? What does the test coverage is about if it’s not the implementation? What are you monitoring? The specs or the implementation?…
Not caring about the implementation seems like not caring about the materials when building an house, with eyes stayed only glued to a novel’s like description of the house.
>A lot of words, but essentially says nothing useful.
This is essentially the state of all blog posts now. As well as much code. Lots of content, not a lot of value.
I couldn't agree more. I've been building something that is trying to solve this problem, an abstraction layer for code that you, your agents and co-workers can all use together. I would love the chance to talk to you and get feedback if you're willing.
My email is in my bio