rb2k_
Zooz (popular zwave manufacturer) has some interesting tidbits on their homepage.
https://www.support.getzooz.com/kb/article/1103-zen72-vs-zen...
"The ZEN77 Dimmer is recommended for 3-way and 4-way installations since you won't need to rewire your other switches in the set-up, you can simply replace the main switch with direct connection to power with the ZEN77 dimmer.
This model can control up to 100 Watts of LED bulbs but we don't recommend using it in installations with chandeliers or large groups of lights over 6 bulbs. Version 1.0 and 2.0 of the ZEN77 (700 series Z-Wave chip) were MOSFET dimmers so if your bulbs work better with trailing-edge (or reverse-phase) drivers, those versions of the model worked best. Version 3.0 of the ZEN77 (700 series Z-Wave chip) is now a TRIAC dimmer so if your bulbs work better with leading-edge drivers, this model will work better. The 800 series version of the ZEN77 is also a TRIAC dimmer. Why We Changed to all TRIAC: We found that newer LED bulbs dimmed better with TRIAC dimmers, and considering limited availability for MOSFETS, we decided to transfer the ZEN77 model to TRIAC as well."
Direct image link: https://scontent-atl3-2.xx.fbcdn.net/v/t39.2365-6/439015366_...)
Do you happen to know if that's still the case?
(I guess for use-cases such as live streaming it doesn't matter that much, but for video that ends up in some archive, it's probably less acceptable)
I was told about e.g. multiple internal CI/build systems because one org didn't want to rely on the other, so they both built their own little software stacks.
That's a bit different than what I've heard from meta/google/amazon who seem to be more open to running centralized internal services
Criticism is certainly helpful and necessary for advancing the state of the art, but without something to balance it, it turns into a pretty bleak place to work. I guess this is one example that feels more like a personal vendetta than a constructive criticism of the work.
Often the suggestion featured does suggest a whole team as a review based on code ownership.
Any company that I've seen put SRE/"DevOps"/... as the sole primary on-call rotation basically just created a glorified operations team.
Unless you have shared pain for botched releases, you will never get rid of these problems.
But that means that in one case you make 200k base, have an on-call and don't get any extra on-call money. In the other case you make 140k base, have an on-call and get 10k extra on-call money.
Ultimately you end up doing the same work but one of them gets paid less.
"Funkstandards / Frequenzen EnOcean (868 MHz), Low-Power-Funk (2.4 GHz) WLAN (802.11 b/g/n 2,4 GHz)"
So that's neither of the two major protocols (zwave and zigbee) nor any of the up and coming ones (thread).
Am I missing something?
https://research.facebook.com/publications/holistic-configur...
You can see that there's a common backend ("configerator") that a lot of other systems ("sitevars", "gatekeeper", ...) build on top of.
Just imagine that these systems have been further developed over the last decade :)
In general, there's 'configuration change at runtime' systems that the deployed code usually has access to and that can switch things on and off in very short time (or slowly roll it out). Most of these are coupled with a variety of health checks.
(Not saying that it induced a hypomanic episode, just that all of those fit the description)
People always mention that as an argument. I'm pretty sure that we could figure out a solution if we actually worked on it. Given how far we've come over the last 100 years, I don't see this as a problem that we couldn't solve over the next 100 years.
Why not though?
They'll be tax payers soon and I'm sure we'd get more of them if we made it easier to rear them.
There's probably a lot of subsidies that are currently in place that make less sense.
A lot of the ones in Germany are as well. https://en.wikipedia.org/wiki/List_of_trade_unions_in_German...
> time off
I get 21 days in the US, but any holiday that falls on a weekend I am guaranteed to get on a weekday.
Ultimately it ends up somewhere around 30 paid days off I would guess. Back in Germany, if a holiday fell on a weekend, I just lost it.
> government paid health care
In Germany I had to pay 7.5 percent of my salary + my employer had to match that. When I was freelancing I had to do the full 15%.
The US clearly has the worse healthcare system overall, but I pay a LOT less for MUCH better service. That is however just because of my employer and on a population level it's a catastrophe.
That being said, my impression is also very skewed by FANMAG and the average experience is probably worse.
For simple workloads (e.g. serving static files via HTTP) I'm pretty sure it could saturate a gigabit connection.
You can even find pre-made travel routers with the Allwinner H3: https://www.amazon.com/Portable-Allwinner-Quad-core-high-Per...
https://hochgatterer.me/hkcam/
I agree on the comment for rtsp though. Most solutions have multiple seconds of latency which is a bit suboptional.
(Not holding my breath for the kind of responses this comment might get ;))
https://california.public.law/codes/ca_bus_and_prof_code_sec....
California Business & Professions Code section 16600 makes clear that any non-compete provision between employer and employee will not be enforceable under California law
1. Stop putting college kids with a bachelor degree in business in charge of software development teams. "Management" is still seen as something very 'fancy' in Germany. Being "a manager" carries a lot of weight.
2. Allow Engineers to advance without forcing them into management. A lot of very talented engineers in Germany are forced in mediocre middle management / product owner positions as the only option to gain some more influence.
3. Pay