One of the most powerful lessons I learned as a programmer was to use combinatoric spaces to my advantage, rather than allowing them to explode into—for example—handwritten source code. This required relaxing, for example, an obsession with static type checking.

https://twitter.com/scheminglunatic/status/1869304249039081677

Instead what I learned was to use static product types to form homogeneous building blocks for large combinatoric spaces, and to organize data transforms around forming those spaces. Choosing actual points in this space becomes a completely dynamic capability.

Early return is actually not great

https://twitter.com/ohmypy/status/1849754238642983332

It is hilarious how controversial this is

@Skytrias [1/n] I haven't covered that yet (I will probably do it in the next part), but I control properties like size, colors, fonts, and some other things with stacks. So, for example, you might push a default size for each axis on the stack (as well as a default font, etc.), then... @Skytrias [2/n] ...if you want to deviate a size, color, font, etc. for a button, you would just push a new value onto the associated stack before the button call, and then pop afterwards.

@AbnerCoimbre @notnullnotvoid @handmade_net I will provide my personal thoughts about Handmade, and maybe we can work towards an understanding of the manifesto, if/how it should be revised, etc. (1/7) @AbnerCoimbre @notnullnotvoid @handmade_net My experiences with @handmade_net have provided a lot of insight here, namely in that Handmade *isn't* just about making things fast, it's about knowing when to allow things to be slow, and reasoning about reality. I like @AbnerCoimbre's "computer literacy" idea here. (2/7)