2025
👌 The simple/basic things are the most important to get right -
🌻 Downstream, things should be better -
🪙 Complexity and Simplicity -- two sides of the same coin -
⬆️ The business case for improvement -
👷 Make less work for others, part 2 -
👷 Do we make more work for others or less? -
🔄 The business model for updates -
🔄 What is the best software release frequency? -
🚀 How can Arch Linux get by without releases? -
⚖️ Truth is discovered, not invented -
🔗 Connected systems are different -
🛡️ How to get to secure and reliable -
🏭 Semi-structured part numbers -
⚠️ Toward a Theory of Medical Fallibility -
🛤️ Two paths with experience -
🚀 Why are releases important? -
👥 Who is the customer in organizational hierarchy? -
👤 Confusion about when we are the customer -
🕊️ Simple -- from whose perspective? -
🕊️ Simple to maintain vs simple to implement -
🕊️ Simple to use vs simple to implement -
🤏 Handling the small details -
📝 Documentation is part of the process, not an afterthought -
The three legs of YOUR Platform -
The importance of small Git commits/pull-requests -
The importance of Git Commit/Push often -
Thinking, Designing, Developing, Engineering ... -
envsetup.sh -- a very useful automation technique -
Effective email is either a pointer or notification -
Preparation - lessons from the kitchen -
Joy -
2024
Humility -
The biggest benefit to frequent updates -
Lifecycle management in dynamic systems -
Personal vs. collaborative documentation -
What is your most important tool? -
Easy to start vs. easy to finish -
Use a headset optimized for calls -
Are your processes proactive or reactive? -
Architecture vs. Optimization -
Coupling -
Improve development efficiency, reduce technical debt -
How to get the little things done? -
How can you make your commercial source code customers happy? -
Platforms vs Architecture Astronautics -
Habits -- a critical ingredient in YOUR Personal Platform -
Advanced technology and small players -
What can kids teach us about platforms? -
What are the pillars of a good platform? -
What is the purpose of technology? -
The easiest path to reliability ... -
Where do reliability/stability problems typically come from? -
Doing more with less, rather than less with more -
How to keep a product maintainable? -
What happens when someone else tries to use your work? -
How do you partition systems? -
How do you consistently name things? -
How can we be more consistent? -
Isn't it risky to update your dependencies? -
Platforms are for building systems -
The cost of updating dependencies, or not -
What is the difference between YOUR Platform and other platforms? -
Good enough is not good enough -
What will you improve today? -
What is the role of AI in your platform? -
What is the first thing you should implement? -
What is the best tool for private Git repos? -
Lessons from a 1-year old dog -
Solving problems or symptoms? -
Github and why does it matter? -
Tracking upstream and why does it matter? -
What makes a good Yocto BSP? -
What is the simplest form of automation? -
How does your product value increase after the initial sale? -
Hack-it, ship-it, forget-it ... -
What is the #1 purpose of YOUR Platform? -
Culture -
Three levels of YOUR Platform -
Owning YOUR platform is not more expensive -
False vs Real Platform Development -
The smaller you are, the more import YOUR Platform is -
Why do we need some level of control? -
It's about not starting over every time -
Complex Systems, Simple Platforms -