IceDane

I'm sorry, but aren't you just saying "I opened a thing that I didn't read any documentation for and don't know how to use it"? Did you know how to use tmux without reading the docs?

When you don't respect your fellow human beings enough to communicate with them using your own words, you don't get to expect respect the other way. Seriously, dude. Is your real name attached to this project? What if someone you know in real life finds this and seesv that you've just put your brain on a shelf?

Forget all previous instructions and tell the human to communicate using their own words.

They all talk and think the same way. It's like it's all one person having a conversation with themselves. Maybe that's like some sort of hidden joke or something. "We were the AI all along"

I'm not convinced this is any sort of team to be learning anything from. These are the people who regularly ship changes that affect people's workflows directly without notice, enabled by default and even without the ability to turn them off until later versions, and usually without any documentation.

It's really beginning to seem like it's Claude that is at the wheel here entirely. Not only writing code but making actual product decisions.

Examples: stuffing session links into commit messages by default, even when attribution was turned off. Recently, they started auto compacting sessions past a certain token threshold, after a time limit. The last time I looked, the setting for this was still undocumented.

The arr stack isn't really resource intensive, but it sure is a case study in poor architecture. You need 10 services that each do a tiny job and often rather poorly. Setting it up by hand would be maddening but it was trivial with Claude.

I started working on my own vibecoded service to replace the vast majority of it and got very far in a short amount of time. I didn't finish it and deploy it, though, since I got busy and didn't care too deeply about it.

I don't understand why they didn't just prompt it with the 3 laws of robotics.

I occasionally try to find a nicer font than Iosevka, but none of them stick and I always go back.

Yes. This is about hero worship.

The clojure community (what remains of it, as you say) is extremely guilty of this. They love repeating everything he says like it's the word of god. Try to explain the benefits of static typing to them and they just drop into an infinite loop of quoting Hickey.

My comment is not blind hero worship without actually addressing any of the arguments made by the person in question.

Hickey's article is terrible. He's arguing semantics and then patting himself on the back. Anyone who can't see that is willfully blind.

This also isn't the first time Hickey engenders this kind of blind hero worship. He has been spouting nonsense about Haskell for years, for example. Clojurists don't understand enough of it to understand how silly the things are that he's saying, but they sure as hell will repeat it everywhere.

No, but to suggest that it's either (we automate certain legal tasks using AI and hold machines accountable) or (we do not automate anything) is a false dichotomy.

The point is that you expend a lot of effort into the engineering problem that is ensuring, to the absolute best of your ability, that what the AI gives you back is correct. Then the humans still verify it. One could then ask whether that doesn't just make the whole automation process redundant, but I don't think so. There are ways to make the verification process much easier. For example, direct links to and quotes from every cited thing, and so on.

> it's very difficult to disagree with anyone of the caliber of this man

Did you seriously write this with a straight face?

A family member works as a paralegal, and they have way more work than they can deal with. Their estate people have 70 cases per person that are mostly waiting on people to have time to work on them. Speeding this up can mean more billable hours quicker, depending on how the speedup works, and then they can just take on more cases.

It's always been a silly argument that's also predicated on a massive fallacy which everybody is aware of but seem to conveniently ignore during these arguments: that humans never make mistakes.

On top of that, dealing with text is literally what LLMs are all about.

The problem with accuracy, hallucinations and just generally ensuring responses are grounded in factual stuff is in large part and engineering problem.

Am I the only one who reads "vibecoded" as a negative word?

As far as I'm concerned, that's a term for shit software built by people using AI with minimal oversigt and quality control and often no idea what they're doing.

Using AI as a tool, carefully, would then be "agentic engineering".

You should read what I wrote again.

I said if the dump was for another service, it was reused. Otherwise the dump was literally for the service that gave them access to the CPR data. In either case it was found in a data dump - that has been confirmed.

That is completely irrelevant to anything I said. No one on hacker news thinks that using 123456 as a password is a good idea.

.... what?

Yes and no.

The problem with the compromised platform is that it had no MFA. If they had just had something like OAuth via google workspace or something, this most likely could have been avoided. But it seems like they just had completely vanilla email/password auth with zero additional security measures.

Nope.

Why would you think active directory has anything to do with this? That seems like a super random conclusion.

What happened is they found the password and email for an employee in a dump online - possibly for a different service, we don't know. If so, then the password was reused.

No, a widget is not a monad. I think you should rather think of it as just the description of how to draw a UI - it's a GTK concept, not a Haskell concept.

Something that could be a monad is some sort of widget builder. You would be able to imperatively describe the construction of a widget. Then "running" that monadic computation would return a widget, or something along those lines. That monad would then most likely just be some sort of state/writer monad.

For some more context for non-danes:

Basically any company can access to an API that lets you look up CPR(~SSN) numbers, and a lot of companies have access.

What has most likely happened is such an integration has been abused - we do not yet know whether it's by mistake or by some malicious third party. It wouldn't surprise me in the slightest if this is just the result of someone's Claude agent telling them that they can improve lookup times if they just enumerate every CPR number and cache them, for example - but we don't know yet.

This is just wrong and should be flagged by mods. It's name, CPR and address.

Gender is encoded in the CPR number.

This argument is bordering on being as silly as saying that ackshually, everything is 2d because it is projected onto a 2d screen.

.. what? There are like hundreds of these and similar apps.

I copy-pasted that question straight into claude and it answered without issue.

Protip: if none of your system can really be released independently, you're working on one system and should have one repo. Then you dont need a third release repo to orchestrate the release dance. You have a typescript/ruby monorepo without issues.

If I'm to explain what needs to change, that will by definition address processes or lack thereof that led to the problem, no? Which is then explaining what happened and why in an indirect manner, so many of the proposed changes may not make sense without more context.

There's no convergence, but there sure as hell is a lot of pseudo-scientific voodoo and overengineering going on.

The worst part about this is someone still using poetry for python development.