rb2k_
Joined 16 years ago
Karma
3,138
Submissions
850
Member since
Jul 20
Computer person
View on Hacker NewsRecent submissions
Comment · 1 year ago
There's differences. e.g. MOSFET vs TRIAC
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."
Comment · 2 years ago
The readme mentioned H20 GPUs. Nvidia's "China compatible" card (41% Fewer Cores & 28% Lower Performance Versus Top Hopper H100 Config)
Comment · 2 years ago
Some Llama3 400B numbers for the April 15th checkpoint are listed at https://ai.meta.com/blog/meta-llama-3/
Direct image link: https://scontent-atl3-2.xx.fbcdn.net/v/t39.2365-6/439015366_...)
Comment · 3 years ago
In the past (with h265 / h264 at least), hardware encoding always ended up with visibly worse quality (and often even bigger file sizes) compared to a software encoder like x264/x265.
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)
Comment · 3 years ago
Last I talked to people about Apple's internal tooling, it was still pretty fragmented between different organizations.
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
Comment · 3 years ago
Did you base your router config on some existing template or did you just built it up from scratch?
Comment · 4 years ago
There should be a difference between applying critical thinking and being borderline hostile though.
Comment · 4 years ago
I think one of the problems with large parts of academia is that the system thrives by finding flaws within things other people have created.
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.
Comment · 4 years ago
Nah, a dedicated "code review team" is not a thing.
Often the suggestion featured does suggest a whole team as a review based on code ownership.
Comment · 4 years ago
> Some companies hire dedicated tech people whose only job is to be oncall, handle alerts, and improve the oncall infrastructure. This role is called ‘DevOps Engineer’ at some companies, SRE (Site Reliability Engineer) at others, and may also be called ‘Operations Engineer.’
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.
Comment · 4 years ago
One thing that this article is also kinda missing is the base compensation. Some companies (e.g. FB) are in the top 90th percentile or so of the industry but then don't pay on-call compensation..
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.
Comment · 4 years ago
The website mentions:
"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?
Comment · 4 years ago
It's 7 years old by now, but there's some literature:
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.
Comment · 4 years ago
Interesting. That almost sounds like mania/hypomania.
(Not saying that it induced a hypomanic episode, just that all of those fit the description)