Nostr Web Client

Ignore vibe coders, when they tell you what their software does. They don't actually know what it does. They also have no clue how computers work and networks function. They couldn't design efficient and effective algorithms, if their lives depended on it.

They say they tested it. They're good testers.

No, I am a good tester. And part of being a good tester is...

Knowing precisely what the software is meant to do.

Knowing how computers work.

Knowing how networks function.

Knowing how to design efficient and effective algorithms.

The jokes on you:

Good testers know what the software does, better than the people who coded it.

Also, be honest, the AI writes the tests, too, doesn't it? They've "reviewed" it. Except that it's also code. So, no, they didn't.

This is like purchasing food from people who can't tell you what the ingredients are or how it was produced. It's usually going to turn out fine.

Reply to this note

Please Login to reply.

Discussion

, 5mo ago

You sound like a new York cab driver complaining about driverless technology

Silberengel 5mo ago

You sound like someone who can't cook.

, 5mo ago

🤣🤣🤣

Nunya Bidness 5mo ago

When vibe coding collides with sheer experience, the world will melt.

This will take much longer than we think and the effects will be much larger than we can imagine.

nostr:nevent1qvzqqqqqqypzplfq3m5v3u5r0q9f255fdeyz8nyac6lagssx8zy4wugxjs8ajf7pqqswkskyawtcxhckr3wwmfk2kz9k0zy6vxj0yz3v9fwdt7uxaeqjl8sw7umnr

The Fishcake (nostr.build) 5mo ago

People lacking the fundamentals can never achieve greatness, only mediocrity

Laeserin 5mo ago

We shall pray that they achieve mediocrity.

The Fishcake (nostr.build) 5mo ago

🤞🏻

Sebastix 5mo ago

💯💯

Silberengel 5mo ago

They take pains to sandbox the AI, but the resulting code is often not sandboxed and it's running on your localhost.

It will hallucinate entire libraries and then not find them and magic one up that does what-the-fuck-evah, that you probably didn't even need. (It might have known they aren't there, and this is just its preferred method for messing up your code base.)

It creates complex solutions to simple problems, and includes all sorts of bizarre shit in there because... reasons.

And so on.

Oh, let's just track this variable for performance and then upload that dataset to the cloud to...

And if you ask it why it did that, it'll say,

I didn't do nuffin.

Tekkadan, ゲロゲロ! 🐸 5mo ago

😥 what did I do wrong this time?

Sondre | satoshiconsult.com 5mo ago

👏

7fqx 5mo ago

I also suspect a lot is basically immediately abandonware, unfortunately.

Silberengel 5mo ago

Almost all of it. Great for prototyping, or for setting up a scaffold for a new project.

ᴛʜᴇ ᴅᴇᴀᴛʜ ᴏꜰ ᴍʟᴇᴋᴜ 5mo ago

scaffolding and starting writing tests and translating code from other languages, and writing tedious and simple algorithms that are well established, especially on a specific data type are the things i mostly do with a coding agent. i will probably use it a lot to scatch together the beginnings of UI designs as well.

Silberengel 5mo ago

We have more and more design patterns and other architectural concepts, that we're manually adding, and then it's easier to expound upon those, than AI code stuff.

So, the code-base keeps shrinking.

Silberengel 5mo ago

Can also use more defensive and reverse-algebra logic and cut out most of the conditionals and validation.

That's always incredibly satisfying.

ᴛʜᴇ ᴅᴇᴀᴛʜ ᴏꜰ ᴍʟᴇᴋᴜ 5mo ago

yeah, i do a lot of that sort of stuff too. another thing is strong typing lets you prevent incorrect things from even getting past the compiler, like fixed size arrrays and creating derivative types of base types so only correct ranges of values are available to the caller. saves a lot of mistakes.

dynamic typed languages are so easy to create bugs that hide forever. another one is variable shadowing, most go programmers are constantly using the allocate-and-assign := operator all the time for everything and explicitly specifying return values. those two also can create hard to find bugs. i avoid them altogether by named return values and short functions with "naked" returns. my IDE also always shows the function signature at the top when it's scrolled down part way in so the return values names are always in front of me.

Silberengel 5mo ago

Well, that's the Rust advantage, I guess. I have barely started writing Typescript and I already sort of hate it.

ᴛʜᴇ ᴅᴇᴀᴛʜ ᴏꜰ ᴍʟᴇᴋᴜ 5mo ago

rust is full of expressive constructs. overflowing. i'd sooner learn typescript than rust, the worst of typescript is objects and inheritance. i've seen enough of how it works and how ugly its syntax is. i mean, the whole thing of the last statement's return value being the return for a function is just stupid, though not entirely stupid.

all the stuff that gives hints to the garbage collector is way too arcane. yes, rust has a fucking garbage collector. this is one of the biggest lies of Rust evangelists. IT HAS A FUCKING GARBAGE COLLECTOR. it's a retarded one, that you have to give exhaustive, explicit instructions how to manage the memory of everything. you can mess that up pretty easily too but seriously, having to say "i'm just borrowing this, will return at end of function" is so lame compared to a smart GC that uses escape analysis during compilation to generate those hints for you.

there's a lot of things that these supposed "expressive grammars" make "easier" but they actually just end up making the code far more complex to understand and read. they create a very idiosyncratic idiom very easy to create for programmers and that's bad for the poor bastard that comes afterwards, who then has to basically learn a new language.

satCummins 5mo ago

Sounds like the virus tests that test for nonexistent viruses that then become cases that then result in scamdemics that then result in clotshots that then result in deaths that then are blamed on non existent viruses.