📚 node [[2023 04 05]]
- Wednesday, 04/05/2023 ** 10:15 If it's much easier to ask a coworker about code than it is to read the code or view some visualization of it, this is a code visualization/documentation/communication failure ** 11:33 How do we build libraries - and software - that will last forever? https://twitter.com/rsms/status/1643371448839581698
- Internet enabling 'dynamic linking' of these loosely coupled services, and the host platforms are the ones that break rather than any external dependencies.
- Rapid release cycles and platform API updates (sometimes breaking) that cause code to stop functioning on the platform.
https://twitter.com/rsms/status/1643380936392966144 : Spin up an app from any time using an archived snapshot of a system. Only depends on services
https://twitter.com/stockdiesel/status/1643377679637581825 : Only depend on services that are too big to fail - that cause big problems for major players on a global scale. It's nearly impossible to be an important customer as an individual or small company, but if my only dynamic, external dependency is on a bog-standard Amazon system, I'm pretty safe. ** 12:03 You can tell when a web product team gets updated laptops - their software starts to run more slowly on everyone else's computers but they don't notice the difference anymore.
📖 stoas
- public document at doc.anagora.org/2023-04-05
- video call at meet.jit.si/2023-04-05
⥱ context
← back
(none)
(none)
↑ pushing here
(none)
(none)
↓ pulling this
(none)
(none)
→ forward
(none)
(none)
🔎 full text search for '2023 04 05'