pull down to refresh
Love this kind of thinking. Culture is one of those things that can be nudged and affected but it seems nearly impossible to control. I've worked at companies where culture was important but it can't be created by a road map. Being a parent has taught me you can guide and influence but kids are born with their own natures and make their own choices. The best I can hope to do is lead by example, coach, guide, and protect. Most of all love. I think this applies to the broader culture as well.
reply
☑️ morning strength training
☑️Breakfast - 6 eggs and 2 chicken thighs
☑️Doom scrolling stacker.news
reply
A ton for sure.
- The biggest is probably watch out for implementation-specific issues. But it's incredibly hard to detect these early on.
- That's why bite the bullet and go multi-node, multi-implementation.
- You need more than one node anyways for maintenance downtimes.
- The more an implementation let's you control, the better. Take e.g. CLN's plugin system which let's you write your own low-level stuff like your own payment logic if you don't like the one that is shipped with the node. Or completely abstract the database backend.
Will add more as it comes to mind.
reply
how will splicing impact LN node operators?