I think there is another aspect that is important: limit the blast radius. Shit inevitably happens when you create something new and complex, and when it does, you’d rather minimise the impact where possible.
I think there is another aspect that is important: limit the blast radius. Shit inevitably happens when you create something new and complex, and when it does, you’d rather minimise the impact where possible.
Oh boy, that was hilarious!
“Torvalds sold out.” Would you mind elaborating what you mean by selling out in this context?
I mean a good approach would be to just go through Apollo and … copy with bride! Christian did an amazing job with it.
Feature: hide posts based on specific words in title. Handy when you’ve had enough of a particular topic (trump, musk, …)
I think the bullshit picture aligns well with the product!
All important automations should run fully locally. I also find that focused and simple automations are often most useful. When I say simple I mean in terms of automation logic, not necessarily in terms of interfacing devices, which can be tricky at times. Example of simple automations I like most would be switching amplifiers on/off based on audio state changes, switching lights on/off relative to sunset, and switching electric water and floor heating elements on/off depending on energy price.
This happens easily for big successful organisations. Over decades a strong culture aligned with how they succeed forms. Once the market changes requiring a culture change, a seemingly invincible company suddenly stumbles. They simply can’t respond even if they what they should change.
Ex. Rolls Royce CEO stated this phenomenon well: culture eats strategy for breakfast.