.net being a good example of this

I'm sure I still have CD case with 'Windows .net' printed on it which contains Windows 2000 and SQL Server... .net?

The marketers really went to town on that one, would have loved to be in the creative pitch meetings for that swag.

'.net, what is it??'

'Who knows??! But if we print .net in multicolour on enough stuff, somebody might figure it out!'

> The marketers really went to town on that one,

To be fair, the developers at Microsoft went to town on it as well, adopting C# for parts of Windows Blackcomb, including the File Manager, the Desktop Manager, and (some of) WinFS. It turned into a fiasco and the .NET adoption was mostly dropped, as far as I remember, when they did the "reset" and pivoted to Vista.

Because the WinDev team sabotaged, the effort, instead of doing an Android or ChromeOS with everyone roaming into the same managed direction, they made sure they pretty Windows APIs would win..

So since Vista all new APIs follow Longhorn ideas, while using COM, followed by Windows Runtime, with the caveat that tooling is just as bad as before .NET was invented, but hey they are happy fellows on their little turf.

OmniWeb was a pretty good browser and I used it exclusively until Firefox was released for Mac.

I have a vague recollection that there used to be a Word Processor for the Atari ST with the same name, but I could be wrong.

One of the reason Switzerland is a rich country per-capita is that it has used its resources very wisely by investing in ubiquitous public transport throughout the whole country.

Yes, I can't wait to hear that my car no longer works because all the plastic "rusted"

Have you thought about, or are you already involved in interviewing new developers for the company?

It sounds like you might already have a nose for what makes a good dev (i.e. somebody who holds the same values as you) It's a great way to influence the company culture, and get good co-workers, which can also de-stress you as you now have fellow travelers whom you can trust with tasks.

It's also fun, sometimes humbling but always interesting!

+1 to your comment.

I suspect they are feeling stressed because they're the main goto person on the product, and with enough random bobble heads running around trying to commit sacrilege on your codebase it quickly becomes a problem of control to maintain the quality you've so strongly instilled vs allowing the product to progress.

Their best path to get out of this bind I'd say is to slowly try to make themselves redundant on that product, choose a victim dev to be your successor and gradually disengage. Possibly a new product or project will be started and then they're free to get involved in that instead.

Also learn how to interview new candidates and get involved at that level, getting good (even better than you) coworkers is a great way to influence the whole company culture and make your work life much more pleasant.

The article then goes on to say:

>In fact the picture is rather different: a sorting process is under way

And talks more about the process of penalizing weaker crypto assets, focusing on Tether. So it's actually a balanced and interesting overview of the fallout of the current selloff on what is now becoming a rather large and very complex market all of its own.

I only mention this as your comment seems a bit dismissive based on that one sentence.

Thanks for bringing this up! The good stuff you've mentioned is behind the paywall for me and the intro I can read does look non-balanced.

There are always archive links. It’s a good idea to read the whole article before condemning it.

https://archive.ph/4x3je

> “… The trouble is that a draconian crackdown would put at risk the benefits that crypto eventually promises, including new financial products that bypass stodgy banks; innovations in property rights; and the possibility of a less centralised financial system.”

Bit OT, a further good idea will be to buy the subscription and support good journalism. I am not being flippant, I believe good journalism needs support.

IIRC they offer some trial subscription where you can register and read a few articles for free in a month or so. Also articles from "The Economist" are frequently posted in HN and often comments have non-paywalled links. Reading through them probably help you to judge whether it is good journalism or not.

Well... you need trees to spread more trees. But if you've got no trees to start with, then you need drones.

>But 99%+ of companies don't have such problems and never will.

Not sure where you get your metrics, but I would say a more general rule would be that the more people work on an evolving product that includes code and schema changes, then the more you need db constraints to enforce what it means to have correct data.

If only 1 or 2 people are involved in a db that changes pretty infrequently then possibly in the long term you can get away with it.

But if you have a constantly evolving product which must carry new features, logic changes and additions to the schema, then I would say you definitely need db constraints - FK and column. It only takes a few different developers to decide that T,F,Y,N,TRUE,FALSE,YES,NO,Null,NULL,None all mean the same thing, and you've got a slowly evolving mess on your hands.