Not exactly but if you're not obsessed with maintaining a monorepo, Gitlab allows you to organize your repos around organizations, which then has granular permissions. The underlying primitives is still Git, of course, so you can just submodule as necessary.

> Making matters worse, many datacenters now in the pipeline in the US are slated for areas already experiencing drought, according to analysis by The Guardian newspaper.

If it's astroturfed it's only because the people complaining don't have enough water to grow natural grass on their lawn. FTFY.

The article even admits that their current tasks are easier than before. For the same paycheck! For 200K I will dredge through the most obscure IMO/Leetcode/ICPC problems and the palm of my hands will remain delicately smooth, in danger only of drying from the air conditioning. If there is no meaning and dignity in that I'm sure I'll have plenty leftover from that comp to find meaning and dignity elsewhere be it a side gig, charity work, or heck even just good times with my family and my social circle. A lot of people "just do a job" for much, much less and still live rich inner lives.

Really, an orchestra of small violins playing while I read this one.

Put simply, the 10x developer is a 10x because they've spent ~10x more time immersed in the problem domain than the average developer.

What they do is more sleight-of-hand than Tony Stark engineering his way out of a terrorist cell. If 10x engineer takes a weekend to solve a problem that has stumped the team for a month, it's because he's collected the necessary context to solve the problem over the course of their long career; doesn't mean the answer didn't need to be synthesized, but they already had the raw materials in their cupboard. They have a giants' shoulder to stand on because they bothered climbing. They didn't derive anything from first principles; no one prototyped an Iron Man suit from scrap contraband.

The implication being anyone can be a 10x engineer in the right environment.

---

Allow me to carry my own throne with an anecdote, believe what you will: once upon a time, Engineering Manager had the brilliant idea to create a modular system for our main product, the pitch being that we can outsource feature development to contractors while keeping team costs down as we only need to maintain a lean modular system. They tested the idea on a couple of easy scope projects which were successful.

Then came the big test. Three projects outsourced to a team of four contractors. These projects were far more complex than the first two: lots of state management and integration with other systems. In due time deadline neared and the contractors had a very pretty UI that just needed to be wired in. I got pulled in to see the projects home. It was supposed to be easy if not for the Pareto Principle. Relationship with the contractors soon soured as they bailed, showing us that they've technically already accomplished the project on their billable hours spreadsheet. We, the regular team, just needed to deploy the code they turned in but the deployment is none of their concern apparently.

That's when I had to roll-up my sleeves, got dirty with their spaghetti code. The way I see it, the contractors fell on the part where they had to integrate with other systems because said systems were legacy, i.e., created before the idea of the Lean Modular Main System. Honestly, even I didn't know exactly how to work with them but, crucially, I knew how to get answers when the going got tough. I knew how to quickly figure out what I didn't know because as a regular employee I knew things beyond first principles.

In the end, two out of the three projects deployed. They were only a couple weeks late. IIRC the third one only failed because it really ran out of time budget. Upper Management was not happy but Engineering Manager stuck out his neck for me, for which I am genuinely grateful. I didn't get exactly the coveted 10x wording out of him but he pointed out that I released 2/3 whereas a team of four couldn't even release one.

That's not entirely accurate of course. I could code you up a decent web frontend but I could not, for the life of me, get all those pretty UI animations to work even if it's my only way out of a terrorist cell.

I have always tried to abide by DRY in my programming career with the huge exception of writing unit tests. I made the mistake, early in my career when Test-Driven Development was all the rage, of making unit tests reflect the inheritance structure of the actual code. It just made sense. Needless to say, it quickly descended into the most bizarre manifestation of inheritance hell as tests randomly failed with no correlation to the changes done in the core code.

Hence, I resolved to make unit tests the huge exception to DRY. The more straightforward your tests are, the better. Endeavor that each test method up to a test class should read understandably on its own.

This, of course, made tests quite a mechanical chore to write. Which makes it the perfect use case for these large, verbose, and humorless daemons. Bonus that they are also very good at vibing out the set-up needed for a test so I can focus on specifying the test cases I want rather than setting up mock after stub after fake.

The output is also very easy to review and verify. I see no moral quandary in this kind of usage.

The AI you read of as a child (speaking for myself, coming from a lot of 80s sci-fi stories) is not all good of course; that's where most of the plot's conflict comes from. But LLMs, for a lot of people, are more burdened with the downsides sci-fi stories warned us about with very little, if any, of the advantages.

And speaking of forests for the trees, you zoom out a bit more and see that this AI hype train is following a years-long trend of SV being exposed for its moral failings. We have repeatedly shown, as an industry, that we missed the point of the literature we so love to quote. From the concept of "meritocracy" to naming a company "Palantir". The AI hype is not an isolated incident. We love to quote Jeff Goldblum from Jurassic Park but it's all rhetoric---we don't really ask ourselves that question!

I get the idea to "battle-test" the rewrite first but (a) how does one even determine a reasonable timeframe for battle-testing that much LOC and (b) each vibe-coded update pushed to the Bun upstream basically resets the battle-testing timer. I guess you could lag behind $LATEST by a given window but that just brings us back to (a).

I get the idea to "battle-test" the rewrite first but (a) how does one even determine a reasonable timeframe for battle-testing that much LOC and (b) each vibe-coded update pushed to the Bun upstream basically resets the battle-testing timer. I guess you could lag behind $LATEST by a given window but that just brings us back to (a).

Given that part of their announcement is to keep supporting pre-rewrite versions of Bun, it implies to me that they are open to reconsider if the Bun team cleans up their act. I don't think it could get any more reasonable than that.

It's not "spam" if it is relevant to me, such as security incident disclosures.

Also, as tiffanyh pointed out, what's wrong with Github blog or is that exclusively for marketing fluff now? That would've been appropriate enough, without having to spend Sendgrid credits.

Not to mention Twitter is not an open platform anymore! (A) I'm an employee in an organization paying for Github. (B) I don't have a Twitter account. I already have a Github account because of (A). Why should (B) stop/delay me from getting official comms about this?

More than a decade ago I had a project that used a pretty aggressive input-suggestion widget on the UI. We used a jQuery plugin for it and it was by far the most complicated part of the frontend. In fact, it was the main use-case for jQuery in that project.

Reading the article, I thought it would be pretty much a breeze re-implementing that frontend in a lightweight JS-minimalist version. But of course, unless I ship my machine to the users, not really. Sad state of affairs.

Nonetheless, I'm really impressed with what's included in the HTML spec nowadays! I haven't kept-up with developments in the spec since I read all about XHTML in high school. I ought to take some time every now and then to see what's changed though, again, browser compatibility is a PITA today as it was back in high school.

Though I kinda agree that framing it as "consent" feels a bit off even if I myself would say no if only Chrome had the courtesy to ask. What icks me more is a 4GB[1] blob that has no relevance to the primary business of being a web browser; this is basically the IE anti-trust issue all over again. And it's an experimental feature! Under saner policies this thing would be a plugin from "Google Chrome Labs".

[1] I found weights.bin in Ubuntu 22.04 Chrome v147.0.7727.137 but it's "only" 2.7GB. Still, my ick stands.

- The Witcher 3 (honorable mention, for all its jank, Skyrim) - Sublime Text and vim - Krita and Procreate - Early Google Chrome - Redis and Postgres

Seeing "steve-yegge.medium.com" on the HN frontpage averts me by reflex. Like, I'm suddenly inspired to learn more about agriculture. Or contracting, I heard that could be lucrative. Heck, I'd even go full hipster and open a bookshop in this economy.

Steve, you probably don't give a shit about my opinion but I just want to know from which Jamaican zip codes do you source your supply.

The plot thickens...

- IT policies around GH accounts make no sense. It's a long story but, in short, you can't use any of your pre-existing GH accounts whether personal or professional (as in, an account I made exclusively for $DAYJOB before The Synergy Mandate) and must create a new one aligned with IT conventions.

- We don't monorepo hence we made extensive use of groups. There is no direct mapping for this concept in GitHub so we have to manually namespace projects.

- And now of course GH's no-nines availability :(

For my team, profit happens to be sensitive to our release dates---a day or two of delay can really make the difference if we'll make the month's projections or not. In another world, I would proactively mirror our profit-essential code but it's not worth the risk making a skunkworks guerilla effort. I'd like to think we can blame The Synergy Mandate in a few postmortems in the near future but of course I did not graduate yesterday, I know that's not gonna happen.

Thoughts and prayers we keep hitting our profit projections and they don't axe our product for underperformance.

(Writing this down, I can really feel how this job has changed since I joined.)

> inconsiderate of 1 in every 10 people in public spaces.

It's high-impact for you but low-impact for humanity in general or even just for businesses with a rat problem.

1 in 10 is exactly the definition of "low impact". I get that it's a ginormous inconvenience to the dozens of you out there---and as a person with his own allergies, albeit not to cats, you have my sympathy---but that doesn't change the fact that 10% falls pretty squarely under the definition of low-impact.

- WYSIWYG editor is table stakes. The lovely folks at marketing once thought I was hacking when I `ps -eaf`-ed in an unresponsive Macbook.

- They "put" images in their post. They don't "upload the image and position it with CSS".

- It's the marketing department so they have to have all sorts of bells and whistles. At the very least tracking, at most some obscure integration plug-in that as an engineer I have no kind words for. Social integrations and "You may also like..." sections also come to mind.

> cheap WP plugins that export the whole site as static to something like FTP or S3, so you can just firewall the actual WP behind an IP restriction and host the actual public-facing site from S3/whatever.

Not that I have extensive WP experience but unless you can name me an actual plugin that has good street cred for being used in the wild wild west, I'm gonna say this is not as easy as you make it sound. For one you just described a very rudimentary data pipeline which someone has to support and maintain even infrequently. Also, speaking from experience, plugins don't always play nice with other plugins. I once tried to export my very basic personal site out of WP to find the footnotes all messed up (I don't know now but back then I handled footnotes with a plugin).