HN user

sasaf5

1,260 karma
Posts14
Comments401
View on HN
[dead] 14 days ago

Nowadays you don't just write an article. You ask Claude to write it for you.

"So the interesting question isn't whether personal hardware is coming. It's who gets to write the software that runs on it."

It's not that I don't like your point of view. It's that I can't stand AI slop.

I'd like to gently push back because this is a misconception that is worth untangling. It's not that no one is talking about it. It's that there's a genuine silence about the subject.

I have been using Emacs+git on termux on an Android phone for more than 5 years.

I don't even use a third party software-keyboard, I just use termux's special key bar. To set it up, add the following to ~/.termux/termux.properties

  extra-keys = [['TAB','CTRL','ALT','ESC','HOME','END','LEFT','UP','DOWN','RIGHT']]
This has been enough for using org mode in everyday life tasks, and I don't need to keep swapping keyboards.

I’ve seen employees spend days drafting documents that a free tool like Mistral could generate in seconds, leaving them 30-60 minutes to review and refine.

What I have seen is employees spending days asking the model again and again to actually generate the document they need, and then submit it without reviewing it, only for a problem to explode a month later because no one noticed a glaring absurdity in the middle of the AI-polished garbage.

AI is the worst kind of liar: a bullshitter.

Up to now, my attempts at doing what the author claims to be possible ends up in a broken piece of code that the agent only makes worse when asked to debug, and finally it wont even compile. There seems to be a threshold of difficulty above which the agent will go bug-runaway. I honestly haven't seen this threshold going up. If anything, it seems to be saturating.

Org mode versioned with git.

Every issue at work becomes an item in this org, and all information relevant to the issue goes there: emails, chats, code snippets, documentation paragraphs, etc...

It's amazing how clearer things become, and how quickly you can get back in action if the issue resurfaces a few years later.

It also told me that it had permanently disabled my Facebook account—an account that I’d had for more than 15 years, and that was my primary way of staying in touch with family and friends around the world.

You don't need Facebook for that. Write down a list of the people you care about and contact them with some frequency, at least on their birthday.

Early 2023, when everyone started using chat GPT for coding, I thought it would be a big boost because it enabled us to quickly employ a large number of people in a project regardless of language or framework.

An year into the project I am forced to revise my opinion. When browsing my code-base I often stumble in abstruse niche solutions for problems that should not have existed. It was clearly the work of someone inexperienced walking through walls in an AI-fuelled coding frenzy.

Having an oracle that knows all answers is useless if you don't know what to ask.

Also, I have seen several times someone "following their passion" and doing something that was not required by the business. The end result is a huge mess of overcomplicated things that doesn't do what was needed and no one else can fix.

Many times the business just needs a boring old solution for a tedious problem that no one would be passionate about, and it's normal to engage in that kind of grind.

I would change that advice to "do what you are passionate about, among the things that the business needs, and understand that sometimes you just can't do that".

On the other hand I have seen several devs who were just good at quickly tackling whatever was necessary at the moment and became very successful without ever showing a sign of passion for computing. For them it's just a craft and they go do some hobby after that.

The epitome of "no duplication's" failure is CMake. It subsitutes two duplicated build systems with a crudely unified version of both. What before were duplicated lists (tedious to maintain) become an algorithm (difficult to maintain). Add to it the plethora of other build systems and you really have something that has failed its unifying mission.

I would prefer fewer patients per doctor then. It seems that the problem is due to the limited supply of doctors. In both countries where I lived, supply of doctors was artificially limited by regulation.