I hate that some people started to implement semantic search everywhere without option for user to opt out. I want fuzzy search first then I might switch to semantic search if I feel like it. If I type a phrase and get results that don’t match it in any way, I am getting annoyed.

Rant off. Not really related to the article.

It depends.

If you’re SaaS vendor you should give troubleshooting information to your support team skipping the user. User should get “our support team received the error” and support should handle it directly.

“Something went wrong, try again later” is also acceptable but only if support team gets info about it and user really ca just try later.

I have approximately zero confidence that if I see an error message that says "our support team received the error" that anyone has received the error.

In fact I would generally bet thousands of dollars against that.

The only place I've worked that logged out technical details (inside of a <details> element) was also the one that did the best with logging those in Bugsnag and then having engineers triage them and create tickets. I think those things are very connected.

That depends. There are common errors where the support team gets that information because they have seen it before and having seen that error changes the support script in a hopefully helpful way.

Companies generally have massive amounts of errors though. They investigate the most common errors for their script. Sometimes when someone figures out a different error they adjust the script. Most errors though never get investigated.

I have seen the mailboxe folderss of companies with automated error responses and none of them were read.

Eh, depends.

I very much believe this gets dumped in some kind of ELK stack or something like that. And quite often teams will monitor to ensure that some new error message isn't going wild and alerts are sent out.

Single errors mean nothing, unless of course you're putting in a support call and we're directly looking it up.

> “our support team received the error”

Oh good, I guess I’ll expect to hear back never.

I think it’s a good thought but we’ve been conditioned that these things are black holes. User should have all agency in escalating or continuing troubleshooting rather than implied wait for deus ex machina from the support team.

> If you’re SaaS vendor you should give troubleshooting information to your support team skipping the user.

What support team? The ones that were all not hired in the first place, and if they were hired then they were replaced by AI? The same support team that customers simply cannot reach at all?

Sounds very useful.

Not everyone is Google, Meta, Amazon or Microsoft.

There are companies that care about their customers.

Missing part of discussion is “what for?”.

To make personnel decisions who to fire or give bonuses it doesn’t work. Just as lines of code don’t. If any of those indicators is lacking you have to dig deeper.

What lazy managers want is a single number they don’t have to dig into to make decisions. Lines of code, story points, bug counts.

To plan work for next sprint having last 6 months of stats gives quite good idea what can be achieved. But story points or stats are not useful for telling if specific features will be developed in specific timeframe.

Measuring “single developer productivity” is unsolved problem. It also is not a problem unless you are pointy haired boss and want to plan bonuses based on that or fire people based on that.

You definitely can measure team output over time and have some idea. Compare team to what they did in last 6 months and you have your measure for having idea how much can be achieved next month. But you cannot not plan like what can be achieved in longer period just next sprint or two.

This said you cannot compare teams like that.

I think you missed the part where there were much much less software devs/engineers earlier.

Year after year it was just much more new people joining as things got easier and more accessible.

Now you see 40 or 50 year olds far and between where most guys I see are in their 30s. Ones that are 60 yo diluted in the sea of new entrants.

Ageism didn't came from the top it just happened with flood of young employees, there is just social dynamics where you might get 40yo not being a manager getting along with bunch of 25yolds but that's going to be an exception not the rule.

I have vibe coded 3 applications I never had time to code but always wanted.

Now it is different in a way where now I don’t have time to use those apps.

That’s a joke.

But I do believe it answers the question of “what to build?”. If you didn’t have time before LLM assisted coding you still don’t have time for it. You most likely know what is used and what not already by heart or by some measurements.

Following Dutch jokes:

Well the lock itself for a junkie in Amsterdam has value if you get expensive one it is additional loot.

I don’t think so.

It is just realization by author that HTML is also useful tool and MD lacks some stuff.

He didn’t write anything about “now we should stop using MD files”.

It is more like: “I see I can do cool stuff with HTML and found cases where it definitely is right tool for the job”.

Most educated and motivated Polish people were slaughtered by Germans and Russians in WW II then ones still alive working for or heavily oppressed by puppet soviet state.

One of the examples:

https://en.wikipedia.org/wiki/Katyn_massacre