What's this person's phone OS? This seems somewhat overlooked here. To me, the mobile OS is the centerpiece of any ecosystem. That leaves only two options.
The worst parta are in NRW and in particular Cologne (honorary mention: Frankfurt). Unfortunately a lot of people live there and a lot of trains go through there. Don't understand why it's not getting fixed. Every time more money is dedicated to rail the government of the day decide upgrading the stations is what deserves focus.
It's an infuriatingly accurate sketch. A team should usually have responsibility for no more than one service. There are many situations where this is not possible or desired (don't force your kafka connect service into your business logic service), but it's the ideal, IMO. More services mean more overhead. But someone read a blog post somewhere and suddenly we have four microservices per dev. Fun times.
That's all fake. LinkedIn is for sales and recruiting. If you see something there - a post, anything - it's meant to sell something. It's all as fake as the contents of an ad break.
If you give your data to a Chinese company you make your data available to the Chinese intelligence services. Same with most other countries with geopolitical ambitions. I don't see how this is controversial. This is why you only buy IT services from countries you trust.
Desktop operating systems really dropped the ball on protecting us from the software we run. Even mobile OSs are so-so. So the browser is the only protection we reasonably have.
As someone who has a hard time putting down tiktok, I have to say: Yes, the platform and algorithm is addictive and predatory, but some of the content is really good. Lots of very funny sketches, in particular. I don't like dances and whatever, so I get none of that.
Are you sure this is how he'll be remembered? Half the US thought him preferable to AOC and Hillary Clinton. It's hard to conclude in any other way than that the perception of his legacy will be equally divided.
Ypu could probably run it in wasm. Of course, without access to the DOM it won't go any further than anything else on wasm. The whole thing is nuts if you ask me. So much lost potential.
It's a reasonably cheap and unlocked handheld with fecent battery life. Personally I'd want more pixels, but if it works it works. It seems to be the default choice for remote control these days.
Yeah, photography (editing aside) is about having taste and getting lucky. A good photographer can of course raise their odds of getting lucky, but still. There's some technique in there too, but that's really not all that complicated. That said, I think few things match a good photo. There's something about a photo subject being real that I find fascinating. A photo exhibition does not display the imagination of the photographers, but rather the incredible in the real world.
So they should put it on the box. In small font on the back if necessary, but make it an official part of the spec sheet - don't pretend it's irrelevant.
I think the pricing of the big three is absurd, so I'm on your side in principle. However, it's the steady state that worries me. When the box has been running for 4 years and nobody who works there has any (recent) experience operating postgres anymore. That shit makes me nervous.
It's far cheaper to do it yourself, but the entire point is that you outsource the management of the service. Lots of people don't want to deal with database failovers, or - god forbid - deal with Kubernetes control plane issues.
Absolutely not. There's a gazillion cloud providers out there with hosted postgres+kafka+redis and the other big open source softwares. Hetzner is just not one of them.
I hesitate to call Hetzner "cloud". Hetzner is an EC2+S3 competitor, not an AWS one. IMO the minimum for being a real cloud is you need hosted Postgres, hosted Kafka, hosted Kubernetes, and S3-compatible object storage. Without the first three Hetzner is just not in the same product category. Nobody sensible buys AWS for the comically overpriced EC2.
Indeed. And SAP has no cooperation with any European cloud providers, afaik. It's the big three plus alibaba. SAP wants to move away from on-prem, but I guess it has a solution for critical applications. Maybe that can be shoehorned onto OVH or something.
Eh, these are highly skilled individuals that just don't like learning a new thing, no matter how useful. That attitude is a problem to be managed, but these people deserve a certain amount of respect. Anyone saying "suck it" or similar should get a grip.
The entire point of code names is that you can delay coming up with a marketing name. If the end user sees the code name then what is even the point? Using the code name in external communication is really really dumb. They need to decide if it should be printed on the box or if it's only for internal use, and don't do anything in between.
Often each API route will have its own handler function. That function will - usually through many layers of indirection and abstraction - launch queries towards your database.
Exactly. Divide the code in impure and pure functions. The pure functions can be easily unit tested. The impure ones can often be integration tested. The rest you'll just have to live with (or cover with whole-process integration tests). For tests spanning larger chunks of your code base it might be worth it to mock impure code. Never mock pure code - that's madness.