Tame product development chaos with YOUR Platform.

195 Tags

#abstraction5 #accessibility2 #action1 #adaptability1 #agile1 #AI17 #arch2 #architecture7 #asset1 #automation13 #BCR1 #BSP3 #business3 #cad1 #cd2 #Certainty1 #change1 #changelog1 #chat1 #checklist2 #ci1 #closed-loop6 #coding4 #collaboration11 #commitments1 #communication10 #community5 #complexity1 #confidence1 #consistency5 #constraints2 #containers1 #context3 #control6 #cost2 #coupling2 #creativity2 #csv2 #culture4 #customer6 #daily3 #data4 #data structures2 #dates1 #debt2 #debugging1 #deep work1 #demo1 #dependencies2 #deployment1 #design1 #details1 #different1 #discipline1 #disipline1 #distributed1 #documentation13 #drawing3 #dry1 #email5 #embedded1 #engineering1 #errors1 #experience9 #experts1 #fallibility1 #false1 #feedback6 #files2 #finish1 #focus1 #friction2 #future5 #git13 #gitea3 #github1 #gitlab1 #goals1 #golden1 #google1 #growth1 #habits4 #hack1 #hardware1 #headset1 #help1 #hiring1 #humility1 #improvement13 #innovation1 #integration7 #iot1 #iteration5 #kids1 #law1 #learning6 #levels2 #liability2 #lifecycle2 #linux2 #long2 #maintenance11 #management3 #markdown3 #math1 #meetings7 #meta1 #metrics1 #monorepo1 #naming2 #notes2 #open1 #optimization2 #organic1 #organization3 #oss12 #other1 #others1 #own1 #partitioning2 #partnumber1 #patterns1 #people2 #personal6 #phases1 #platform10 #pomodoro1 #preparation1 #present1 #proactive1 #problem2 #process19 #product2 #productivity11 #programming6 #reflection2 #relationships1 #release7 #reliability1 #reliablility1 #reuse1 #risk1 #rituals1 #satisfaction1 #scalability1 #scaling9 #screencast1 #scripting1 #security1 #self-hosting1 #server1 #service1 #shell1 #shipping2 #short1 #silos1 #simplicity19 #size1 #soc1 #software2 #start1 #steps1 #steve-jobs2 #strategy1 #symptom2 #system1 #systems7 #team7 #technical debt5 #technology5 #test2 #testing4 #tests1 #time1 #time-management1 #tool1 #tooling1 #tools17 #transparency1 #trust1 #truth1 #update5 #upstream1 #users2 #value2 #verification1 #video1 #vision5 #wealth1 #why1 #work2 #workflow12 #writing4 #yagni3 #yocto3

#abstraction

๐Ÿงฉ Composing is hard, complexity is easy -

๐ŸŽผ Compose software like music -

๐Ÿงช Abstractions and Platforms -

๐Ÿ”— Coupling -

๐Ÿงช What is a good abstraction? -

#accessibility

๐Ÿ“ The file dilemma -

๐Ÿ“ง Effective email is either a pointer or notification -

#action

๐Ÿšด The power of movement -

#adaptability

๐ŸŒ€ Complex systems are hard to predict -

#agile

๐Ÿฅฃ The two ingredients for agility -

#AI

๐Ÿ“š Documentation never has to go out of date again -

๐Ÿ›Kernighan's Law -

๐Ÿ“ Document "why" not "how" -

๐Ÿ”„ Close the loop with AI -

๐Ÿ’ฐ Ways to reduce your AI costs -

๐Ÿ“ The file dilemma -

๐Ÿ”„ AI and documentation - close the loop -

๐Ÿค– AI is the new compiler -

โœจ Anyone can write scripts now -

๐Ÿค– How I use Claude Code to help publish this blog -

๐Ÿ”ญ Text based formats and command-line tools are the future -

๐Ÿ”„ Flipping the playbook for AI coding -

๐Ÿง‘โ€๐Ÿ’ป The first step in AI coding -

๐Ÿค– The biggest problem with AI -

๐Ÿค– What is AI good for? -

๐Ÿง‘โ€๐Ÿ’ป Will AI cause coding to disappear? -

๐Ÿค– What is the role of AI in your platform? -

#arch

๐Ÿ† The entire story -

๐Ÿš€ How can Arch Linux get by without releases? -

#architecture

๐Ÿ”— Integration, not isolation (part 2) -

๐Ÿ”— Integration, not isolation -

๐Ÿงฉ Composing is hard, complexity is easy -

๐ŸŽผ Compose software like music -

โžก๏ธ Frontload the boring stuff -

๐Ÿงช Abstractions and Platforms -

โš–๏ธ Architecture vs. Optimization -

#asset

๐ŸŒฑ OSS can decrease or increase your code liability -

#automation

๐ŸŒ€ Complex systems are hard to predict -

๐Ÿ“Š Simple data formats + powerful tools scale -

๐Ÿ“š Documentation never has to go out of date again -

๐Ÿ’ฐ Ways to reduce your AI costs -

๐Ÿ”„ AI and documentation - close the loop -

โœจ Anyone can write scripts now -

๐Ÿค– How I use Claude Code to help publish this blog -

๐ŸŽ‰ 200 posts -

๐ŸŒฟ A natural way to get more testing/automation -

๐Ÿค Handling the small details -

๐Ÿงฉ The three legs of YOUR Platform -

๐Ÿ”ง envsetup.sh -- a very useful automation technique -

โœ… What is the simplest form of automation? -

#BCR

๐Ÿ† The entire story -

#BSP

๐Ÿ™ Github and why does it matter? -

๐Ÿ” Tracking upstream and why does it matter? -

๐Ÿ”ง What makes a good Yocto BSP? -

#business

๐Ÿ—‚๏ธ Git has an unfortunate name -

๐Ÿ“ˆ What do we mean by scaling? -

โฌ†๏ธ The business case for improvement -

#cad

โžก๏ธ Frontload the boring stuff -

#cd

๐Ÿš€ Git driven CD -- you know what got deployed -

๐Ÿ™‹ How to help yourself? -

#Certainty

โœ… Guarantees -

#change

๐Ÿ”— Connected systems are different -

#changelog

๐Ÿ“„ Who is a changelog for? -

#chat

๐Ÿ‘ฅ Alternatives to meetings -

#checklist

โœ… The problem with software -

๐Ÿ›ค๏ธ Two paths with experience -

#ci

๐Ÿ™‹ How to help yourself? -

#closed-loop

๐Ÿ”„ Closed-loop engineering -

๐Ÿšด The power of movement -

๐Ÿ”„ Closed-loop humans -

๐Ÿ”„ Look for closed loops -

๐Ÿ”„ Close the loop with AI -

๐Ÿ”„ AI and documentation - close the loop -

#coding

โš–๏ธ Code is a liability, not an asset -

๐Ÿ“š Keep documentation close to the design/code -

๐Ÿšด The power of movement -

๐Ÿค– AI is the new compiler -

#collaboration

๐Ÿ’ฐ What is the cheapest PDM tool out there? -

๐Ÿ—‚๏ธ Git has an unfortunate name -

๐Ÿ“ Git* solves the problem of managing files -

โœ๏ธ Effective communication (Written) -

๐Ÿ”— Integration, not isolation (part 2) -

๐Ÿ”ญ Text based formats and command-line tools are the future -

๐Ÿค Modern product development is a collaborative endeavor -

๐Ÿ‘ท The tension between solo and collaborative work -

๐Ÿ› ๏ธ Selecting tools -

๐Ÿงฉ The three legs of YOUR Platform -

๐Ÿ“ง Inbox zero -

#commitments

๐Ÿค Keeping commitments -

#communication

๐Ÿ“ Document "why" not "how" -

๐Ÿ”„ Closed-loop humans -

๐Ÿ—‚๏ธ Git has an unfortunate name -

โœ๏ธ Effective Communication (Sketching) -

๐ŸŽจ Effective Communication (Drawing) -

๐Ÿ“น Effective Communication (Video) -

๐Ÿ“ธ Effective Communication (Images) -

โœ๏ธ Effective communication (Written) -

๐ŸŽง Effective communication (Audio) -

๐Ÿ“ง Top vs bottom posting in email -

#community

๐Ÿค Modern product development is a collaborative endeavor -

๐Ÿš€ Advanced technology and small players -

๐Ÿ™ Github and why does it matter? -

๐Ÿ” Tracking upstream and why does it matter? -

๐Ÿ”ง What makes a good Yocto BSP? -

#complexity

๐ŸŒ€ Complex systems are hard to predict -

#confidence

๐Ÿฅฃ The two ingredients for agility -

#consistency

๐Ÿ“… Dates in filenames -

๐Ÿš€ Platforms vs Architecture Astronautics -

๐Ÿท๏ธ How do you consistently name things? -

๐Ÿ”„ How can we be more consistent? -

๐Ÿ”„ Does consistency matter? -

#constraints

โœจ The Beauty of Constraints -

๐Ÿ˜ฑ The tragedy of no constraints -

#containers

๐Ÿ”— Integration, not isolation -

#context

๐Ÿ“ Document "why" not "how" -

๐Ÿ“ The file dilemma -

๐Ÿ“ง Effective email is either a pointer or notification -

#control

๐ŸŒ€ Complex systems are hard to predict -

๐Ÿ“ Git* solves the problem of managing files -

๐Ÿ•น๏ธ What can we control? -

๐Ÿ˜จ Control is a scary thing -

๐ŸŽ›๏ธ What is control? -

๐ŸŽฏ Why do we need some level of control? -

#cost

๐Ÿ’ฐ Ways to reduce your AI costs -

๐Ÿ’ฐ What is the cheapest PDM tool out there? -

#coupling

๐Ÿ”— Integration, not isolation -

๐Ÿ”— Coupling -

#creativity

โœ๏ธ Effective Communication (Sketching) -

Creativity -

#csv

๐ŸŒฑ๐Ÿ“ˆ Simplicity scales -

๐Ÿ“ˆ What is the quickest way to store and track data? -

#culture

๐Ÿ—‚๏ธ Git has an unfortunate name -

๐Ÿ“ง Top vs bottom posting in email -

๐ŸŽฏ Rituals and Culture -

๐ŸŒฑ Culture -

#customer

๐Ÿค Modern product development is a collaborative endeavor -

๐Ÿ‘ค Who is our "customer"? -

๐Ÿ‘ฅ Your team as the customer -

๐Ÿ‘ฅ Who is the customer in organizational hierarchy? -

๐Ÿ‘ค Confusion about when we are the customer -

๐Ÿ•Š๏ธ Simple -- from whose perspective? -

#daily

๐ŸŽ‰ 200 posts -

๐ŸŽ† 100 daily emails -

๐Ÿ”ง What will you improve today? -

#data

๐Ÿ“Š Simple data formats + powerful tools scale -

๐Ÿ“ The file dilemma -

๐Ÿ“ˆ What is the quickest way to store and track data? -

๐Ÿ‘Œ Struggling to scale your IoT system? Simplify your data. -

#data structures

๐Ÿ”— Coupling -

๐ŸŒฑ๐Ÿ“ˆ Simplicity scales -

#dates

๐Ÿ“… Dates in filenames -

#debt

๐Ÿ”„ Open loops -> technical debt -

โœ… The problem with software -

#debugging

๐Ÿ”Ž Seeing patterns -

#deep work

๐Ÿ‘ท The tension between solo and collaborative work -

#demo

โœจ Demos vs. Products -

#dependencies

๐ŸŽฒ Isn't it risky to update your dependencies? -

๐Ÿ’ธ The cost of updating dependencies, or not -

#deployment

๐Ÿš€ Do you own your deployment? -

#design

๐Ÿ“š Without docs -

#details

๐Ÿค Handling the small details -

#different

๐ŸŽ† Do something different -

#discipline

๐ŸŽ‰ 200 posts -

#disipline

๐Ÿค Keeping commitments -

#distributed

๐Ÿ”— Connected systems are different -

#documentation

๐Ÿ“š Without docs -

๐Ÿ“š Documentation never has to go out of date again -

๐Ÿ“š Keep documentation close to the design/code -

๐Ÿ“ Document "why" not "how" -

๐Ÿ’ฐ Ways to reduce your AI costs -

๐Ÿ“ Git* solves the problem of managing files -

๐Ÿ”„ AI and documentation - close the loop -

๐Ÿค– AI is the new compiler -

โœ๏ธ Effective communication (Written) -

๐Ÿ”„ Flipping the playbook for AI coding -

๐Ÿ“ Documentation is part of the process, not an afterthought -

๐Ÿ“ Personal vs. collaborative documentation -

๐Ÿ™‹ How to help yourself? -

#drawing

๐Ÿšด The power of movement -

โœ๏ธ Effective Communication (Sketching) -

๐ŸŽจ Effective Communication (Drawing) -

#dry

๐Ÿงช Abstractions and Platforms -

#email

โœ๏ธ Effective communication (Written) -

๐Ÿ“ง Top vs bottom posting in email -

โœ‰๏ธ Email filters -

๐Ÿ“ง Effective email is either a pointer or notification -

๐Ÿ“ง Inbox zero -

#embedded

๐Ÿ”— Integration, not isolation -

#engineering

๐Ÿ“š Without docs -

#errors

โš ๏ธ When things go wrong ... -

#experience

๐Ÿ“ What is my process for capturing experience? (part 3) -

๐Ÿ“ What is my process for capturing experience? (part 2) -

๐Ÿ“ What is my process for capturing experience? -

๐Ÿง  How to leverage experience? -

๐Ÿ”ญ How to encourage vision? -

๐Ÿง ๐Ÿ”ญ The tension of experience and vision -

๐Ÿง ๐Ÿ”ญ Experience and Vision -

๐Ÿ“Š Past performance ... -

๐Ÿ›ค๏ธ Two paths with experience -

#experts

๐ŸŽ“ The problem with experts -

#fallibility

โš ๏ธ Toward a Theory of Medical Fallibility -

#false

โš–๏ธ False vs Real Platform Development -

#feedback

๐Ÿ”„ Closed-loop engineering -

๐Ÿ”„ Closed-loop humans -

๐Ÿ”„ Look for closed loops -

๐Ÿ”„ Close the loop with AI -

๐ŸŽ‰ 200 posts -

๐Ÿ”„ Open loops -> technical debt -

#files

๐Ÿ“ Git* solves the problem of managing files -

๐Ÿ“ The file dilemma -

#finish

๐Ÿ Easy to start vs. easy to finish -

#focus

๐Ÿณ Preparation - lessons from the kitchen -

#friction

๐Ÿฅฃ The two ingredients for agility -

๐Ÿ† What is the #1 purpose of YOUR Platform? -

#future

๐Ÿ“ Document "why" not "how" -

What is the role of vision? -

๐Ÿ”ฎ Preparing for the future -

โฐ The present or the future? -

โ“ But what if ... -

#git

๐Ÿ’ฐ What is the cheapest PDM tool out there? -

๐Ÿ—‚๏ธ Git has an unfortunate name -

๐Ÿ“ Git* solves the problem of managing files -

๐Ÿš€ Git driven CD -- you know what got deployed -

๐Ÿ› ๏ธ Another reason to self-host Gitea -

๐Ÿ› ๏ธ Git* -- the new standard for workflow -

๐Ÿ” The importance of small Git commits/pull-requests -

๐Ÿ” The importance of Git Commit/Push often -

๐Ÿ“ง Inbox zero -

๐Ÿ˜Š How can you make your commercial source code customers happy? -

๐Ÿ“Œ Where do you put stuff? -

๐Ÿ—๏ธ What is the best tool for private Git repos? -

๐Ÿ™ Github and why does it matter? -

#gitea

๐Ÿ› ๏ธ Git* -- the new standard for workflow -

๐Ÿ˜Š How can you make your commercial source code customers happy? -

๐Ÿ—๏ธ What is the best tool for private Git repos? -

#github

๐Ÿ› ๏ธ Git* -- the new standard for workflow -

#gitlab

๐Ÿ› ๏ธ Git* -- the new standard for workflow -

#goals

๐Ÿ† Goals vs. Systems -

#golden

๐Ÿšซ No Golden Machines -

#google

๐Ÿ” You are not Google -

#growth

๐Ÿ“ˆ What do we mean by scaling? -

#habits

๐Ÿ”„ Closed-loop humans -

โœ๏ธ Effective Communication (Sketching) -

๐Ÿ’ญ Thinking, Designing, Developing, Engineering ... -

๐Ÿ’ช Habits -- a critical ingredient in YOUR Personal Platform -

#hack

โš ๏ธ Hack-it, ship-it, forget-it ... -

#hardware

โ™ป๏ธ How to iterate quickly on hardware -

#headset

๐ŸŽง Use a headset optimized for calls -

#help

๐Ÿ™‹ How to help yourself? -

#hiring

โš™๏ธ Fix systems, not people -

#humility

๐Ÿ™ Humility -

#improvement

๐Ÿ›Kernighan's Law -

๐Ÿ”„ Closed-loop engineering -

๐Ÿ”„ Closed-loop humans -

๐Ÿ”„ Look for closed loops -

๐Ÿ”„ Close the loop with AI -

๐Ÿ”„ AI and documentation - close the loop -

๐Ÿ”„ Open loops -> technical debt -

โฌ†๏ธ The business case for improvement -

โฌ†๏ธ The path of improvement -

โฌ†๏ธ What is improvement? -

โšก Improve development efficiency, reduce technical debt -

๐Ÿ’ช Good enough is not good enough -

๐Ÿ”ง What will you improve today? -

#innovation

โฐ A platform stuck in time -

#integration

๐Ÿ“ The file dilemma -

๐Ÿ”— Integration, not isolation (part 2) -

๐Ÿ”— Integration, not isolation -

โœ… Guarantees -

๐Ÿ› ๏ธ The defining characteristic of a good workflow tool -

๐Ÿค Integrate early -

Creativity -

#iot

๐Ÿ‘Œ Struggling to scale your IoT system? Simplify your data. -

#iteration

โœ‚๏ธ YAGNI -

๐Ÿšด The power of movement -

๐Ÿ”„ AI and documentation - close the loop -

โ™ป๏ธ How to iterate quickly on hardware -

๐Ÿ” The importance of Git Commit/Push often -

#kids

What can kids teach us about platforms? -

#law

๐Ÿ“ Goodhart's law -

#learning

๐Ÿ”„ Closed-loop engineering -

๐Ÿšด The power of movement -

๐Ÿ”„ Closed-loop humans -

๐Ÿ”„ Look for closed loops -

๐Ÿ”„ Close the loop with AI -

๐Ÿ“น Effective Communication (Video) -

#levels

๐Ÿ” Support from the top -

๐Ÿ—๏ธ Three levels of YOUR Platform -

#liability

โš–๏ธ Code is a liability, not an asset -

๐ŸŒฑ OSS can decrease or increase your code liability -

#lifecycle

โœจ Demos vs. Products -

๐Ÿ”„ Lifecycle management in dynamic systems -

#linux

๐Ÿ“ The file dilemma -

๐Ÿš€ How can Arch Linux get by without releases? -

#long

๐Ÿ“ˆ What do we mean by scaling? -

๐Ÿ The long game -

#maintenance

๐Ÿ›Kernighan's Law -

๐Ÿงฉ Composing is hard, complexity is easy -

๐Ÿ”ง How to keep a product maintainable? -

๐Ÿ’ช Good enough is not good enough -

๐Ÿ”ง What makes a good Yocto BSP? -

โš ๏ธ Hack-it, ship-it, forget-it ... -

๐Ÿ—๏ธ Three levels of YOUR Platform -

โš–๏ธ False vs Real Platform Development -

๐Ÿ The long game -

๐Ÿ”น Simplicity -

โœจ The Beauty of Constraints -

#management

๐Ÿ“ Git* solves the problem of managing files -

๐Ÿ‘ฅ Everybody Works and the impact on meetings -

๐Ÿ” Support from the top -

#markdown

๐ŸŒฑ๐Ÿ“ˆ Simplicity scales -

๐Ÿ“ Personal vs. collaborative documentation -

๐Ÿ“ง Inbox zero -

#math

What can kids teach us about platforms? -

#meetings

๐ŸŽง Effective communication (Audio) -

๐Ÿ‘ฅ Alternatives to meetings -

๐Ÿ‘ฅ Everybody Works and the impact on meetings -

๐Ÿ‘ฅ Efficient meetings -

๐Ÿ‘ฅ Meetings and human relationships -

๐Ÿ‘ฅ Why meetings? -

๐ŸŽง Use a headset optimized for calls -

#meta

๐Ÿ‘‹ Introduction -

#metrics

๐Ÿ“ Goodhart's law -

#monorepo

๐Ÿ”Ž Seeing patterns -

#naming

๐Ÿ“… Dates in filenames -

๐Ÿท๏ธ How do you consistently name things? -

#notes

๐Ÿ“ Personal vs. collaborative documentation -

๐Ÿ”ง What is your most important tool? -

#open

๐Ÿ”ญ Text based formats and command-line tools are the future -

#optimization

๐Ÿ’ฐ Ways to reduce your AI costs -

โš–๏ธ Architecture vs. Optimization -

#organic

๐ŸŒฑ Culture -

#organization

๐Ÿ”„ Open loops -> technical debt -

๐Ÿ” How to get the little things done? -

๐Ÿ“Œ Where do you put stuff? -

#oss

๐Ÿ—‚๏ธ Git has an unfortunate name -

๐Ÿ“ง Top vs bottom posting in email -

๐Ÿค Modern product development is a collaborative endeavor -

๐Ÿง‘โ€๐Ÿ’ป How can we increase developer productivity? -

๐ŸŒฑ OSS can decrease or increase your code liability -

๐Ÿ˜Š How can you make your commercial source code customers happy? -

๐Ÿš€ Advanced technology and small players -

๐Ÿค What happens when someone else tries to use your work? -

๐Ÿ™ Github and why does it matter? -

๐Ÿ” Tracking upstream and why does it matter? -

๐Ÿ”ง What makes a good Yocto BSP? -

๐ŸŒฑ Culture -

#other

๐Ÿ†š What is the difference between YOUR Platform and other platforms? -

#others

๐Ÿ‘ท Do we make more work for others or less? -

#own

๐Ÿ’ฐ Owning YOUR platform is not more expensive -

#partitioning

๐ŸŒฑ When edge nodes grow up -

๐Ÿ”  How do you partition systems? -

#partnumber

๐Ÿญ Semi-structured part numbers -

#patterns

๐Ÿ”Ž Seeing patterns -

#people

๐Ÿ‘ค It's all about the people -

๐Ÿ‘ฅ Platform != People -

#personal

๐ŸŽ‰ 200 posts -

๐Ÿ“ Personal vs. collaborative documentation -

๐Ÿ”ง What is your most important tool? -

๐ŸŽง Use a headset optimized for calls -

๐Ÿ’ช Habits -- a critical ingredient in YOUR Personal Platform -

๐Ÿ—๏ธ Three levels of YOUR Platform -

#phases

๐ŸŒ’๐ŸŒ“๐ŸŒ”The four phases of product development -

#platform

๐ŸŒ€ Complex systems are hard to predict -

๐Ÿ’ฐ What is the cheapest PDM tool out there? -

๐Ÿ“ The file dilemma -

โœจ Anyone can write scripts now -

๐Ÿ“ˆ What do we mean by scaling? -

๐ŸŒฑ๐Ÿ“ˆ Simplicity scales -

๐Ÿงฉ The three legs of YOUR Platform -

โœ… The Platform Test -

๐Ÿ”„ What is YOUR Platform? (v2) -

๐Ÿข What is your Platform? -

#pomodoro

๐Ÿ” How to get the little things done? -

#preparation

๐Ÿณ Preparation - lessons from the kitchen -

#present

โฐ The present or the future? -

#proactive

โšก Are your processes proactive or reactive? -

#problem

๐Ÿถ Lessons from a 1-year old dog -

๐Ÿ” Solving problems or symptoms? -

#process

๐Ÿ“š Without docs -

๐ŸŒ€ Complex systems are hard to predict -

๐Ÿ”„ Look for closed loops -

๐Ÿ”„ Close the loop with AI -

๐Ÿค– AI is the new compiler -

๐ŸŽ‰ 200 posts -

๐Ÿ”— Integration, not isolation (part 2) -

๐Ÿ”„ Open loops -> technical debt -

๐Ÿ“ What is my process for capturing experience? (part 3) -

๐Ÿ“ What is my process for capturing experience? (part 2) -

๐Ÿ“ What is my process for capturing experience? -

๐Ÿง  How to leverage experience? -

๐Ÿš€ Git driven CD -- you know what got deployed -

๐Ÿ”„ The secret to process -

โš™๏ธ Fix systems, not people -

๐Ÿงฉ The three legs of YOUR Platform -

๐Ÿ’ญ Thinking, Designing, Developing, Engineering ... -

โšก Are your processes proactive or reactive? -

โš ๏ธ When things go wrong ... -

#product

๐Ÿ’ฐ What is the cheapest PDM tool out there? -

โœจ Demos vs. Products -

#productivity

๐Ÿ“š Documentation never has to go out of date again -

๐Ÿ“š Keep documentation close to the design/code -

๐Ÿ”„ Close the loop with AI -

๐Ÿค– AI is the new compiler -

โœจ Anyone can write scripts now -

โœ๏ธ Effective Communication (Sketching) -

๐ŸŽจ Effective Communication (Drawing) -

๐Ÿ“น Effective Communication (Video) -

๐Ÿ“ธ Effective Communication (Images) -

๐ŸŽง Effective communication (Audio) -

๐Ÿง‘โ€๐Ÿ’ป How can we increase developer productivity? -

#programming

โš–๏ธ Code is a liability, not an asset -

โœ‚๏ธ YAGNI -

๐Ÿงฉ Composing is hard, complexity is easy -

๐Ÿ”„ Flipping the playbook for AI coding -

๐Ÿง‘โ€๐Ÿ’ป The first step in AI coding -

๐Ÿง‘โ€๐Ÿ’ป Will AI cause coding to disappear? -

#reflection

๐Ÿ“ What is my process for capturing experience? (part 3) -

๐Ÿชž Platform reflection -

#relationships

๐Ÿ‘ฅ Meetings and human relationships -

#release

๐Ÿ”„ When to update application dependencies? -

๐ŸŒฟ A natural way to get more testing/automation -

โฉ Get on with it ... -

๐Ÿ”„ What is the best software release frequency? -

๐Ÿš€ How can Arch Linux get by without releases? -

๐Ÿš€ Why are releases important? -

๐Ÿ“„ Who is a changelog for? -

#reliability

โœจ The easiest path to reliability ... -

#reliablility

๐Ÿ›ก๏ธ How to get to secure and reliable -

#reuse

โ™พ๏ธ It's about not starting over every time -

#risk

๐ŸŽฒ Isn't it risky to update your dependencies? -

#rituals

๐ŸŽฏ Rituals and Culture -

#satisfaction

๐Ÿ˜Š Joy -

#scalability

๐Ÿ“ The file dilemma -

#scaling

๐Ÿ“Š Simple data formats + powerful tools scale -

๐Ÿ“ˆ What do we mean by scaling? -

๐Ÿงฉ Composing is hard, complexity is easy -

๐ŸŒฑ๐Ÿ“ˆ Simplicity scales -

๐Ÿ“ˆ Why GUI development tools don't scale -

โš–๏ธ Horizontal vs Vertical Scaling -

๐Ÿ‘Œ Struggling to scale your IoT system? Simplify your data. -

๐Ÿ“ˆ Scaling -

๐Ÿ“ˆ Two ways to scale -

#screencast

๐Ÿ‘ฅ Alternatives to meetings -

#scripting

โœจ Anyone can write scripts now -

#security

๐Ÿ›ก๏ธ How to get to secure and reliable -

#self-hosting

๐Ÿ› ๏ธ Another reason to self-host Gitea -

#server

๐Ÿšซ No Golden Machines -

#service

๐Ÿ‘ค Confusion about when we are the customer -

#shell

๐Ÿ”ง envsetup.sh -- a very useful automation technique -

#shipping

๐Ÿ’ญ Thinking, Designing, Developing, Engineering ... -

๐Ÿ† What is the #1 purpose of YOUR Platform? -

#short

๐Ÿ The long game -

#silos

๐ŸŒฝ What is the easiest way to avoid silos? -

#simplicity

โš–๏ธ Code is a liability, not an asset -

โœ‚๏ธ YAGNI -

๐Ÿ›Kernighan's Law -

๐Ÿ“Š Simple data formats + powerful tools scale -

๐Ÿงฉ Composing is hard, complexity is easy -

๐ŸŽผ Compose software like music -

๐ŸŒฑ๐Ÿ“ˆ Simplicity scales -

๐Ÿ‘Œ Struggling to scale your IoT system? Simplify your data. -

๐ŸŒ… Simple stuff is boring -

๐Ÿช™ Complexity and Simplicity -- two sides of the same coin -

โฌ†๏ธ What is improvement? -

๐Ÿ•Š๏ธ Simple -- from whose perspective? -

๐Ÿ•Š๏ธ Simple to maintain vs simple to implement -

๐Ÿ•Š๏ธ Simple to use vs simple to implement -

What can kids teach us about platforms? -

โœจ The easiest path to reliability ... -

๐Ÿ” Where do reliability/stability problems typically come from? -

๐ŸŒ Complex Systems, Simple Platforms -

๐Ÿ”น Simplicity -

#size

๐Ÿœ The smaller you are, the more import YOUR Platform is -

#soc

๐Ÿš€ Advanced technology and small players -

#software

โœ‚๏ธ YAGNI -

๐Ÿงฉ Composing is hard, complexity is easy -

#start

๐Ÿ Easy to start vs. easy to finish -

#steps

๐Ÿ‘ฃ What are the first steps? -

#steve-jobs

๐Ÿง‘โ€๐Ÿ’ป How can we increase developer productivity? -

Creativity -

#strategy

๐Ÿ“ˆ What do we mean by scaling? -

#symptom

๐Ÿถ Lessons from a 1-year old dog -

๐Ÿ” Solving problems or symptoms? -

#system

๐Ÿ”— Integration, not isolation -

#systems

๐ŸŒ€ Complex systems are hard to predict -

๐Ÿ”„ Closed-loop engineering -

๐Ÿ”„ Look for closed loops -

๐ŸŒฝ What is the easiest way to avoid silos? -

๐Ÿ‘ค It's all about the people -

๐Ÿ† Goals vs. Systems -

๐Ÿ—๏ธ Platforms are for building systems -

#team

๐ŸŽง Effective communication (Audio) -

๐Ÿค Modern product development is a collaborative endeavor -

๐Ÿ‘ท Make less work for others, part 2 -

๐Ÿ›ค๏ธ Two paths -

๐Ÿ‘ฅ Your team as the customer -

๐Ÿ“ Personal vs. collaborative documentation -

๐Ÿค What happens when someone else tries to use your work? -

#technical debt

โš–๏ธ Code is a liability, not an asset -

๐Ÿ’ธ Technical debt -

๐Ÿ›ค๏ธ Two paths -

โšก Improve development efficiency, reduce technical debt -

๐Ÿ’ธ The cost of updating dependencies, or not -

#technology

๐Ÿ’ฐ What is the cheapest PDM tool out there? -

๐Ÿ Easy to start vs. easy to finish -

๐Ÿš€ Advanced technology and small players -

๐Ÿ’ป What is the purpose of technology? -

๐Ÿ” Where do reliability/stability problems typically come from? -

#test

โœ”๏ธ Legacy code -

โœ… The Platform Test -

#testing

๐Ÿ”„ Flipping the playbook for AI coding -

โžก๏ธ Frontload the boring stuff -

๐ŸŒฟ A natural way to get more testing/automation -

โœ… Guarantees -

#tests

๐Ÿ™‹ How to help yourself? -

#time

โฐ A platform stuck in time -

#time-management

๐Ÿ” How to get the little things done? -

#tool

๐Ÿ”ง What is your most important tool? -

#tooling

๐Ÿฅฃ The two ingredients for agility -

#tools

๐Ÿ“Š Simple data formats + powerful tools scale -

๐Ÿ“š Keep documentation close to the design/code -

๐Ÿ’ฐ What is the cheapest PDM tool out there? -

๐Ÿค– AI is the new compiler -

โœจ Anyone can write scripts now -

โœ๏ธ Effective Communication (Sketching) -

๐ŸŽจ Effective Communication (Drawing) -

๐Ÿ“น Effective Communication (Video) -

๐Ÿ“ธ Effective Communication (Images) -

๐ŸŽง Effective communication (Audio) -

๐Ÿ“ˆ Why GUI development tools don't scale -

๐Ÿ› ๏ธ The defining characteristic of a good workflow tool -

๐Ÿ› ๏ธ The critical features of workflow tools -

๐Ÿ› ๏ธ Selecting tools -

๐Ÿ› ๏ธ Two classes of tools -

๐ŸŽง Use a headset optimized for calls -

๐Ÿšซ No Golden Machines -

#transparency

๐Ÿ” The importance of small Git commits/pull-requests -

#trust

๐Ÿค๐Ÿ” Trust, but verify -

#truth

โš–๏ธ Truth is discovered, not invented -

#update

โœ… The problem with software -

๐Ÿ”„ The business model for updates -

๐Ÿ”„ The biggest benefit to frequent updates -

๐ŸŽฒ Isn't it risky to update your dependencies? -

๐Ÿ”„ What is the first thing you should implement? -

#upstream

๐Ÿ” Tracking upstream and why does it matter? -

#users

๐Ÿ‘ฅ Who are users? -

๐Ÿ•Š๏ธ Simple to use vs simple to implement -

#value

๐Ÿ‘ค Who is our "customer"? -

๐Ÿ“ˆ How does your product value increase after the initial sale? -

#verification

๐Ÿค๐Ÿ” Trust, but verify -

#video

๐Ÿ“น Effective Communication (Video) -

#vision

๐Ÿ”ญ How to encourage vision? -

๐Ÿง ๐Ÿ”ญ The tension of experience and vision -

๐Ÿง ๐Ÿ”ญ Experience and Vision -

๐Ÿ“Š Past performance ... -

What is the role of vision? -

#wealth

๐ŸŒป Downstream, things should be better -

#why

๐Ÿ“š Without docs -

#work

๐Ÿ‘ท Make less work for others, part 2 -

๐Ÿ‘ท Do we make more work for others or less? -

#workflow

๐Ÿ“Š Simple data formats + powerful tools scale -

๐Ÿ“š Documentation never has to go out of date again -

๐Ÿ“š Keep documentation close to the design/code -

๐Ÿ’ฐ What is the cheapest PDM tool out there? -

๐Ÿ“ธ Effective Communication (Images) -

๐Ÿค– How I use Claude Code to help publish this blog -

๐Ÿ‘ฅ Alternatives to meetings -

๐Ÿฅฃ The two ingredients for agility -

๐Ÿ› ๏ธ Git* -- the new standard for workflow -

๐Ÿ› ๏ธ The defining characteristic of a good workflow tool -

๐Ÿ› ๏ธ The critical features of workflow tools -

๐Ÿ˜Š How can you make your commercial source code customers happy? -

#writing

๐Ÿšด The power of movement -

โœ๏ธ Effective communication (Written) -

๐Ÿค– How I use Claude Code to help publish this blog -

๐ŸŽ† 100 daily emails -

#yagni

โš–๏ธ Code is a liability, not an asset -

โœ‚๏ธ YAGNI -

๐Ÿงช Abstractions and Platforms -

#yocto

๐Ÿ™ Github and why does it matter? -

๐Ÿ” Tracking upstream and why does it matter? -

๐Ÿ”ง What makes a good Yocto BSP? -