You wanted this feature for years. You understood the problem, but the amount of time that it would have taken to properly implement and test it held you back from doing it. Obviously, anyone else who wanted this feature came to the same conclusion.

This new tool reduced the amount of time that it would take. So you used the tool. You used the tool to bring the feature into existence, checked the tests, and took enough time to ensure that it was good. You didn't lie about your contribution in the PR, and the maintainer deemed it acceptable. And now everyone has this feature!

When you eat a strawberry do you feel like an impostor for not growing it yourself?

spend all day talking to people (except it's LLMs) and not sure if you accomplished anything, but people seem happy

The plus side is for your personal things like this you don't have to use it of course!

We had 8 people on that team. The entire scope of what we did for a living was replaced, mostly by 2010 or so. My role was made redundant by improving storage performance and capacity. We had a few TB and lots of blob data. I cared about where data was stored from a disk geometry perspective. Today, I could smoke that infrastructure with my MacBook.

The other DBA roles also mostly moved on. ORMs automated a lot of schema work. Engine optimizations eliminated a lot of the operational tuning work that went on. Most of the other stuff moved into adjacent developer roles.

Most places have very few DBAs today. That startup today would have had zero.

I think the author is being way too hard on himself. He defined a problem, worked with the computer to “scratch the itch” presumably QA’d the result and sent it upstream. That’s valid and useful. The method is different. But the work is solving the problems - and just like crazy kids solved problems with VisualBasic and the real men wielding C++ shook their heads, the AI tools are going to produce alot of shit, but also solve alot of problems.

At the very least the change has made me reduce the amount of time I spend here. But I'm still a bit bummed about it.

I built a TV OS slideshow app for both photos and videos (as far as I know all the apps just go through photos).

I have no experience in Apple OSes development and in the past it would had taken me at least a week to just read enough documentation to get started.

Now? It took me 3 hours of iterating with an LLM to start from scratch developing and publish the app.

AI will click as another tool in the toolbox.

The quality of a contribution is not a function of how much you learned or grew while you made it. Learning and growth are part of your compensation for making the contribution. The author is not a fraud for not learning anything. If anything, it seems like they should feel short-changed!

When voluntarily making contributions to open-source projects, everyone should of course feel free not to use AI tools if they want. However, I would argue that using AI tools is a valuable skill itself, and worth practicing.

But now post LLM coding agents, its not at all that. Nothing about programming for money resembles artisanship.

It might be time to try sewing wallets or something...

They absolutely do care how software is built. They just don't weight the factors the same way you do.

Product companies exist to convert software into money by providing utility to users. There's really no part of the transaction that meaningfully involves how much fun you're personally having building it.

> This PR adds support for embedded Ruby (ERB) which is commonly used in Ruby on Rails projects. Note that I used heavy assistance from Claude Code and tried to ensure it didn't generate slop to the best of my abilities. All tests are passing and I also visually verified the end result which looks solid to me.

> Here's a screenshot that was generated by building the Chroma CLI with the ERB lexer and running it against the test data file with chroma --lexer=erb --style=monokai --html lexers/testdata/erb.actual

Well I’m sorry you feel that way, impostor syndrome is tough to deal with already without AI.

You seem to be driven by understanding and you have a great tool to learn from here if you make an effort over time to grasp the “slop” you’re throwing to the wall. Be curious, ask why several times and explore guilt free over time when you are in the right mindset.

I’m glad you got something useful out of it this time and also not everything you do with AI has to be useful or a final “deliverable”, it can also be a great toy and window into more understanding.

you will get a proper sense of ownership and of at least having put some work into not delivering slop, though of course there might still be subtle issues that only the people familiar with the codebase would catch.

As long as you understand it before committing, you own your version of it now. There's no way in hell I'd waste time playing the slot machine. I am perfectly capable of writing the exact missing parts I need to integrate and move on quickly. How is this any different from SO copypasta a decade ago? Just like that wasn't always the right tool for the job, neither is "AI".

This sounds like a completely different problem than AI usage itself. My time is most valuable making decisions for the project. Yes, the vast majority of those decisions involve the code for the implementation details, but I just need clean simple code that does the job and that anyone or anything can easily change later. The AI doesn't always give that to me, and sometimes neither do other humans. That's why I'm employed. That's what it really means to be a maintainer and contribute.

> I felt like I was flinging slop over the wall

> my impostor syndrome got worse

> thanks for dealing with my slop, Alec

> I have never felt like a bigger fraud in this field

I'm the most senior software developer in my company and I sit in the middle of the room with my screens open to everyone, and I use 10x the average tokens. I've felt like an imposter when I was barely measuring up against the intellectual giants in my first jobs. It's a feeling, and it has nothing to do with you, your work, or your automation tools.

Secrecy leads to bad patterns of practice. AI doesn't make good programmers bad, or bad programmers good.

Addressing the lack of fun:

> I’m privileged that I get to have fun at all in my line of work

> this has sucked out all of the fun

Split your coding in two: The part that gets done quick, and the part where you personally care about every line of code.

This was always a problem with commercial programming for me: Employer only cares that it gets done, I care that it's good. The tension is necessary.

There are aspects to your style of craftsmanship that the AI hasn't encoded yet.

I choose to embed those in templates and agent skills, but you can also just keep writing that code yourself.

Addressing productivity:

> I would not have the mental capacity or skill to create a pull request like that without AI tooling

> Now that using AI is a normal expectation at work and how I’m evaluated in performance reviews, I suspect that this fraud feeling will only grow

I think that's why using it is so unavoidable: It does increase productivity and lowers cognitive strain, at the cost of yolo.

I don't know if "fraud feeling" is referring to your impostor syndrome, and you want to get rid of this: deal with the feeling, it's just part of your growth as a person. Or if you're using fraud as a loaded term to devalue AI use in programming for ideological reasons: Can't help here, I don't have a problem with it.

Addressing craftsmanship:

> no matter how big the impact, I feel empty

> I still contributed something of value

> I perhaps tied my identity too much to my career

> I’m not the greatest engineer, but I’ve always worked hard

> I care about the craftsmanship of my code

Your interest in the details of your craft will disappear eventually.

Keep it up as long as you care, it's fun.

When you're ready to see yourself as something else, it will naturally fade.

I've been an aspiring team lead without a team for a long time. Now I have a team of robots (and incidentally a team of people), and it feels natural. I still code in my spare time, but not for productivity, only when I have to or when I want to have fun.

For me, I've slowly switched to wanting things to exist rather than wanting to make them. That helps swallowing that I don't code as much any more. (I mean, I still recreatively code 2-3 hours per day, but it's far from the 8-16 hours that have been the norm in my life.)

If it helps: It is probably good for your physical well-being that you don't have to sit hunched over as much.