devjab
Joined 3 years ago
Joined 3 years ago
I mean, I have to write exit strategies from Azure because the EU might demand our industry to leave non-EU infra. Yet ironically the digital company ID I would need to sign new contracts with within Europe aren't available without one of the two app stores. It's not that I can't sign those contracts without the ID, but I'd probably have to go to Germany in person.
I can't say why Diesel.rs doesn't need async, and I would like to point out that I know very little about Diesel.rs beyond the fact that it has to do with databases. It would seem strange that, anything, working with databases which an I/O heavy workload would not massively benefit from async though.
This is anecdotal, but if my experiences aren't unique then there is a lot of lack of reasonable in DevOps.
As with everything, there isn't a golden rule to follow. Sometimes OO makes sense, sometimes it doesn't. I rarely use it, or abstractions in general, but there are some things where it's just the right fit.
This scores 6: function a(b) { return b[0]; }
This scores 3: const a = (a) => a;
(score is 7) function get_first_user(data) { first_user = data[0]; return first_user; }
Score better than this:
(score is 8) function get_first_user(data: User[]): Result<User> { first_user = data[0]; return first_user; }
I mean, I know that the type annotations is what gives the lower score, but I would argue that the latter has the lower cognetive complexity.
https://www.europol.europa.eu/media-press/newsroom/news/cybe...
If I had an electrician redo the wiring, I'd do the same thing without the "smart".
He probably had a shit life, but I never saw him bully anyone again.