I’ve been trying to ask people a different question: sure, we’re more productive now but to me, the AI era is only serving to plunge us deeper than ever into producing more, more, more, faster, faster, faster. And for what? What’s it all for? I became a software engineer because I have a lot of fun writing code, thinking through and solving complicated problems, and experiencing the reward of seeing what I’ve built by hand working for the first time.
Do people really have fun managing a fleet of agents that generate the code instead? Or is it just the rush of producing something extremely quickly, much more quickly than you might be able to alone, regardless of how well (or poorly) it might work? For me, being able to move quickly was never the fun part.
It’s one thing to utilize AI to lessen the drudgework, the boilerplate, but I look at people who have gone all in on agentic development and it just really makes me wonder.
> I’ve been trying to ask people a different question: sure, we’re more productive now but to me, the AI era is only serving to plunge us deeper than ever into producing more, more, more, faster, faster, faster. And for what? What’s it all for?
Many devs here have stated that the fun part for them is seeing the end product, not the act of creating it. Using AI is an act of need satisfaction.
Unfortunately, cloning a GitHub repository or downloading a Squarespace template doesn't hit the spot, because you can see exactly where the code came from, so your brain knows you were not the one responsible. AI's greatest feature is that it obfuscates provenance. You can now happily clone that repository or download that template without the feeling that you're cloning someone else's repository or downloading someone else's template.
It is why I feel dirty after AI generates a piece of clever code: I know I am stealing somebody's IP without attribution. And the AI companies benefit from this, not the real people behind the training data.
People who use coding as a means to an end, producing a product
People who enjoy process over product and coding is the enjoyable part, not the end product
Company executives fall into bucket 1. Even if you love your cushy air-conditioned job, doesn’t mean the people above you don’t see you as a means to an end, a better product.
Solo founders and small startups are in bucket 1 as well but that doesn’t mean that don’t enjoy coding, just the product being made is much more satisfying.
I think that’s a false dichotomy. I enjoyed coding but was more interested in the problems code could solve. Both were really important facets of the job. When I was a chef, I loved being creative with flavors and techniques, and giving people a new favorite aesthetic memory to file away. Losing one of those things would make the job not worth it to me even though I enjoyed both.
Great point. I learned to code to solve a problem and fell into love with programming as much as the product building. Now the first part is gone and I’m forced to decide which was more enjoyable.
I do think food is a bit different. With software and businesses, the end product keeps on giving and can be forever changed. For food, the process is many times longer than the actual eating the food part.
Brother, there was slop before AI and slop after AI.
Pre-AI slop got a pass because the creator probably worked tirelessly to make it and that process gave it value.
Post-AI slop get criticized because AI can create it so fast and easily.
But the builder has not changed. Because the builder knows that the product depends on iteration and polish. And knowing what to iterate and what to polish requires intuition and taste. And thats the thing about taste, its forever fleeting. What we think is AI slop, was actually novel and coveted at a point before AI existed.
Many developers became developers because of the paycheck, but they never particularly enjoyed the job, so if instead of working they can twiddle their thumbs waiting for the agent to make attempts at fixing their ticket, they prefer it that way.
I can clearly identify this kind of developers at work by their mindless enthusiasm for AI. Development is just another job before they can move into "management" and make all-knowing statements all day long.
> producing more, more, more, faster, faster, faster. And for what? What’s it all for?
If you wanted a literal answer, it is to accelerate revenue as much as possible to make the very rich people who own most of the company even unfathomably richer. No benefit to you for making more faster. Other than the burnout, that's all for you to enjoy.
I know it's probably automatic because of the similar titles, but hitting the bottom of the layoff announcement only to be recommended that article about hiring 1,111 interns in 2026 is a reaaal bad look
Not meaningfully, but sometimes 6mo-1y as part of an undergraduate programme to gain industry experience. E.g. I had 6mo in my third year (not at Cloudflare).
By "Astral" do you mean "Spinel"? Also, what paid services? So far the only paid services they've mentioned is retainer services that essentially amount to priority customer support. The tools themselves are only ever described as free
EDIT: Misread the comment and thought it was only about `rv`, not both `uv` and `rv`
What is Spinel? Astral is the developer of uv, and they have announced their hosted platform service, pyx [0]. It appears it will be FOSS as well, but they'll have a hosted version of it.
What makes you think they _haven't_ tried to work things out with Ruby Central? As per a separate article[1], this seems to be a last resort:
> “Since Ruby Central has informed us they will never allow us to continue working on the projects they now claim they own, that we successfully maintained and operated for the last ten years, the former RubyGems team is launching gem.coop today.”
Some additional context is that Justin Searls is close friends with people who are or have been on Rails Core and/or at Shopify. I've long been a fan of Justin's work, and I've spent time with him at conferences so I can attest to him being a nice person in my experience… But, given the alleged parties at play here, it's hard to take this piece as unbiased when it lacks that disclosure
It's an opinion piece by a trusted member of the community. He doesn't need to act unbiased but be credible and informative. As he wrote in his disclosure:
> People whose livelihood depends on the health of the Ruby ecosystem deserve more information than they're getting, especially now that its operational stability has come under threat.
On this count, Searls' article has done the work. I didn't know that Andre Arko baselessly threatened Google with lawyers, or that Andre played fast-and-loose with people's donations. That information was excluded from "unbiased" analyses and fact-checks which seem to largely target Andre's enemies.
The problem is not that Searls has opinions, it's that this petty hit piece against Andre was heavily wrapped in neutral, 'all I can do is offer a little bit of context', 'I'm not rushing to take sides' framing language, resulting in a disingenuous, passive-aggressive tone.
Why is Justin dredging up that one time eight years ago when Andre mistakenly called out a repo for infringing upon his employer's work (for which he publicly apologized five hours later)? Why is he harping on anecdotes from nine years ago in order to suggest Andre may have allegedly (gasp) expensed technology purchases and business meals to his employer? What does this all have to do with the current situation, other than unnecessarily stir the pot with a laundry list of old petty grievances fed to him by a bunch of anonymous contacts ('a lot of different people told me a lot of concerning stories')?
I think the author's close ties to Rails Core / Shopify employees is extremely important context for this post, especially since it's context that's been intentionally hidden by a neutral, unbiased framing.
Someone vibe coded a PR on my team where there were hundreds of lines doing complex validation of an uploaded CSV file (which we only expected to have two columns) instead of just relying on Ruby's built-in CSV library (i.e. `CSV.parse` would have done everything the AI produced)
Ask it to write tests, then let it run until the tests pass (preferably in a sandbox, far from your git credentials). It is quite good at developing hypotheses and tests for them, if that is what you explicitly ask for. It doesn’t have (much) ego, so it doesn’t care if it is proven wrong and will accept any outcome fairly if it is testable. Although sometimes it comes to the wrong conclusion and doubles down that the fact should be true so it prepares to write and publish a library to make it true
Sorry! Didn't mean to BS you. I've not come across a scenario where it hallucinated me with a non-existent library. Can you share what you were trying to do when that happened?
I wish I had the transcript. I don't, and I'm afraid that the passage of time has muddied the interaction to the point of uselessness (when it comes to listing specifics).
Craft coffee is a luxury item that isn't part of Japanese culture in the same way that it is in the west. In the early morning, when you're a salaryman trying to get to work as fast as possible, you get coffee from a vending machine or convenience store. Craft coffee is something to enjoy leisurely, which is why most specialty coffee shops don't open until much later than we're used to
Thanks. I guessed that. I got downvoted so I assume people think I am complaining. I am not. Just observing and curious as to why they open later I assume there are different rituals and I never found out. Thanks for replying!
> Our API is a Ruby on Rails application. For all public-facing models, we have added a `public_id` column to our database. We still use standard auto-incrementing BigInts for our primary key. The `public_id` is only used as an external identifier.
Their office has an entire team dedicated to physical security. If you're walking around by yourself and you don't have an employee badge, they find you pretty quick.
I’ve been trying to ask people a different question: sure, we’re more productive now but to me, the AI era is only serving to plunge us deeper than ever into producing more, more, more, faster, faster, faster. And for what? What’s it all for? I became a software engineer because I have a lot of fun writing code, thinking through and solving complicated problems, and experiencing the reward of seeing what I’ve built by hand working for the first time.
Do people really have fun managing a fleet of agents that generate the code instead? Or is it just the rush of producing something extremely quickly, much more quickly than you might be able to alone, regardless of how well (or poorly) it might work? For me, being able to move quickly was never the fun part.
It’s one thing to utilize AI to lessen the drudgework, the boilerplate, but I look at people who have gone all in on agentic development and it just really makes me wonder.