Programming
In software engineering there are two things you are trying to get right:
Software Validation - Did we build the right thing?
Software Verification - Did we build the thing right?
Software simplicity is a prerequisite to reliability.
A small, simple API is usually also a hallmark of a well-understood problem.
Run/Right/Fast.
Make the code work I write is working. Then I can make it fast (if necessary). Solving the “correct/clean/performant code” problem all at once can be overwhelming. Don’t be overwhelmed. Solve one at a time.
Reducing the maintenance burden is, for most codebases, the biggest optimization I can do.
Of course it's all about striking a balance, but 99% of the time there is a choice between performance and readability, readability is the right answer. Performance should only be chosen if it is absolutely necessary.
If I write ugly code, anyone who intends to fix a bug or add a feature will not enjoy his work and likely avoid it next time.
Explicit over implicit is almost always better.
Readme driven development is pretty neat. Write the README first as a specification. Then write the code for it. Zeit do it often.
We are about to study the idea of a computational process. Computational processes are abstract beings that inhabit computers. As they evolve, processes manipulate other abstract things called data. The evolution of a process is directed by a pattern of rules called a program. People create programs to direct processes.
Always be looking for patterns. Abstract them always and only when it simplifies.
Persevere in getting an abstraction just right. When you find it, everything will magically fall into place.
The implementation is the design.
Hide whatever the caller shouldn't care about. In particular, you can remove type parameters with appropriate quantification.
Declarative configuration means that you write down the desired state of the world in a configuration and then submit that configuration to a service that takes actions to ensure the desired state becomes the actual state.
Every single feature makes product more complex, makes testing more complex, puts constraints on UI design etc. Controlling feature creep (also by revisiting old features) is very important to keep project healthy. Larger the project, more important it is.
If we take a look at any given line of code in a method, we can nearly always categorize it as serving one of the following roles: 1. Collecting input. 2. Performing work. 3. Delivering output. 4. Handling failures.
Awesome Cold Showers - For when people get too hyped up about things.
Professional Programming - Collection of full-stack resources for programmers.
Awesome Roadmaps - Curated list of awesome software development roadmaps.
Visual Programming Codex - Resources and references for the past and future of visual programming.
Software Foundations series - Broad introduction to the mathematical underpinnings of reliable software.
Exercises in Programming Style - Comprehensive collection of programming styles using a simple computational task, term frequency.
Execute program - Programming lessons.
Best Practices Checklist - List of awesome idiomatic code resources. Rust, Go, Erlang, Ruby, Pony and more.
Sourcetrail - Free and open-source cross-platform source explorer. (HN)
Developer Roadmaps - Community driven roadmaps, articles and resources for developers. (HN) (Code)
