-
Learning to code can be compared to learning to cook. Not everyone aspires to become a professional chef, but many people learn to cook so they can eat better and more affordable. Similarly, once you remove the pressure of needing to produce professional and scalable code, programming can become a different activity altogether. Just like cooking at home, it is very different from cooking in a commercial kitchen. (An app can be a home-cooked meal)
-
If you don’t know what the problem is, you haven’t fixed it. If you do end up in a situation where you make a change and the problem mysteriously goes away, don’t stop there. Undo the change and see if the problem recurs. If it doesn’t, then the change is probably unrelated to the problem. If undoing the change causes the problem to recur, then figure out why. (John Ousterhout’s favourite sayings)
-
Timelines influence priorities and add accountability. Most things have timelines. Projects, tasks, meetings - nearly everything has an end date. Timelines are needed to clarify expectations and let people know when things will happen. Without timelines, dependencies can’t be managed, and communication breaks down. (Everything should have a timeline)
-
Over the course of the year, it’s become increasingly clear that writing code is one of the things LLMs are most capable of. This isn’t such a big surprise if you think about what they do. The grammar rules of programming languages like Python and JavaScript are much less complicated than those of Chinese, Spanish or English. (Stuff we figured out about AI in 2023)
-
“Move with urgency and focus. A bias for action speeds our learning and delights our users. Focus on what matters most, make fast initial progress, and iterate toward the best outcome.” (a reminder from Stripe’s operating principles)
-
Attention control is critical for changing/increasing/altering motivation. The focus of attention physically determines which synapses in your brain get stronger and which areas of your cortex physically grow in size. The implications of this provide direct guidance for the alteration of behaviours and motivational patterns.
-
Architecting is a series of trade-offs. In architecture, every decision comes with a trade-off. Cost, resilience, and performance are non-functional requirements that often come into tension with each other. As the saying goes, “Everything fails all the time.” Being able to defend against failure means investing in resilience, but performance may pay the price.
-
Good design strives for consistency. Consistent sequences of actions should be required in similar situations; identical terminology should be used in prompts, menus, and help screens; and consistent colour, layout, capitalization, fonts, and so on should be employed throughout. Exceptions, such as required confirmation of the delete command or no echoing of passwords, should be comprehensible and limited in number. @shawn @shawn @ernest @jum-ooo-back-23-nov
-
“Fast learns, slow remembers. Fast proposes, slow disposes. Fast is discontinuous, slow is continuous. Fast and small instructs slow and big by accrued innovation and by occasional revolution. Slow and big controls small and fast by constraint and constancy. Fast gets all our attention, slow has all the power.” Pace layering
Substack edition
Learning to code can be compared to learning to cook. Not everyone aspires to become a professional chef, but many people learn to cook so they can eat better and more affordable. Similarly, once you remove the pressure of needing to produce professional and scalable code, programming can become a different activity altogether. Just like cooking at home, it is very different from cooking in a commercial kitchen. (An app can be a home-cooked meal)
If you don't know what the problem is, you haven't fixed it. If you do end up in a situation where you make a change and the problem mysteriously goes away, don't stop there. Undo the change and see if the problem recurs. If it doesn't, then the change is probably unrelated to the problem. If undoing the change causes the problem to recur, then figure out why. (John Ousterhout’s favourite sayings)
Timelines influence priorities and add accountability. Most things have timelines. Projects, tasks, meetings - nearly everything has an end date. Timelines are needed to clarify expectations and let people know when things will happen. Without timelines, dependencies can't be managed, and communication breaks down. (Everything should have a timeline)
Over the course of the year, it’s become increasingly clear that writing code is one of the things LLMs are most capable of. This isn't such a big surprise if you think about what they do. The grammar rules of programming languages like Python and JavaScript are much less complicated than those of Chinese, Spanish or English. (Stuff we figured out about AI in 2023)
“Move with urgency and focus. A bias for action speeds our learning and delights our users. Focus on what matters most, make fast initial progress, and iterate toward the best outcome.” (from Stripe’s operating principles)
Attention control is critical for changing/increasing/altering motivation. The focus of attention physically determines which synapses in your brain get stronger and which areas of your cortex physically grow in size. The implications of this provide direct guidance for the alteration of behaviours and motivational patterns.
Architecting is a series of trade-offs. In architecture, every decision comes with a trade-off. Cost, resilience, and performance are non-functional requirements that often come into tension with each other. As the saying goes, “Everything fails all the time.” Being able to defend against failure means investing in resilience, but performance may pay the price.
Good design strives for consistency. Consistent sequences of actions should be required in similar situations; identical terminology should be used in prompts, menus, and help screens; and consistent colour, layout, capitalization, fonts, and so on should be employed throughout. Exceptions, such as required confirmation of the delete command or no echoing of passwords, should be comprehensible and limited in number.
“Fast learns, slow remembers. Fast proposes, slow disposes. Fast is discontinuous, slow is continuous. Fast and small instructs slow and big by accrued innovation and by occasional revolution. Slow and big controls small and fast by constraint and constancy. Fast gets all our attention, slow has all the power.” Pace layering