Ideas to write about

Things I believe to be true

  1. Having the original author make a change dwarfs all other maintainability considerations

  2. an assumed level of knowledge is necessary to go to next level

Tiers of abstraction necessary

  1. currently source control, ifs, loops, functions, objects

  2. maybe in the future types systems, ADTs, patterns (like boundaries, side effect management, category theory stuff)

If complexity is the big enemy, what is "simple"?

Rest

Software concepts in business: writing everything in the main function, organizing by function (project management, QA, dev) is the same as organizing by code function (views, models, data) and organizing by domain (products, billing, whatever) lets change happen more cleanly. Also making decisions where knownledge resides.

Reducing complexity through the ancient art of writing shit down

How the internet search experience is broken by the flooding of beginner information.

Reducing complexity through "chunking" — recipes, data input

How to prioritize and structure progress. IE, how much design, when to go end to end

Tradeoffs and consequences for having a ticket for all commits.

Having trouble balancing small commits (under 2 days) with meeting a DoD and having a ticket

Maybe each one could reference what it’s part of, but doesn’t need to complete the ticket. For requirements traceability it doesn’t need to complete the ticket, but does need to reference something.