How I Write Code

Guidelines

• Use case first
• Look for similar problems
• Direct expression of solution to this exact problem
  • Solution should do one thing
  • Never solve a problem you do not have
• How does this generalize?
• What abstraction am I trying to provide?

FLUID:

• Functional
• Loose
• Unit testable
• Introspective
• Dempotent

LIQUID (Bad)

• Large (files, classes and methods)
• Interdependencies
• Quagmire
• Undocumented
• Illegible
• Duplicate code

PLASMA

• Persistence
• Local Reasoning
• Algorithms
• Simplicity
• Modularity
• Abstractions

References

• Faster, Easier, Simpler Vectors - David Stone - CppCon 2021
• Implementing static_vector: How Hard Could it Be? - David Stone - CppCon 2021
• https://github.com/davidstone
• SOLID Revisited : The State of the Matter - Phil Nash - NDC TechTown 2021
• Software Engineering Is About Tradeoffs - Mateusz Pusz - NDC TechTown 2021