I've made a general repo linting tool [0][1]. Originally it's purpose was to replace a bunch of repo hygiene/structure validation scripts I ended up adding as I noticed various sloppy AI changes. I ended up going through a bunch of open source repos to see what other kinds of validations they had via scripts and incorporated those into the tool as a set of general/extensible rule types. This tool allows you to define repo structure, hygiene and other rules in a declarative way, and it is very fast [2] (great for pre-commit and CI workflows).
Shameless plug - I've been working on a general repo linting tool alint [0], which helps keep a repo cleanly structured and hygienic - essentially a linter for everything in a repo that a language-specific linter doesn't cover. It also has some considerations for integrating/playing nicely with agentic coding [1]. This started as a replacement to a bunch of scripts I had in repos that did similar things - but more cohesive, readable and much faster.
I've been building a general linter tool to help keep repos in a consistent and clean shape when working with AI [0]. You can define repo and file layout, structure, hygiene rules and have them checked in pre-commit, in ci, or manually. It also integrates and plays well with AGENTS.md - allowing exporting agent instructions from the alint rule config [1].
I found myself writing a bunch of scripts and AGENTS.md for ensuring certain structure/organization for projects when using AI. The maintenance, performance, and reliability of these eventually became a problem, so I built this tool.
In order to make it more generally useful I went through a bunch of open source repos to see what kind of hygiene/validations they do - and it turns out quite a few repos have their own scripts and validation for similar purposes - I've been gradually adding more rules/validation types to cover more use cases.
In the process I also discovered repolinter [0] - a similar to tool which is now archived.
The corporations and executives are already winning if you swallowed the concept of 'rockstar' engineer. Sure there are more and less experienced engineers, but even interns can and often do provide good input and spot mistakes made by seniors. The 'rockstar' engineer at most tech companies simply equates to the somewhat autistic guy with a brown nose who's working 15 hour days for a pat on the head from management (and making many mistakes in the process).
>The 'rockstar' engineer at most tech companies simply equates to the somewhat autistic guy with a brown nose who's working 15 hour days for a pat on the head from management (and making many mistakes in the process).
I love it! And posts on HN about Big Ideas and uses corpspeak to justify driving people to long hours. The engineer who's picked up talking points of his employer because he's well-paid and trapped on the spectrum, making it hard to comprehend a life of Play outside of work.
The study that defined the 10x engineer defined him as 10x as good as the worst engineer. If there is a 0.1x engineer, and a 1x engineer, that 1x engineer is the very definition of a 10x engineer.
I've long thought a 10x engineer is one with just the right amount of analysis paralysis - not too much or too little. It's not that they're 10x engineers, it's that everyone else is 0.1x due to a confluence of reasons. And the ones we call 0.1x are 0.01x.
Some famous examples of a "10x developer" state: Linus Torvalds writing Git, Brendan Eich writing JavaScript. Somewhat less famously, I get that feeling often when I stop thinking and start doing on an electronics project, a wooden shed or even a cosplay. Every hackathon ever, same principle - stop thinking, start doing.
But it's only a 10x state if you're doing the right thing, otherwise it's a -10x state, and that means you need to have already done the right amount of thinking and have a good intuition for what you're trying to do. (As long as you can recognize a failed experiment and revert, risk of being -10x isn't that terrible)
This is such an obvious observation that I’m surprised to find it often missing. 0.1X is nothing compared to the destruction (ie negative X) you can do with the right combination of recklessness and managerial pressure. Definitely happens with engineers. Perhaps even more with PMs.
Even if we forget "rockstar", there are certainly different levels of engineers. More experience doesn't automatically mean better either. That is not to say experience doesn't matter. It matters quite a bit.
Sure , good interns can sometimes have good feedback or spot mistakes. But not consistently enough.
All of this to say that it's not just experience that makes one a better engineer.
Experience is one of the only objective signals we have, but you're right it's not the only one. I've seen plenty great junior engineers and interns, and plenty of incompetent staff/principal engineers.
> should expect maybe 5x faster cycle in major software apps
To what end and what would that even look like though? Enshittifying everything at maximum speed? The apps/platforms I use regularly - GitHub, Spotify, Google maps (just to name a few), have gotten noticeably shittier in recent times.
>GitHub, Spotify, Google maps (just to name a few), have gotten noticeably shittier in recent times.
What if AI lets you create new versions of those tools, but without the enshitification?
I say that being in the "soaking" stage of using AI to rebuild a shitty software project in 70KLOC over about 2 weeks of spare time, so this may not be as theoretical as you might think.
> What if AI lets you create new versions of those tools, but without the enshitification?
I'm not sure I fully understand what you're saying here. Isn't the value of these tools almost entirely independent of their actual software? That is, we have many good open source, self-hostable forges (Forgejo, sr.ht, etc.), lots of great music player software (Jellyfin, Symphonium, etc.), and decent maps software (OsmAnd and Organic Maps). People use GitHub, Spotify, and Google Maps -- perhaps even _put up_ with their often bad/glitchy software -- because of network effects (all three) and content/licensing partnerships (Spotify/GMaps). That proprietary data isn't something AI can help you with, right?
It really depends on the use-case. For example, my most starred github repo is a tool to convert Spotify playlists to YouTube Music (that was done pre-AI). Github depends on what issues you have with it, what your use case is, and whether you can leverage some of the network effects via API from the github source. Maps, same story.
Confirmation bias. The internet has complained about software updates decades before LLMs became ubiquitous. I made a career fixing human slop by domain experts.
We easily forget that the great majority of software engineering is fixing the mistakes of other highly capable software engineers.
It's just so easy to blame the machine instead of admitting no one here is an expert on anything and they count their hits and not misses. If they did, we would find the probability of making a mistake to be higher than a fronter coding agent.
It's a hard headed crowd and everyone, LLM pilled or not, suffers from the Dunning-Kruger. All of us.
Just look at the comments. Everyone is perfect when they do things themselves.
There's a pattern I noticed, especially on this site, where people claim various VC/ad/tech dark patterns, enshitification, privacy violations, dishonest marketing, etc MUST be allowed, otherwise open source or 'the internet' will face some sort of existential risk.
No bro - open source and the internet existed long before SV tech parasitism did and will exist long after.
I don't disagree, that pattern exists, but it is essentially true. Just not in the way the folks saying it is true understand it. If the "VC/ad/tech dark patterns, enshitification, privacy violations, dishonest marketing, Etc." wasn't allowed then their job might not exist. That can be true. What is missed is that if there is value in the thing, then it will exist.
When I reflect back to someone making this argument by saying, "So your argument is that you make your living as a pick pocket, but if pick pocketing is made to be illegal, you won't be able to make a living." Which of course would only be true if they only thing they could do was 'be a pick pocket'. Its a very common rhetorical technique to argue that the status quo cannot be changed. All the arguments that "you'll put all coal miners out of business if you require only green energy" And yet the people, the miners themselves, will likely be fine. The firms might not, but there are other firms that could exist.
This isn't a new problem, or one specific to this web site, although it does get disproportionately hit because so many technology companies saw what Google started in the 2000's and said, "Man there is soooo many ways to get money for this." rather than, "Is this a reasonable way to make money? Sure it is 'perfectly legal' but is it right? Is it moral?" The type of person who thinks that something is "Only illegal if you get caught" is neither moral nor particularly concerned about what is right. And we got a lot of that type.
"Its a very common rhetorical technique to argue that the status quo cannot be changed."
Thank you for putting this so eloquently into words. This rigid thinking is also common in topics such as working conditions, collective bargaining, on-call time, parental leave, healthcare, and effectively (unintentionally or not) shuts down conversation.
I've come to realize the objections from people who think this way all effectively boil down to 'Be grateful for what you have because any alternative would be worse.' But if you pry and ask that they expand you'll find there really isn't any there there, because it's black and white thinking. It isn't rooted in fact, it comes from fear. I sure hope we haven't collectively forgot how to even imagine a system that functions better than the one we have today.
Thanks. For me, I was in debate club in High School and that included basic rhetoric. In college I took an argumentation class as a non-engineering elective. The most useful thing this class taught (for me) is how to 'see' the argument, and as a consequence see how it is constructed. Throughout my career it has been especially useful in "political" situations at work. Not everyone argues in good faith, and being able to spot those who are not is valuable.
reply