More Code More Problems
summary
Argues for mastering languages not frameworks, prefers tiny reusable modules over monolithic stacks, and justifies every line to reduce technical debt; reports PHP has dozens of full‑stack frameworks that force pulling huge code for small features and cites ripping out a Django REST addon for performance. Uses and builds practical tools: funit simple unit tester and ry.php HTTP client, deploys Elasticsearch as a black box, and shows small readable code speeds debugging, testing, and long‑term maintenance.
AI-written summary · about
chapters (16)
- 0:00Start
- 2:40Learn languages, not frameworks
- 4:48Versatility and flexibilty
- 6:28Complexity of full-stack frameworks
- 7:17Build small things
- 8:33Small things with simple purposes
- 8:50Solve single problems
- 9:01Work together & solve big problems
- 9:33Less code is better than more
- 9:45Manage less code
- 12:00Support less code
- 13:48Justify every line
- 16:55Create and use simple, readable code
- 17:49I want code that is easy to verify
- 18:23Readability is a feature
- 22:57Confession
related talks
45m'Writing code that lasts'...or writing code you won't hate tomorrow
01h 47mClean code
59mTechniques for writing high-quality code
39mClean, Concise, Collaborative Code
32mKeeping your code strong
53mIntentional Code - Minimalism in a World of Dogmatic Design
20mGood Code is a Balancing Act
39mYou should stop writing code