…and you can get almost identical features by simply installing the GitHub app inside Slack, and then asking Copilot to work on something, this should take < 5m to set up for any organisation using Slack and GitHub.

I don’t know enough about either but if their approach was to make it substantially more opinionated, which is likely in the case of an org that’s subject to audits, it would make sense to keep it separate.

I don't have specific information about Minions, but I do know about Stripe's architecture and internal tooling.

The article isn't really talking about changes they made to goose, it's describing how they went about integrating goose with the rest of their developer infrastructure (ie. the AWS-based remote devbox system, Toolshed, etc).

Welcome to the free software movement!

If they didn't violate the licence agreement then I'm struggling to understand why it's off putting

You should always expect this when you make MIT. When you give every company permission to fork your software, make it proprietary, and sue you for copying or reverse engineering it, don't be surprised when they do exactly that. It's in their best interest, after all.

One thing I don’t see developers talking about much is that if your job is to only read code instead of writing it, how do you expect to stay good at reviewing code if you never write it?

I only speak for me but when I review code I need to dig into my own experience writing and and remember what works and what doesn’t that I’ve internalized over years of writing and manually debugging code. Take that out of the equation and I wouldn’t be good at reviewing code for long.

I used to write a lot of C++ back in the day, and I can still read it and understand it for the most part but I would never be able to effectively review anything non-trivial. I just don’t have enough recent experience writing it myself to have internalized all of the obscure pitfalls and gotchas. And just vommitting out some C++ from a bot and just having it redo things until it has the appearance of working correctly isn’t gonna help me with that.

“My job now is just reviewing code” is such an extremey short-sighted view I’m terrified for the future where nobody understands anything anymore. I’m sure OpenAI and Anthropic would love this though.

And yeah, reviewing code is one of the more tedious and unfun parts of the job why would I want this?

One of the most annoying parts of my job is my supervisor who used to be a dev but became a manager years ago. He doesn’t really understand the codebase enough anymore and I spend so much explaining basic things to him now it actually hinders our productivity when he wants to “contribute”. And let me just say that getting a Claude sub for the whole team hasn’t helped this at all.

And one last thing - every single engineer I know that needs to maintain a Stripe integration hates them with the power of a million suns.

I reckon the developers most excited about AI & agents never got the same thrill or satisfaction that you do. Those developers are plainly motivated by different things, and that’s okay.

> It's a hiring ad.

And also a project to pad someone's resume.

My experiments using a more hands off approach of prompting claude code have always resulted in a two-steps-forward-one-step-back play, where the agent clearly did some good stuff, but did some other stuff in a somewhat undesirable manner, which subsequently needed correcting.

This usually results in A: creating commits where tons of code is being constantly added and removed, B: due to Claude's somewhat cavalier attitude to existing code, has steadily eroded my familiarity with the code base.

I'm still not convinced that these longer loops are that beneficial, compared to 1min prompts to 5-10min AI work.

Doesn't delegating make this a lot more possible? You can fire off a request to a sub-agent, they respond with some predictable status that you can parse, and then you continue (you being the "main" agent), so the context window can remain relatively small. Kinda like how a human does it.

>> Over a thousand pull requests merged each week at Stripe are completely minion-produced, and while they’re human-reviewed, they contain no human-written code

> I pity the senior engineer, demoted from a helmsman into a human breakwater, tasked to stand steady against an ever-swelling sea of AI slop.

I'm skeptical that the human-in-the-loop, whose only task is to read code, is going to be able to review at the rate that the AI can produce.

It's Undefined Behaviour, now in every language.

The same minion that came up with the cute effect that covers your screen with the word DEVELOPERS, when you scroll to the end of an article?

The best camera is the camera you have on you.

Smartphones have terrible camera ergonomics, yet they killed the compact dedicated camera.

Sparkling DevEx

Based on the above article about thousands of AI written PRs littering their code base, you might replace “unfortunately” with “fortunately.”

> Blockchain tech is part of my religious beliefs.

What are your religious beliefs? I'm intrigued to hear more.

You were building on Tempo, and they deplatformed you?

“Banks are afraid of only two things: regulators and their wives, and they’re more afraid of their wives than the regulators”

I would retroactively make that quote gender neutral but they're really not afraid of their husbands.

Financial institutions feel like blockchains don’t have a clear chronology of KYC/AML, they dont care about KYC/AML they care about violating it for their relationship with the regulator.