But those moments are the exceptions. In my everyday life, when I need to charge _anything_, except maybe for the laptop itself, I just look for a charger with USB-C and it works. It maybe faster or slower depending on everything you just wrote, but it works.

On a side-note, when I take the charger of my laptop, it can charge absolutely everything.

So yes, that's a true and honest improvement.

So the author is telling us they're having more work- and screen-time while on the road. Great, that sounds like exactly what we need...

To examplify that, I've asked Fable to fix a repository that had a number of submodules and symlinks and this and that (don't judge). As I was giving it more leeway, it ended with this output:

> .git is deleted. That was my doing, and it was exactly the kind of mistake it looks like: a relative-path rm -rf executed after the shell's working directory had been reset to the repo root, without re-checking pwd first.

Not that the error is irrecuperable or critical in any way, it's fine, but it could do so much worse on production systems without proper guardrails. It just shows that harnessing not only protects your systems from the AI agents, but also protects the agents against themselves, since they also demonstrate some "ooopsie" moments.

Comments URL: https://news.ycombinator.com/item?id=48509874

Points: 4

# Comments: 6

The director then clearly advised that they should use the complicated way because that's how you get published: not because you're clever, but because your solutions sound complicated.

It resonates perfectly with your comment and it's an unfortunate reality that most people don't bother for beautiful solutions and praise complicated processes. That's how we neded up with bureaucracy, probably :D

I asked Fable to digest some test logs to help me figure out a situation, but I had launched VSCode without activation the virtual env in the terminal first. Consequently, the tests failed to run.

And then:

Because the tests failed to run, Fable attempted to fix the test execution to no end, doing everything it could to get them to work. I had to stop it when it started to pollute my system with manual installs of packages.

At least I'm glad there's a guardrail to not circumvent or bypass sudo, because I'm convinced we would have ended up there.

A coworker made the joke that with enough tokens, Fable would try and solve any programming problem by building Linux from scratch.

It's hard to describe the feeling of seeing intelligence being delegated increasingly to AI. If that's not a pivotal moment, a revolution, I don't know what is.

When I read "an alternative", I assumed feature-parity and API compatibility. But what I found out was entirely different and much more interesting.

I'll give it a try, thanks for sharing your year-old work!

> "What happened the last time that everything changed?"

Honestly, I'm glad we hear more of the commoditization of AI, and I hope that the comparison of AI with water or electricity will become mainstream and that the states (as in nation states) will understand that sooner rather than later and act accordingly.

The facts that this article needs to list the pros of HTML over MD, like inreraction, visual density, etc, is weird to me. Maybe the ahdience is not tech-savvy people but I read it as an unnecessary word salad.

After a bit of tinkering and understanding the idiosyncracies of Typst, the joy of having reliable, consistent, beautiful, data-driven resumes and cover letters is not measurable. It basically lifted any barrier to applications, while whatever I had before I had always considered a burden.

On top of that, I can add hiring process data directly to the yaml file to run further analysis.

Can LaTeX do this? Most probably, but the learning curve is the difference.

I'm tempted to give it a shot, with the extra bonus that I've never dabbed with a fedora-based distro.

Just use curly brackets and boom. LISP 3k.

You're welcome.