Astra writes a lot of security bugs too, the upside is that if you also use it to review the output it will find a lot (most?) of them.

This is one of the least talked about and most useful features in any harness I would say, the review feature. I have never not found issues (either security or implementation) running it, no matter the code base or language.

Most, not all, are just delivering more bad stuff faster. I personally also think I deliver more good stuff with AI, but the products I use are just getting worse daily it feels like. Just the other day I noticed Slack had installed some disgusting menu bar icon for their AI bot, without asking, just to take a fresh example of this.

I wouldn’t say poor, fishing was the backbone for over a thousand years and generated its fair share of wealth, so did timber. Seafood is still second after oil, even if oil of course is much bigger. Norway benefits greatly from being a massive country with a small population and enormous natural resources. This makes governing far simpler compared to many other countries, and the culture is of course vastly different too.

I’ve only ever been to Lofoten but it was lovely, I think that’s how humans are supposed to live, too bad I can’t afford to move there.

Wait are you from Norway or?

Sorry, I have that image due to, just the image of a "poor" fishing country. Now we envy you and I heard all my life that we in Sweden are Norways poles/polacks due to cheap labour from Sweden.

That said we in Sweden where extremely poor too, see the famous book "Utvandrarna" for how it could be so miserable that people left.

Now we are the ones causing issues - "det svenske tilstander"

Well, I say "we" but these are not the Kalles Kaviar looking people. It could get to that point though...

This was the case at a previous job. Someone read some "state of devops report" or similar BS where they wrote that good teams ship often. They took from that it was shipping often that made good teams... And as a result we had some contrived deploy process on Slack with buttons and emojis and what not to deploy. Not a single customer saw any value out of this of course, because shipping something is not the same as shipping something valuable.

So I guess releasing 60 times in a working day proves that you're part of a good team /s

In a thousand years when the robots try to figure out human history they will short circuit when they try to solve the naming conventions of LLMs. Is it a natural law that the naming should be completely useless? Is the Fibonacci sequence hiding in here somewhere and we just can’t see it yet…

For me even just the config format is such an upgrade that it was worth switching. Just a simple text file I can backup anywhere and actually read without clicking in a tabbed GUI where I never seem to remember what goes where. iTerm2 still has that weird thing you have to export right?

It’s subjective. The config format is a downgrade for me. The only settings I change is the color theme anyways. The terminal default should work well. It takes four seconds to use the mouse to open the theme config and pick a theme. It takes at least five minute to find the config file location, the syntax for the config file, understand whether it uses fs events to auto reload, and then decide to include or exclude it in your backups. I don’t intensely customize my terminal emulator so it’s not worthwhile. On the other hand my Emacs config is more than 500 lines long and that’s worthwhile.

I think you hit upon what bugs me about file config. It's not the file, it is having to find it, find the docs, find the syntax, find the keys, find the values, etc.

If it was always in a standard format, it wouldn't be a problem. Something like dconf, without the poor design.

OK, that may be true (and yes, iTerm still uses weird plist xD) but... On the day to day basis I don't care about config file. I mostly use one OS, I don't do reinstalls (had MBP from 2013, then after switching to MBP M1 moved the files and configs _once_) so having nice and readable config doesn't matter at all.

Having to search for some obscure configuration names and options is simply getting in the way.

For that reason I stayed away from Zed for ages - it is a fine editor but tweaking it options without even rudementary settings GUI was just super-meh.

I do hope that Ghostty will go the same route and they will add something that would help manage the simple config options (backed by the config file) without having to deal with purely-textual form)

This... It's weird how companies and people think adding something is the same as adding value. Feature creep was an issue even before AI, now we see one worse feature being added after the next (does anyone even know all the touch controls of iOS or even macOS, as an example), with some expectation of that there will be money coming in because of it.

I benefit greatly from AI myself, but I use it to augment my capabilities, not as a slot machine for building things nobody will ever use, which seems to be the norm based on the products I use.

I much preferred the fake photos—as in not photos of food served at that restaurant—than the AI generated images of food that doesn't exist at all on menus, as an example. I also hate that Etsy is now mostly an AI-image gallery.

A one-shotted POC can also put you straight into the very wrong direction, with a very high degree of certainty.

I also prefer doing a POC, but it's not without risk, especially if your stakeholders are just a bit too eager. Another problem I've seen is that a POC can hide complexity, so a lot of weight is on you as the author to do the due diligence before and bring that along.

This is an often underrated problem. I used to work at a company where we would hold demos every other friday, with drinks and nibbles. We would put a lot of thoughts into what we were going to present, and were really careful about the messaging, because execs and sales were watching.

The last thing we wanted was for an "Isn't it neat?!" hacked-together demo to be mistaken for something shippable, if workable at all.