eldelshell

The one tossing the nuclear threat is Putin whenever his tea is too cold.

println

This is why I don't like health related business models. In a similar scenario, who's stopping Susan from sueing over a "bad" outcome from the platform recommendation. When people's health is on the line, shit can get ugly really fast.

Pffft! And what next, running software on fat clients? Preposterous!!!

My experience with SSE so far (take this as recommendations if you wish)

You need to implement a server-side heartbeat feature.

You need to handle the close event from EventSource and be able to reconnect.

Tabs can be problematic. When you subscribe, you use a URL with a nominal ID to identify the client. For example, on a chat app, you would use /api/sse/userA/subscribe

Problem is, if userA starts opening tabs, each tab creates a new subscription for userA so you need to randomize each connection (userA-UUID).

If you don't use a nominal id, the server won't know to which subscriber to send the data and you don't want to broadcast all your chats.

I've used the Broadcast channel API in conjunction with SSE to have only one tab handle the SSE connection, and broadcast incoming SSEs to the other tabs which also reduces the number of connections to the server to one.

On the server it's also a PITA because not all instances/pods have the subscribers list. The way I've found to solve this is with clustering the instances with Hazelcast or Redis or a MQ.

But once you figure out all this, SSE works quite well.

SSE has its own API (EventSource), it's not a normal fetch/ajax request.

https://developer.mozilla.org/en-US/docs/Web/API/Server-sent...

Bluetooth PoS printers are a bitch to work with and good luck doing that from JS.

IMO, LC (and similar) aren't a bad choice for the interview process. The problem comes when it's used as a silver bullet solution. Most seniors that'll show up to an interview are probably working and simply don't have the time or will to grind LC.

Also, SWE is a highly movable profession, where being more than 5 years on the same place is unusual. So every ~5 years you have to polish your CV, grind LC and basically restart learning all computer science concepts you haven't used in those ~5 years, without feeling burnout or dismay.

Funny thing is that A players can go downhill not because of their engineers, but because of their management. How many companies have we seen in tech go under because of bad engineering vs bad management?

End of day you have to deal with physics. All those bits have to be stored somewhere. Have we really reached the point where the Facebook database can be stored in a distributed system across personal devices? Hell no! As a matter of fact, being centralized, FB can store that amount of data more efficiently than any Blockchain can even dream about.

There are this things called "Exchanges" in every airport in the world.

With the US dollar, Euro and some others, the world is your casino (following the comparison) and you can trade all of them. Same with gold and silver (although this are a bit harder to trade).

Hell, try to pay a taxi in Djibouti, Sao Paolo or Islamabad with a BTC or USD and see which they'll accept and which will get you kicked out.

Log4J is far from being the standard. As a matter of fact, JBoss, Quarkus, etc, aren't affected by this because they don't use log4j.

I'll sell you a paper that says you own a Beanie Baby. That's NFT for you, but without the paper, so you don't even own a paper.

I don't remember where but a guy made the comparison between NFT and those companies that sell stars, or land in Mars or the Moon, like they'll sell you a paper that says you own Proxima B.

This is the best way to understand NFT.

I read this comment every decade.

This. You're only unprofessional if you start ranting about it at every opportunity you have, specially during a job interview.

Just saying, check what a private health insurance costs in the US vs the UK. Even if the NHS is not the best, it's a big market force which makes it very hard for private insurances to fuck you up in the ass like in the US. At least in my country, having my 4 pax family in a premium private insurance costs me close to 400€/m.

Some companies have a rule that if the extension of the business travel is longer than X you get business class. So if your French colleague came from France and then you went somewhere else together, they could've included a whole business pack for the same price as a tourist class.

Not sure this is the case but FYI.

The main difference is that, at least in my country, my salary represents a part of what my company pays for my employment. AFAIR if I earn X my company is paying X*1.5 that goes into taxes, social security, etc. While in the US the salary is mostly given to the employee and they have to pay for all of the above. In your example, that company in NL could be paying something closer to 80k-90k which depending on the exchange rate is close to US$100.000

OTOH, we all know how some salaries are crazy high in high COL areas like SF, which I'm sure don't represent the whole of the US. I work with devs in Florida and NC that don't get pass the 6 figures.

I can hear all those binary trees being sorted.

It's stupid. Let's stop leaks by creating another, centralized leak source... Leaks now in 4K!

6. Microservices. It's not unusual to have several Microservices consume a common entity, like say, User. If every microservice has to authorize each request doing a db lookup, it doesn't scale either.

He does bring fair points that it's important to understand before using JWT. If your use case includes immediate logout, or to avoid stale data, then it might better to not use JWT.

I'm just going to add that it also helps to describe your intent on code. For example, on Quarkus or other Java frameworks you use javax.ws.rs annotations. So if you're reading your code and see @GET or @PATCH you know what that method is doing even without reading the method signature. If you then add swagger it will generate a nice UI with colors and all that also helps to describe the purpose.

It also isn't a "pure" HTML solution as all the magic is happening on CSS. So, convoluted CSS or two lines of JS?

From the worst: always shower and stay up-to-date.

From the best: abstract only when needed.

You have to understand the Apple fanboy mindset. If it breaks, it's your fault. Soldered SSD? Do backups you dummy! Over heating? Just use it for email and browsing. Dead pixels? Get better glasses. No ESC key? Buy an external keyboard. Keys not working? Don't push them so hard, they're butterflies!

If by "strictly enforced" you mean a colleague will change your lock screen background to a goatse then that's how I learned.

Are you still salty about systemd? Let it go, let it go.

It's all bullshit.

What a bunch of crap.