Exactly the reason I keep dealing with HomeKit annoyances.
1,045 karma · joined November 9, 2016
Exactly the reason I keep dealing with HomeKit annoyances.
The cost of the router and two stations was about the same as for router and one station of various hyped products.
It has got lots of smarts, VPN server, DNS server, highly configurable and you can opt in into Synology cloud with DDNS and connection to home network using their stuff. There’s security monitor, something akin to fail2ban, etc.
Additionally I have a Synology NAS that serves as a server using docker and as media station using Emby package. Additionally my old thinkpad laptop serves as a build agent for Drone CI primary that is running in docker on the NAS.
Everything else connects to internet and home network via WiFi, 800 megabits seems plenty for everything I want to do.
I am not affiliated with Synology, just a happy user that finds that everything I need to work, simply works.
Vow, for a rare occasion that one translates rather nicely.
Same thing, my first reaction was "oh my god, no, please no" and I rushed to see if he's alive.
I recently switched from between tech stacks and quite different ways of working and different products.
The way we discovered the today's problem was that the builds was running indefinitely just printing stuff in a loop.
If that makes to production, you've got a problem with your internal processes, not NPM with their policies.
The issue here is the package deal, not all death row inmates are equal. One is a monster that molested and killed a number a number of children, another is an idiot that played knight rider and ended up crashing into a group of people.
As an unrelated (not a victim) observer, I’m fine for mercy and forgiveness for the second type, provided victims agree. I’m definitely not fine giving a chance to get out on the streets to the first type.
Now we do have tools that overcome those limitations somewhat - like limits and stuff but doesn’t remove the need for better tools.
So I somewhat disagree with both of you - we need new, better numbers that are further from math abstraction and closer to actual reality.
Otherwise it is like this story with Poynting vector from Veritasium video - only confuses instead of explaining.
- Node with no fancy stuff like TypeScript, just JavaScript, jest for tests, React on frontend, require 100% test coverage (or less test coverage but use TypeScript).
- Java with Sptrig Boot and their reactive web framework and React on frontend.
Reasons:
- Either of those provides _fast_ feedback loop. Node.js is even faster.
- Either of those have got _huge_ ecosystem and a library for anything.
- Either of those is supported by major cloud vendors and first-class citizens.
- The amount of googleable information on the web if you need some docs or help is enormous.
- The amount of devs to hire is huge.
- IDE support for both is excellent.
- There are official base docker images for either, there are version management tools for either that are very easy to use (mvnvm, sdkman, nvm).
- If your webapp grows you have _a lot_ of scaling opportunities.
KISS database side and use Postgres. Try to make someone else to manage it for you, something like Aurora from AWS or whatever there’s out there. If you _really_ sure that your database model is solid and won’t change and/or you’ve got lots of money to through at problems you may want to consider something managed NoSQL like DynamoDB or what was that, Cosmos from MS?
Host on something like Heroku but be aware that they lack a lot of Enterprise required compliances, we recently moved away from it because of that (we have to be compliant).
No excuse for Michael though, she really put me off.
To their credit they did joke about get behaviour in season 3.
edit: my poor spelling.
+1 on that. Those snobs are tiresome. Firs they shitted ST: Enterprise out of existence (which now they keep on whining how underrated it was), now they are pooping all over the place on all modern stuff.