Context engineering is a critical part of being able to use the tool. And it's ok to not understand how to use a new tool. The different models combined with different stacks require different ways of grappling with the technology. And it all changes! It sucks that you've tried it for your stack (Elixir, whatever that is) in your way and it was disappointing.

To me, the tool inherently makes sense and vibes with my own personality. It allows me to write code that I would otherwise procrastinate on. It allows me to turn ideas into reality, so much faster.

Maybe you're just hyper focused on metrics? Productivity, especially when dealing with code, is hard to quanitfy. This is a new paradigm and so it's also hard to compare apples to oranges. Does this help?

So your take is that every real software developer I know is simply bad at using this magical tool that performs on the level of mid-senior level software engineer in the hands of a few chosen ones? But the chosen ones never build anything in public where it can be observed, evaluated, and critiqued. How unfortunate is that?

The people I talked to use a wide variety of environments and their experience is similar across the board, whether they're working in Nodejs, React, Vue, Ruby, PHP, Java, Elixir, or Python.

> Productivity, especially when dealing with code, is hard to quanitfy.

Indeed, that's why I think most people claiming these obscene benefits are really bad at evaluating their own performance and/or started from a really low baseline.

I always think back to a study I read a while ago where people without ADHD were given stimulant medication and reported massive improvements in productivity but objective measurements showed that their real-world performance was equal to, or slightly lower than their baseline.

I think it's very relevant to the psychology behind this AI worship. Some people are being elevated from a low baseline whilst others are imagining the benefits.

People do build in public from vibe-coding, absolutely. This tells me that you have not done your research and just gone off of general guesses or pessimism/frustration from not knowing how to use the tool. The easiest way to be able to find this on Github is to look for where Claude is a contributor. Claude will tag itself in the PR or pushes. Another easy way to that I've seen come up for this is there is a whole "BuildInPublic" tag in the Threads app which has been inundated with Vibe coding. While these might not be in your algorithm, they do exist. You'll be able to see that while there is a lot of crud that there are also products being made are actually versatile, complex, and completely vibe-coded. Most people are not making up these stories. It's very real.

Of course people vibe-code in public - I was clear that I wanted to see evidence of these amazing productivity improvements. If people are building something decent but it takes them 3 or 4 times as long as it would take me, I don't care. That's great for them but it's worthless to me because it's not evidence of a productivity increase.

> there are also products being made are actually versatile, complex, and completely vibe-coded.

Which ones? I'm looking for repositories that are at least partially video-documented to see the author's process in action.

Gosh, it's almost like a proper IDE has synonymous features with LLMs

the good news is that you can self-host bitwarden pretty easily and so it doesn't have to be a hassle/risk

Grandma is self-hosting what???

I am going to be honest, Grandma is already compromised.

that's where you come in sonny

This.

Grandma, and Uncle Rob, and your cousins, and anyone else you have a long standing relationship with, can use your VaultWarden instance if you let them.

But! You now get to maintain uptime (Rob travels and is frequently awake at 3am your time) and make sure that the backups are working... and remember that their access to their bank accounts is now in your hands, so be responsible. Have a second site and teach your niece how to sysadmin.

Yeah, they have the world class Salesforce engineers there. One of Google's Salesforce's last tech leads wound up becoming the Director of the proprietary Salesforce language Apex.

You can also always have it create design docs and mermaid diagrams for each task. Outline the why much easier earlier, shifting left

That's essentially what I do, but that doesn't (and cannot) entirely solve the problem.

A major part of software engineering is identifying and resolving issues during implementation. Plans are a good outline of what needs to be done, but they're always incomplete and inaccurate.

Used to be? What changed?

People started sending a lot more texts and making a lot fewer phone calls. And you can only piggyback so many text messages on the call packets.

We don't use 2g GSM anymore.

What exactly are you basing any of your assertions off of?

The same sort of rigorous analysis that the parent comment used (that’s a joke, btw).

But seriously: If you find yourself agreeing with one and not the other because of sourcing, check your biases.

Search for "daylist" on Spotify and it'll come up with exactly that

So this will also probably be another seemingly clueless question, but after reading up on air gapped computers, how would that help with the new hash?

Would you mind elaborating on how WordPerfect in 1992 is better than modern day Google Docs?