vichle

Do they have stuff that doesn't rely on microcontrollers? I'm a software engineer since 10 years, I don't want to copy/paste some poorly written C code, I want to solder stuff together :)

Is this a good book for beginners? What other books are good for electronics beginners? Preferably cheaper than this... :)

This is why I always delete by ID when cleaning up after tests.

Most "evil" acts are in fact just selfish. To truly classify something as evil, there needs to be an intent to cause harm.

I'd also argue that desperation is a subset of selfishness.

For real? Sweden has had this for like 15 years. Perhaps if you paid a bit more taxes your government wouldn't be so useless (:

I think it's pretty clear that they are theorizing rather than claiming anything?

You pay a premium for

- Lower chance of fatal bugs/downtime - More reliable load balancing - Proven backup startegies - Not having to learn everything

I've spent 7 years at a "unicorn" and the first five years we used Digital Ocean VPSs for everything. My main takeaways are that the smaller providers don't have "real" load balancing and that you absolutely should not manage your own databases or logging/metrics, it's a pain in the ass unless you have a team for it. I spent countless hours on learning infrastructure instead of building the product. It worked out in the end, but we would have gotten there much quicker if we'd paid the premium.

If I did it again I'd still use VPSs, but with one of the big players and pay for dbs and observability.

This is what I thought. After some fiddling it became clear that compatibility will be an issue for more applications than they claim.

It's probably fine for new projects though.

> Another feature of feature flags is that a non-coder can toggle them.

This is not a feature, and it will get you called in during the weekend at some point.

Maybe I'm missing something, but it sounds like there's a strong case for Erlang/Elixir rather than Clojure? They kinda built BEAM on the JVM, no?

Because all great developers create More complexity (-:

I recently went to an event at Google and several of their devs actually had chrome books... :shrug:

Redis was not a distributed system a decade ago.

Sounds like you've just used node incorrectly, like without any error handling or frameworks? Pure node has always been pretty bad until very recently, the ecosystem is a big part of what has made it popular.

Seriously... Just use what you want and don't get angry that some people disagree? What a waste of time and energy...

> If it ever becomes a liability, you just check in the "transformed" code and it's gone.

I've done this and regretted it - CS transpires to ES3 and specifically null chaining is completely unreadable.

From a backend perspective it's no biggie to instead keep the CS dependency and gradually convert files manually when you have to make changes anyway, or when you have 15 minutes to spare between meetings.

You become fluent enough to not even need tests after a while (yikes!).

Sooo... Thick air?

There will never be 100% consensus on which content is worth watching on any topic, does that mean that you never consider watching anything?

Looks promising. There are a couple of things that worries me though. (I haven't tried it yet, only skimmed the docs)

1. Telemetry needs to be opt-in during install. 2. The roles are weird, why would a developer need write access by default? That's just a recipe for disaster. Would be better to default to read-only in all roles and allow upgrading to write permission as an active choice. 3. There needs to be a clear way to distinguish between prod/staging. I like clients where you can change the background color for different connections, eg screaming red for prod.

Good luck, keep up the good work

Bad analogy. Dropbox solved a problem in a simpler way than doing it yourself. What problem is web3 solving? And is it really simpler to use than the alternative?