~/.mathieu

Tag: thought

Createdslips
slips
Metrics only capture things that can be quantified
Createdslips
slips
Cutting metrics is sometimes beneficial
Createdslips
slips
You are what you measure and optimize towards
Createdslips
slips
Vanity metrics can ruin your confidence
Createdslips
slips
Vanity metrics can give false confidence
Createdslips
slips
Misaligned metrics that redirects attention are harmful
Createdslips
slips
Webpage statistics can be a bad metric
Createdslips
slips
As a GM you need to close the impact feedback loop
Createdslips
slips
Impact that goes unnoticed is like having no impact at all
Createdslips
slips
The principle of least surprise frees up mental load
Createdslips
slips
The principle of least surprise
Createdslips
slips
The mind and thoughts are complex
Createdslips
slips
You should give people the benefit of the doubt
Createdslips
slips
Learning in the open
Createdslips
slips
Building in public
Createdslips
slips
Schrödinger backups
Createdslips
slips
Banana software
Createdslips
slips
Tools unleashes the power of structured logging
Createdslips
slips
Structured logs are hard to read as a human
Createdslips
slips
Last responsible moment
Createdslips
slips
Predicting the future is hard
Createdslips
slips
Technological advancements makes skills obsolete
Createdslips
slips
Skills wither without exercise
Createdslips
slips
Growth work is compounding
Createdslips
slips
Keeping things simple is a skill
Createdslips
slips
Frighteningly interesting software
Createdslips
slips
You are a learning opportunity for somebody else
Createdslips
slips
You can learn something from anyone
Createdslips
slips
Don't be afraid to make use of people's knowledge
Createdslips
slips
Discovery requires time
Createdslips
slips
Make yourself replaceable in order to sell your business
Createdslips
slips
Premature optimization is procrastination
Createdslips
slips
Self documenting systems
Createdslips
slips
A successful infrastructure is one you forget about
Createdslips
slips
Basic documentation is a must for system administration
Createdslips
slips
Create characters together
Createdslips
slips
Validate your business idea
Createdslips
slips
Customer feedback
Createdslips
slips
Aggressive timekeeping in meetings reduces meeting time
Createdslips
slips
Being a small startup offers advantages
Createdslips
slips
If you use your own product, you can estimate the value
Createdslips
slips
Going too broad can hurt you
Createdslips
slips
Incremental development
Createdslips
slips
A profitable business model is more important than the startups value
Createdslips
slips
True innovation is usually both vertical and horizontal
Createdslips
slips
Historical data is important for metrics
Createdslips
slips
Micro services should not be the default
Createdslips
slips
Software should be delightfully boring
Createdslips
slips
Mocking factories should be used when mocking test data
Createdslips
slips
Unit tests should be easy to read
Createdslips
slips
Test names should be straightforward
Createdslips
slips
Complex problems might lead to over engineering
Createdslips
slips
Logs and traces can contain PII
Createdslips
slips
Over engineering is bad for a project
Createdslips
slips
Traces are sequences of logs
Createdslips
slips
Rolling stats is fun
Createdslips
slips
Rolling stats is unfair
Createdslips
slips
Downtime & crafting could be a pillar of play
Createdslips
slips
Breaking the boundaries require sacrifice
Createdslips
slips
Players want to do awesome things
Createdslips
slips
Sidecharacter NPCs evolve to important NPCs by players
Createdslips
slips
Improvisation needs to be trained
Createdslips
slips
Be inclusive (roleplaying)
Createdslips
slips
Roleplaying games is about the players
Createdslips
slips
Content history is a core feature