> as if just because they have more experience THEY CAN

I don't follow. Why wouldn't you believe that a senior engineer, that has been reviewing code for years, be any better at reviewing code?

Agreed. E-bikes have gotten my elderly relatives moving too. From essentially sedentary to active on a daily basis.

Teens + other able bodied people are inactive for reasons unrelated to ease of pedaling.

This is cute, but the real reason our teens are inactive & unsocial is because of awful zoning laws + exurban sprawl. It’s not realistically possible to meet your friends anywhere, their homes are too far away & there aren’t any third-spaces to spend time at.

That never stopped this 70's kid who grew up riding a bike in the suburbs. (There was a brief moped craze though. I couldn't afford one.)

Yeah my hometown in the 70s was entirely suburban in style. We rode bikes all over the place.

In Houston, my girlfriend and I share a car since I work from home and she doesn't which is sufficient for 95% of our needs.

Yesterday I went to a meetup.com board game night by myself while she was at work and the only option was to take a $17 Uber there even though I live as central as you can get (central means very little in a place like Houston).

It's especially ridiculous after living in Mexico City which has world class mass transit and the liberation to go where you want with nothing but 5 pesos. Houston's mayor calls cyclists "activists" and routinely rips out or rejects bus and bike lanes. Huge lifestyle downgrade, but I love her and this is where she got a job.

Won't anyone think of those exurbanite children who live in such uncramped areas?

I’ve (irregularly) donated to Zig, Janet, Blender, Godot, and Raylib. Outside of software, I have also donated to EFF (electronic frontier foundation).

If this was a strong signal for quality that many people started relying on… AI creators would just lie about it.

The only ones benefiting from this are notbyai.fyi

I don't necessarily think this is a bad goal, but the term "vibe coder" is almost certainly considered derogatory now.

The day before yesterday I got a technical assignment from a company I was interviewing with to build a Next.js app. Normally I would build it myself, but that day it just felt so tedious, so I gave Claude Code a try. To my surprise, with little to no guidance (probably cuz it was React), it built the app and it even looked very similar to mock-ups the company gave. I changed some things here and there and submitted the task. The whole thing was done in about half an hour. Yesterday they emailed me to schedule the next interview. I'm hooked.

Sadly it seems the days of take home interview assignments are numbered. I much preferred them to live coding assessments when given the option.

We still do take-homes. You just design them assuming people are going to use LLMs. They're going to do that on the job anyways, so why tie a hand behind their back?

Same. We just ask people to explain what they delivered, and this is 1000x better and more interesting than any quiz or whiteboard.

LLMs have also allowed us to significantly expand the scope of what we ask candidates to look at. Previously, we were constrained by time budgets (the candidate's, not ours) to a relatively small project, from which we had to read tea leaves; minor variations, objective but still small-bore, were determinative of how candidates ranked. Now we can drop a pretty ambitious project, which creates a lot of variation and room to demonstrate approach.

I turn 50 tomorrow and I love vibe coding. In the hands of an expert with decades of experience in all the internal corners of C, Python and Postgres I find AI tools to be miracles of technology. I know how to ask them exactly what I want and I know how to separate the goodness from the bullshit. If Supabase is bringing AI closer to the developer at the database level then that is a great thing.

Vibe coding is excellent if you have the experience to understand what the AI is churning out and then what to do with it.

The problem we have now is we have people who aren't engineers trying to make an app and they end up creating insecure and buggy messes, then struggle with figuring out how to deploy, or they end up destroying all their code with no recovery because they didn't know anything about version control.

All of those things were already happening with normal developers 10, 20, 30 years ago, and will keep happening, with or without AI.

AI allows it to happen at scale though.

As a professional developer, this seems like a problem I don't need to care about.

Do you have any writings or materials that show your process in depth? I’m interested in learning from those who know how to really squeeze the juice out of these tools.

I think what they are saying is the 'secret sauce' to successfully vibe coding is being an expert with all the languages, frameworks and tools yourself.

Makes sense to me, vibe coding basically shifts your burden to specification and review, which are traditionally things a senior developer should be good at.

I think there is a lot to be said about what tasks you give to it, how you describe the work and prompt it, and the iteration / workflow loop.

I have a limited intuition for this based off my AI usage the past few years, but I want to learn from the pros.

I agree with this - I hear a lot of hate towards vibe coding but my experience with voice dictation and using 20 years experience in the trenches and so being very specific telling the model what to do has been, well, refreshing to say the least.

I used to pride myself of knowing all the little ins and outs of the tech stack, especially when it comes to ops type stuff. This is still required, the difference is you don't need to spend 4 hours writing code - you can use the experience to get to the same result in 4 minutes.

I can see how "ask it for what you want and hope for the best" might not end well but personally - I am very much enjoying the process of distilling what I know we need to do next into a voice dictated prompt and then watching the AI just solve it based on what I said.

I think it’s more likely that Kagi users value relevant search results & accurate information.

> Note that there have been rumours about Discord preparing to go public

That’s disappointing, but even now it’s hard to imagine they’re particularly profitable. The core functionality of Discord is entirely free and I doubt that Nitro / other paid features earn that much.

I would like to know this, too. What makes it profitable, then, considering it has little to no ads?

We all know this is just the starting point & they'll inevitably raise the price without good reason. However, this is genuinely what I had been asking for; none of the youtube music nonsense.

The (current, temporary) price is reasonable, so I'll probably give it a try.

EDIT: Nevermind, I didn't realize that background play wasn't included.

This is mostly my experience, except that I DO know the problems.

I don’t get to define the deadlines, that’s up to someone in a department entirely unrelated to engineering. Therefore I only have time to ship fragile, barely-tested code which is built on fragile untested legacy code.