copium
> It's their relentless deindustrialization that will eventually do them in
Agree, China has already won, at this point a lot of the world sees them as a more sane option than USA as well which is a nuts timeline
281 karma · joined February 10, 2017
copium
> It's their relentless deindustrialization that will eventually do them in
Agree, China has already won, at this point a lot of the world sees them as a more sane option than USA as well which is a nuts timeline
How would "node architecture" make people vulnerable to this?
You have to have shell access to a victim first right? Or am I missing something?
TV show characters can be good
I normally use Greek gods for snowflake servers
A concatenation of owner / location and device for LAN devices. JohnsPixel4, LoungeTV,
opacity = (opacity < 0) ? 0 : opacity;
opacity = (opacity > 1) ? 1 : opacity;
if(opacity >= 0 && opacity <= 1) {
document.getElementsByTagName("BODY")[0].style.opacity = opacity;
}I'm not sure this is true, there are plenty of conflicts because of religion. I would argue the most stable would for nobody to be religious
Mail Catcher https://mailcatcher.me/
Lunatic SMTP https://github.com/anlar/lunaticsmtp
Ignoring variable name shadowing a static type system helps a lot
This same colleague had implemented a similar FSM (flying spaghetti monster as known by the team) in an FX (foreign exchange) platform at a previous company. Which after a job change I got the pleasure of experiencing, nobody in the team knew how it worked and everyone was petrified of making changes
Sometimes I wonder if this is a "feature not a bug" the company wins and saves money (in the short term)
It probably costs them via reduced employee happiness turnover etc etc indirectly but there is no KPI for that
* Managing schema migrations across every DB
* You cant query across the DB, want to know some cross tenant thing for ops? That's now a lot harder
* Connection pooling and resource usage can be harder to manage
Most systems I've worked on use a single DB with a `tenant_id` col on every relevant table, it's easy to have your query builder slap in the auth'd tenant I'd. This approach does come with issues like saving and restoring an individual tenants data
Like a lot of things in life, it's a trade off
Without two phase commits I would
1) Write to the DB in the original POST request a record indicating that an email should be sent 2) Process that record outside of the original request and mark it as sent
From https://www.storj.io/node
Average Payout Per Month...
Egress Bandwidth $20/TB
Repair Egress Bandwidth $10/TB
Disk Space $1.50/TB
Audit Bandwidth $10/TB
I have never tried to use it and have no affiliation