Programming Resources

The Architecture of Open Source Applications - Architects look at thousands of buildings during their training, and study critiques of those buildings written by masters. In contrast, most software developers only ever get to know a handful of large programs well—usually programs they wrote themselves—and never study the great programs of history. As a result, they repeat one another's mistakes rather than building on one another's successes.

Do call yourself a programmer, and other career advice

Don't Call Yourself A Programmer, And Other Career Advice

Software Development Waste - Hacker News discussion

Building the wrong product

product that does not address user business needs
not doing research on users or businesses
ignoring feedback, low user value features

Mismanaging backlog

duplicating work, low value features, delaying bug fixes
working on too many features simultaneously, imbalance of feature work and bug fixing, delaying testing or critical bug fixing

Rework

altering delivered work that should have been done correctly
no clear definition of done

Unnecessarily complex solutions

a more complicated solution than necessary
a missed opportunity to simplify features, user interface, or code
unnecessary feature complexity from the user’s perspective
unnecessary technical complexity
duplicating code, lack of interaction design reuse, overly complex technical design created up-front

Extraneous cognitive load

the costs of unneeded expenditure of mental energy
suffering from technical debt,
inefficient tools and problematic APIs, libraries, and frameworks
unnecessary context switching
inefficient development flow
poorly organized code

Psychological distress

burdening the team with unhelpful stress
low team morale
rush mode
interpersonal or team conflict

Waiting/multitasking

cost of idle time, often hidden by multi-tasking
slow tests or unreliable tests
unreliable acceptance environment
missing information, people, or equipment
context switching from delayed feedback

Knowledge loss

cost of re-acquiring information that the team once knew
team churn
knowledge silos

Ineffective communication

incomplete, incorrect, misleading, inefficient, or absent communication
team size too large
asynchronous communication - distributed teams/stakeholders, opaque processes outside team
imbalance - dominating the conversation; not listening
Inefficient meetings (lack of focus; skipping retros; not discussing blockers each day; meetings running over (e.g. long stand-ups))

History of programming

The A-Z of Programming Languages

History of Infra as Code - talk about history of cloud services, Docker etc

History of Programming Language Conference

An opinionated history of programming languages

Is It Time to Rewrite the Operating System in Rust? - Bryan Cantrill - 2018

Why Isn't Functional Programming the Norm? – Richard Feldman - 2019

Why does "=" mean assignment? - Hillel Wayne

Courses

Open Source Society University - Computer Science

The Good Research Code Handbook

Developer Roadmaps - Python, React, backend, frontend.

6.005 Software Construction - course homepage - notes - introduces fundamental principles and techniques of software development - how to write software that is safe from bugs, easy to understand, and ready for change.

Systematic Program Design - video lectures.

calmcode.io - video tutorials for modern ideas and open source tools (mostly Python)

ines/course-starter-python - course framework for spaCy

./missing-semester - gain proficiency with computing systems (shell, editor, version control) - notes - lecture videos