It’s okay, we know you’re busy with those Epstein files.

All I’ve got is a nubby yubikey nano

What do they do with the daddy computers? All of mine only have female ports.

Totally disagree. Your position is way too overly simplistic and naive.

An engineer only builds a bridge as strong as it needs to be, and likewise I “vibe code” things based on how few fucks I need to give.

I’m experienced and can review the output for sanity and completion. I can test it, I can rewrite it, etc.

Stop looking at vibe coding as doing the whole thing, it’s more valuable as the glue between things, or to create scripts tools that make you more efficient.

And you can vibe code entire apps that basically just work these days. You probably don’t want to maintain those apps but thats a question of lifecycle planning.

It is so much faster to vibe code an API integration and a suite of tests than I can write. It’s faster to write a functional jq or bash script.

But it’s also much much much worse at doing data viz or writing pandas code because it’s trained on 10,000 shitty medium blogs.

You really have to know what you’re doing and what the model is doing, but it is not universally trash.

And if you don’t believe me, put $20 into the Claude API and install Claude Code and ask it to build something.

That’s kind of just semantics and the frap the Trump admin is doing to say it doesn’t exist.

The FBI definitely has a file on this. They have the contents of his vault, his log books, etc.

Everyone on the Epstein list deserves to face open justice.

If he’s innocent he could have just released the list and proven it to the whole world.

I don’t think anyone would even trust that now.

Well it is owned by Oracle now

I don’t know rust, but for example in Swift the type system can make things way more difficult.

Before they added macros if you wanted to write ORM code on a SQL database it was brutal, and if you need to go into raw buffers it’s generally easier to just write C/objc code and a bridging header. The type system can make it harder to reason about performance too because you lose some visibility in what actually gets compiled.

The Swift type system has improved, but I’ve spent a lot of time fighting with it. I just try to avoid generics and type erasure now.

I’ve had similar experiences with Java and Scala.

That’s what I mean about it being nice to drop out of setting up some type hierarchy and interfaces and just working with a raw buffers or function pointers.

I actually do like that C/C++ let you do this stuff.

Sometimes it’s nice to acknowledge that I’m writing software for a computer and it’s all just bytes. Sometimes I don’t really want to wrestle with the ivory tower of abstract type theory mixed with vague compiler errors, I just want to allocate a block of memory and apply a minimal set rules on top.

Reminds me of java

I have Toolkit toolkit = Toolkit.getDefaultToolkit(); seared into my brain. Then there were the bean factories…

Oh wow, I didn’t know you were having these problems with him.

But since you’re in my office let’s start you on a PIP and I have to write you up for this hostility against a fellow employee.