A bit of inspiration for building YOUR Platform.

163 Tags

#abstraction3 #accessibility1 #ai4 #arch2 #architecture3 #asset1 #automation5 #BCR1 #BSP3 #business1 #cad1 #cd2 #Certainty1 #change1 #changelog1 #checklist2 #ci1 #collaboration4 #commitments1 #community4 #consistency5 #constraints2 #context1 #control4 #coupling1 #creativity1 #csv1 #culture2 #customer5 #daily2 #data2 #data structures1 #dates1 #debt1 #debugging1 #deep work1 #demo1 #dependencies2 #deployment1 #details1 #different1 #disipline1 #distributed1 #documentation3 #dry1 #email3 #errors1 #experience9 #experts1 #fallibility1 #false1 #finish1 #focus1 #friction1 #future4 #git10 #gitea3 #github1 #gitlab1 #goals1 #golden1 #google1 #habits2 #hack1 #headset1 #help1 #hiring1 #humility1 #improvement6 #innovation1 #integration4 #iot1 #iteration1 #kids1 #levels2 #liability1 #lifecycle2 #linux1 #long1 #maintenance9 #management2 #markdown2 #math1 #meetings5 #meta1 #monorepo1 #naming2 #notes2 #optimization1 #organic1 #organization2 #oss9 #other1 #others1 #own1 #partitioning2 #partnumber1 #patterns1 #people2 #personal5 #phases1 #platform4 #pomodoro1 #preparation1 #present1 #proactive1 #problem2 #process11 #product1 #productivity1 #programming1 #reflection2 #relationships1 #release6 #reliability1 #reliablility1 #reuse1 #risk1 #rituals1 #satisfaction1 #scale1 #scaling2 #security1 #self-hosting1 #server1 #service1 #shell1 #shipping2 #short1 #silos1 #simplicity12 #size1 #soc1 #start1 #steps1 #steve-jobs2 #symptom2 #systems4 #team5 #technical debt4 #technology4 #test2 #testing3 #tests1 #time1 #time-management1 #tool1 #tools6 #transparency1 #trust1 #truth1 #update5 #upstream1 #users2 #value2 #verification1 #vision5 #wealth1 #work2 #workflow4 #writing1 #yagni1 #yocto3

#abstraction

Abstractions and Platforms -

Coupling -

What is a good abstraction? -

#accessibility

Effective email is either a pointer or notification -

#ai

🤖 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

➡️ Frontload the boring stuff -

Abstractions and Platforms -

Architecture vs. Optimization -

#asset

🌱 OSS can decrease or increase your code liability -

#automation

🌿 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

⬆️ 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? -

#checklist

✅ The problem with software -

🛤️ Two paths with experience -

#ci

How to help yourself? -

#collaboration

👷 The tension between solo and collaborative work -

🛠️ Selecting tools -

The three legs of YOUR Platform -

Inbox zero -

#commitments

Keeping commitments -

#community

Advanced technology and small players -

Github and why does it matter? -

Tracking upstream and why does it matter? -

What makes a good Yocto BSP? -

#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 -

#context

Effective email is either a pointer or notification -

#control

🕹️ What can we control? -

Control is a scary thing -

What is control? -

Why do we need some level of control? -

#coupling

Coupling -

#creativity

Creativity -

#csv

📈 What is the quickest way to store and track data? -

#culture

Rituals and Culture -

Culture -

#customer

👤 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

100 daily emails -

What will you improve today? -

#data

📈 What is the quickest way to store and track data? -

👌 Struggling to scale your IoT system? Simplify your data. -

#data structures

Coupling -

#dates

Dates in filenames -

#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? -

#details

🤏 Handling the small details -

#different

Do something different -

#disipline

Keeping commitments -

#distributed

🔗 Connected systems are different -

#documentation

📝 Documentation is part of the process, not an afterthought -

Personal vs. collaborative documentation -

How to help yourself? -

#dry

Abstractions and Platforms -

#email

✉️ Email filters -

Effective email is either a pointer or notification -

Inbox zero -

#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 -

#finish

Easy to start vs. easy to finish -

#focus

Preparation - lessons from the kitchen -

#friction

What is the #1 purpose of YOUR Platform? -

#future

What is the role of vision? -

Preparing for the future -

The present or the future? -

But what if ... -

#git

🚀 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 -

#habits

Thinking, Designing, Developing, Engineering ... -

Habits -- a critical ingredient in YOUR Personal Platform -

#hack

Hack-it, ship-it, forget-it ... -

#headset

Use a headset optimized for calls -

#help

How to help yourself? -

#hiring

⚙️ Fix systems, not people -

#humility

Humility -

#improvement

⬆️ 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

✅ Guarantees -

🛠️ The defining characteristic of a good workflow tool -

🤝 Integrate early -

Creativity -

#iot

👌 Struggling to scale your IoT system? Simplify your data. -

#iteration

The importance of Git Commit/Push often -

#kids

What can kids teach us about platforms? -

#levels

Support from the top -

Three levels of YOUR Platform -

#liability

🌱 OSS can decrease or increase your code liability -

#lifecycle

Demos vs. Products -

Lifecycle management in dynamic systems -

#linux

🚀 How can Arch Linux get by without releases? -

#long

The long game -

#maintenance

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

👥 Everybody Works and the impact on meetings -

Support from the top -

#markdown

Personal vs. collaborative documentation -

Inbox zero -

#math

What can kids teach us about platforms? -

#meetings

👥 Everybody Works and the impact on meetings -

👥 Efficient meetings -

👥 Meetings and human relationships -

👥 Why meetings? -

Use a headset optimized for calls -

#meta

Introduction -

#monorepo

Seeing patterns -

#naming

Dates in filenames -

How do you consistently name things? -

#notes

Personal vs. collaborative documentation -

What is your most important tool? -

#optimization

Architecture vs. Optimization -

#organic

Culture -

#organization

How to get the little things done? -

Where do you put stuff? -

#oss

🧑‍💻 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

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

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

📝 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

Demos vs. Products -

#productivity

🧑‍💻 How can we increase developer productivity? -

#programming

🧑‍💻 Will AI cause coding to disappear? -

#reflection

📝 What is my process for capturing experience? (part 3) -

Platform reflection -

#relationships

👥 Meetings and human relationships -

#release

🌿 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 -

#scale

📈 Scaling -

#scaling

⚖️ Horizontal vs Vertical Scaling -

Two ways to scale -

#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

👌 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 -

#start

Easy to start vs. easy to finish -

#steps

What are the first steps? -

#steve-jobs

🧑‍💻 How can we increase developer productivity? -

Creativity -

#symptom

Lessons from a 1-year old dog -

Solving problems or symptoms? -

#systems

🌽 What is the easiest way to avoid silos? -

👤 It's all about the people -

Goals vs. Systems -

Platforms are for building systems -

#team

👷 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

💸 Technical debt -

🛤️ Two paths -

Improve development efficiency, reduce technical debt -

The cost of updating dependencies, or not -

#technology

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

➡️ 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? -

#tools

🛠️ 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 -

#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 -

#work

👷 Make less work for others, part 2 -

👷 Do we make more work for others or less? -

#workflow

🛠️ 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

100 daily emails -

#yagni

Abstractions and Platforms -

#yocto

Github and why does it matter? -

Tracking upstream and why does it matter? -

What makes a good Yocto BSP? -