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!'

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!

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.

>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.

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.

However it's clear that NATO is also mindful of the fact that Ukraine is currently well led by a capable democratic leader, but that might not be the case in a year or 2, so don't give them too many toys.

Saying that, as an armchair general I would like to see Ukraine driving a wedge to the west of Mariupol down to the sea, and a wedge just south of Kherson to surround the forces there. Secondly they could cross over into Russia via Bolgorod and attack the eastern forces from behind, whilst taking out as much military (including propaganda channels) and rail infra on the way.

The land bridge to Crimea should be reduced to rubble and the port at Sevastopol disabled.

Don't know that they have the man power for that, but that should give the old dictator something to worry about.

Elon I would imagine is way too busy with his other concerns to be distracted by a social media company, even though at the moment it does seem to carry an oversized amount of influence.

And Elon's brand is probably too randomly 'firecracker' for a company that's probably already attracting scrutiny from governments across the world due to the above mentioned outsized influence it has on discourse and opinion.

Bowler Hatted Interviewer: 'Well then, what do you know about these new fangled things then?'

Kipper tie: 'Well I saw one once being used on Logan's Run, and it looked quite easy. I'm also really into Led Zeppelin.'

Bowler Hatted Interviewer: 'Well you sound perfect. When can you start? Only, that spinning tape thing over there stopped spinning 2 days ago and I'm awfully worried we won't get our reports out for month end tomorrow.'

I just wish it wouldn't select pictures of my ex-gf so often :/ Should probably delete them, but.. nostalgia.

>The following OSs do not support kTLS, for the indicated reason:

>Alpine Linux 3.11–3.14 – Kernel is built with the CONFIG_TLS=n option, which disables building kTLS as a module or as part of the kernel.

and even recommends building OpenSSL and Nginx 3.0 yourself anyway, so looks like it will be a while before this might be available out-of-the-box for most major dists. But of course everything is OSS so you can DIY if you don't mind getting some ./configure under your fingernails :)

Russia on the other hand will of course work hard to adapt, but they are about to learn that they will be ostracized and blocked at every turn when they try to reintegrate with the rest of the world. No longer will their oligarchs get to jet around the world with their outsized wealth, no longer will Russian propaganda be accepted as 'valid discussion' and their activities overlooked and hopefully no longer will Russian money be accepted to influence politics.

The mask is off now and the snarling beast underneath can be seen - hopefully now by all.

This is actually a pretty insightful comment, and something I haven't thought about in a number of years since networking disparate machines together to create a system in now so second nature to any modern software that we don't think twice about the massive amount of complexity we've suddenly introduced.

Maybe the mainframe concept wasn't such a bad idea, where you just build a massive box that runs everything together so you never get http timeouts or connection failed to your DB since they're always on.

Kind of how the original British SAS got started I believe.