[flagged]
GitHub is the wrong shape for this new world
41–50 of 53 posts
Re: GitHub is the wrong shape for this new world
#42[flagged]
Re: GitHub is the wrong shape for this new world
#43"The winners of the next decade won't build a better pull request. They'll build the infrastructure that makes software generation, validation, and deployment operate at machine scale."
This is funny, as all the listed primitives and this scale of reliable build infra is the exact shape of Buildkite.
Re: GitHub is the wrong shape for this new world
#44The article failed to describe the problem or a solution. But it was fun seeing the phrase “paradigm shift” again, which feels very 1998.
But do we really need a paradigm shift in how we express the concept of a paradigm shift? It's not like the meaning of the words expired.
Re: GitHub is the wrong shape for this new world
#45Earlier quoted context omitted.
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 wr…
> 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 implement…
I think you misunderstand - it’s not that you shouldn’t be capable of evaluating and improving the implementation, but that it’s usually irrelevant. A very large majority of the time, “good enough” is fine. Fix things people complain about, and use the rest of your time to do more important things.
Re: GitHub is the wrong shape for this new world
#46Earlier quoted context omitted.
> 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 implement…
I think you misunderstand - it’s not that you shouldn’t be capable of evaluating and improving the implementation, but that it’s usually irrelevant. A very large majority of the time, “good enough” is fine. Fix things people complain about, and use the rest of your time to do more important things.
and this is why everything needs 32+GB of RAM and an assload of storage.
LLMs don't have human attention to detail, IME
Re: GitHub is the wrong shape for this new world
#47This is an advert
Re: GitHub is the wrong shape for this new world
#48This is an advert
So?
Re: GitHub is the wrong shape for this new world
#49Earlier quoted context omitted.
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 wr…
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.
That's why you need a way to measure complexity - and no cyclomatic complexity is not it.