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 -
๐งช What is a good abstraction? -
#accessibility
๐ง Effective email is either a pointer or notification -
#action
#adaptability
๐ Complex systems are hard to predict -
#agile
๐ฅฃ The two ingredients for agility -
#AI
๐ Documentation never has to go out of date again -
๐ Document "why" not "how" -
๐ฐ 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 -
๐ญ 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 -
๐งโ๐ป Will AI cause coding to disappear? -
๐ค What is the role of AI in your platform? -
#arch
๐ 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 -
๐ฟ 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
#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 -
#Certainty
#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
#closed-loop
๐ Closed-loop engineering -
๐ AI and documentation - close the loop -
#coding
โ๏ธ Code is a liability, not an asset -
๐ Keep documentation close to the design/code -
#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 -
๐งฉ The three legs of YOUR Platform -
#commitments
#communication
๐ Document "why" not "how" -
๐๏ธ 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
๐ 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" -
๐ง 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 -
๐ฏ 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 -
#creativity
โ๏ธ Effective Communication (Sketching) -
#csv
๐ What is the quickest way to store and track data? -
#culture
๐๏ธ Git has an unfortunate name -
๐ง Top vs bottom posting in email -
#customer
๐ค Modern product development is a collaborative endeavor -
๐ฅ Your team as the customer -
๐ฅ Who is the customer in organizational hierarchy? -
๐ค Confusion about when we are the customer -
๐๏ธ Simple -- from whose perspective? -
#daily
๐ง What will you improve today? -
#data
๐ Simple data formats + powerful tools scale -
๐ What is the quickest way to store and track data? -
๐ Struggling to scale your IoT system? Simplify your data. -
#data structures
#dates
#debt
๐ Open loops -> technical debt -
โ The problem with software -
#debugging
#deep work
๐ท The tension between solo and collaborative work -
#demo
#dependencies
๐ฒ Isn't it risky to update your dependencies? -
๐ธ The cost of updating dependencies, or not -
#deployment
๐ Do you own your deployment? -
#design
#details
๐ค Handling the small details -
#different
#discipline
#disipline
#distributed
๐ Connected systems are different -
#documentation
๐ 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 -
โ๏ธ Effective communication (Written) -
๐ Flipping the playbook for AI coding -
๐ Documentation is part of the process, not an afterthought -
๐ Personal vs. collaborative documentation -
#drawing
โ๏ธ Effective Communication (Sketching) -
๐จ Effective Communication (Drawing) -
#dry
๐งช Abstractions and Platforms -
โ๏ธ Effective communication (Written) -
๐ง Top vs bottom posting in email -
๐ง Effective email is either a pointer or notification -
#embedded
๐ Integration, not isolation -
#engineering
#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 -
๐ค๏ธ 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 -
๐ Open loops -> technical debt -
#files
๐ Git* solves the problem of managing files -
#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" -
๐ฎ Preparing for the future -
โฐ The present or the future? -
#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 -
๐ 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
#golden
#growth
๐ What do we mean by scaling? -
#habits
โ๏ธ 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
#hiring
โ๏ธ Fix systems, not people -
#humility
#improvement
๐ Closed-loop engineering -
๐ AI and documentation - close the loop -
๐ Open loops -> technical debt -
โฌ๏ธ The business case for improvement -
โฌ๏ธ The path of 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
๐ Integration, not isolation (part 2) -
๐ Integration, not isolation -
๐ ๏ธ The defining characteristic of a good workflow tool -
#iot
๐ Struggling to scale your IoT system? Simplify your data. -
#iteration
๐ 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
#learning
๐ Closed-loop engineering -
๐น Effective Communication (Video) -
#levels
๐๏ธ Three levels of YOUR Platform -
#liability
โ๏ธ Code is a liability, not an asset -
๐ฑ OSS can decrease or increase your code liability -
#lifecycle
๐ Lifecycle management in dynamic systems -
#linux
๐ How can Arch Linux get by without releases? -
#long
๐ What do we mean by scaling? -
#maintenance
๐งฉ 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 Beauty of Constraints -
#management
๐ Git* solves the problem of managing files -
๐ฅ Everybody Works and the impact on meetings -
#markdown
๐ Personal vs. collaborative documentation -
#math
What can kids teach us about platforms? -
#meetings
๐ง Effective communication (Audio) -
๐ฅ Alternatives to meetings -
๐ฅ Everybody Works and the impact on meetings -
๐ฅ Meetings and human relationships -
๐ง Use a headset optimized for calls -
#meta
#metrics
#monorepo
#naming
๐ท๏ธ 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
#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? -
#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
#people
๐ค It's all about the people -
#personal
๐ 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? -
โจ Anyone can write scripts now -
๐ What do we mean by scaling? -
๐งฉ The three legs of YOUR Platform -
๐ What is YOUR Platform? (v2) -
#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
๐ Complex systems are hard to predict -
๐ 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 -
โ๏ธ 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? -
#productivity
๐ Documentation never has to go out of date again -
๐ Keep documentation close to the design/code -
โจ 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 -
๐งฉ 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) -
#relationships
๐ฅ Meetings and human relationships -
#release
๐ When to update application dependencies? -
๐ฟ A natural way to get more testing/automation -
๐ 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
#satisfaction
๐ Joy -
#scalability
#scaling
๐ Simple data formats + powerful tools scale -
๐ What do we mean by scaling? -
๐งฉ Composing is hard, complexity is easy -
๐ Why GUI development tools don't scale -
โ๏ธ Horizontal vs Vertical Scaling -
๐ Struggling to scale your IoT system? Simplify your data. -
#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
#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
#silos
๐ฝ What is the easiest way to avoid silos? -
#simplicity
โ๏ธ Code is a liability, not an asset -
๐ Simple data formats + powerful tools scale -
๐งฉ Composing is hard, complexity is easy -
๐ผ Compose software like music -
๐ Struggling to scale your IoT system? Simplify your data. -
๐ช Complexity and Simplicity -- two sides of the same coin -
๐๏ธ 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 -
#size
๐ The smaller you are, the more import YOUR Platform is -
#soc
๐ Advanced technology and small players -
#software
๐งฉ 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? -
#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 -
๐ฝ What is the easiest way to avoid silos? -
๐ค It's all about the people -
๐๏ธ Platforms are for building systems -
#team
๐ง Effective communication (Audio) -
๐ค Modern product development is a collaborative endeavor -
๐ท Make less work for others, part 2 -
๐ฅ 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 -
โก 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
#testing
๐ Flipping the playbook for AI coding -
โก๏ธ Frontload the boring stuff -
๐ฟ A natural way to get more testing/automation -
#tests
#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? -
โจ 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 -
๐ ๏ธ Two classes of tools -
๐ง Use a headset optimized for calls -
#transparency
๐ The importance of small Git commits/pull-requests -
#trust
#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
๐๏ธ Simple to use vs simple to implement -
#value
๐ How does your product value increase after the initial sale? -
#verification
#video
๐น Effective Communication (Video) -
#vision
๐ญ How to encourage vision? -
๐ง ๐ญ The tension of experience and vision -
๐ง ๐ญ Experience and Vision -
#wealth
๐ป Downstream, things should be better -
#why
#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
โ๏ธ Effective communication (Written) -
๐ค How I use Claude Code to help publish this blog -
#yagni
โ๏ธ Code is a liability, not an asset -
๐งช Abstractions and Platforms -
#yocto
๐ Github and why does it matter? -