@XAMTO_AI: Many people murmur: Since AI coding is so powerful, do we still need to learn the basics? Yes, and increasingly so. I'm recommending a gem of a project on GitHub: Professional Programming, covering everything from algorithms to system design to code quality. The learning path is clear, not the kind that just throws a list of books at you and leaves you hanging...

X AI KOLs Timeline Tools

Summary

Recommending the Professional Programming project on GitHub, covering programming basics like algorithms, system design, code quality, providing a clear learning path and hands-on exercises, emphasizing the importance of foundational knowledge even in the era of AI coding.

Many people murmur: Since AI coding is so powerful, do we still need to learn the basics? Yes, and increasingly so. I'm recommending a gem of a project on GitHub: Professional Programming, covering everything from algorithms to system design to code quality. The learning path is clear, not the kind that just throws a list of books at you and leaves you hanging. It also includes hardcore practical exercises—like implementing Redis from scratch or writing your own compiler, forcing you to truly apply the knowledge. https://github.com/charlax/professional-programming…
Original Article
View Cached Full Text

Cached at: 06/09/26, 01:36 AM

Many people mutter: with AI coding being so powerful, do we still need to learn the basics? Yes, we do, and more than ever. Let me recommend a treasure of a project on GitHub: Professional Programming. It covers everything from algorithms to system design to code quality, all very clearly. The learning path is clear — not one of those shallow lists that just throw a bunch of books at you and leave you on your own. It also includes hardcore hands-on exercises — like writing Redis from scratch or building your own compiler, forcing you to actually apply the knowledge. https://github.com/charlax/professional-programming…


charlax/professional-programming Source: https://github.com/charlax/professional-programming ## Table of Contents - Professional Programming - about this list - Principles - Contributing to this list - Must-read books - Must-read articles - Other general material and list of resources - Other lists - Books - Articles - Axioms - Courses - Topics - Accounting - Agentic coding - Algorithm and data structures - API design & development - Attitude, habits, mindset - Procrastination - Authentication/authorization - Automation - Best practices - Beyond software engineering & random - Biases - Business - Buy vs. Build - Cache - Career growth - Choosing your next/first opportunity - Getting to Staff Eng - Characters sets - Chess - Clouds - Code reviews - Coding & code quality - Communication - Compilers - Configuration - Continuous Integration (CI) - Data analysis & data science - Databases - Internals - NoSQL - Postgres - Data formats - Data science/data engineering - Debugging - Design (visual, UX, UI, typography) - Design (OO modeling, architecture, patterns, anti-patterns, etc.) - Design: database schema - Design: patterns - Design: simplicity - Dev environment & tools - Docker - Documentation - Dotfiles - Editors & IDE - Vim - Email - Engineering management - Exercises - Experimentation - Fonts - Functional programming (FP) - Games development - Generative AI - Graphics - Hardware - HTTP - Humor - Incident response (oncall, alerting, outages, firefighting, postmortem) - Postmortem - Internet - Interviewing - Kubernetes - Large Language Model (LLM) - Learning & memorizing - Licenses (legal) - Linux (system management) - Low-code/no-code - Low-level, assembly - Machine learning/AI - Math - Marketing - Network - Observability (monitoring, logging, exception handling) - Logging - Error/exception handling - Metrics - Monitoring - Open source - Operating system (OS) - Over-engineering - Performance - Personal knowledge management (PKM) - Personal productivity - Perspective - Privacy - Problem solving - Product management for software engineers - Project management - Programming languages - Python - JavaScript - Garbage collection - Programming paradigm - Public speaking (presenting) - Reading - Refactoring - Regex - Releasing & deploying - Versioning - Checklists - Feature flags - Testing in production - Reliability - Integration patterns (dependency management) - Resiliency - Search - Security - Research papers - Shell (command line) - SQL - State - System administration - System architecture - Architecture patterns - Microservices/splitting a monolith - Scalability - Site Reliability Engineering (SRE) - Technical debt - Testing - Tools - Type system - Typography - Version control (Git) - Work ethics, productivity & work/life balance - Web development - Writing (communication, blogging) - Resources & inspiration for presentations - Keeping up-to-date - Concepts - My other lists # Professional Programming - about this list > Give me six hours to chop down a tree and I will spend the first four sharpening the axe. (Abraham Lincoln) A collection of full-stack resources for programmers. The goal of this page is to make you a more proficient developer. You’ll find only resources that I’ve found truly inspiring, or that have become timeless classics. ## Principles - This page is not meant to be comprehensive. I am trying to keep it light and not too overwhelming. - The selection of articles is opinionated. - I don’t necessarily agree with or endorse every single line that is written in every single one of those resources. The same applies to their authors: I don’t endorse everything each of those authors has said and will ever say. Items: - 🧰 : list of resources - 📖 : book - 🎞 : video/movie extract/movie/talk - 🏙 : slides/presentation - ⭐️ : must-read - 📃 : paper ## Contributing to this list Feel free to open a PR to contribute! I will not be adding everything: as stated above, I am trying to keep the list concise. ## Must-read books I’ve found these books incredibly inspiring: - 📖 The Pragmatic Programmer: From Journeyman to Master (https://pragprog.com/titles/tpp20/): hands-on the most inspiring and useful book I’ve read about programming. - 📖 Code Complete: A Practical Handbook of Software Construction (http://www.amazon.com/Code-Complete-Practical-Handbook-Construction/dp/0735619670): a nice addition to The Pragmatic Programmer, gives you the necessary framework to talk about code. - 📖 Release It! (https://smile.amazon.com/Release-Design-Deploy-Production-Ready-Software/dp/1680502395): this books goes beyond code and gives you best practices for building production-ready software. It will give you about 3 years worth of real-world experience. - 📖 Scalability Rules: 50 Principles for Scaling Web Sites (https://smile.amazon.com/Scalability-Rules-Principles-Scaling-Sites/dp/013443160X) - 📖 The Linux Programming Interface: A Linux and UNIX System Programming Handbook (http://www.amazon.com/The-Linux-Programming-Interface-Handbook/dp/1593272200): outside of teaching you almost everything you need to know about Linux, this book will give you insights into how software evolves, and the value of having simple & elegant interfaces. - 📖 Structure and interpretation of Computer Programs (https://web.mit.edu/6.001/6.037/sicp.pdf) (free): One of the most influential textbooks in Computer Science (written and used at MIT), SICP has been influential in CS education. Byte recommended SICP “for professional programmers who are really interested in their profession”. There are some free books available, including: - 📖 Professional software development (http://mixmastamyk.bitbucket.io/pro_soft_dev/): pretty complete and a good companion to this page. The free chapters are mostly focused on software development processes: design, testing, code writing, etc. - and not so much about tech itself. - 🧰 vhf/free-programming-books (https://github.com/vhf/free-programming-books) - 🧰 EbookFoundation/free-programming-books (https://github.com/EbookFoundation/free-programming-books/tree/main/books) ## Must-read articles - Practical Advice for New Software Engineers (http://product.hubspot.com/blog/practical-advice-for-new-software-engineers) - On Being A Senior Engineer (http://www.kitchensoap.com/2012/10/25/on-being-a-senior-engineer/) - Lessons Learned in Software Development (http://henrikwarne.com/2015/04/16/lessons-learned-in-software-development/): one of those articles that give you years of hard-earned lessons, all in one short article. Must read. - Things I Learnt The Hard Way (https://blog.juliobiason.me/thoughts/things-i-learnt-the-hard-way/) - Spec first, then code - Tests make better APIs - Future thinking is future trashing - Documentation is a love letter to your future self - Sometimes, it’s better to let the application crash than do nothing - Understand and stay away of cargo cult - “Right tool for the job” is just to push an agenda - Learn the basics functional programming - ALWAYS use timezones with your dates - ALWAYS use UTF-8 - Create libraries - Learn to monitor - Explicit is better than implicit - Companies look for specialists but keep generalists longer - The best secure way to deal with user data is not to capture it - When it’s time to stop, it’s time to stop - You’re responsible for the use of your code - Don’t tell “It’s done” when it’s not - Pay attention on how people react to you - Beware of micro-aggressions - Keep a list of “Things I Don’t Know” - Signs that you’re a good programmer (https://skatgame.net/mburo//courses/350/signs-that-you-re-a-good-programmer.html) (not everything in here is great - some of the points are counterproductive) - The instinct to experiment first - Emotional detachment from code and design - Eager to fix what isn’t broken - Fascinated by the incomprehensible - Compelled to teach - Incorruptible patience - A destructive pursuit of perfection - Encyclopedic grasp of the platform - Thinks In Code - When In Rome, Does As Romans Do - Creates their own tools - Indifferent to Hierarchy - Excited by failure - Indifferent to circumstances - Substitutes impulse for commitment - Driven by experiences - 7 absolute truths I unlearned as junior developer (https://monicalent.com/blog/2019/06/03/absolute-truths-unlearned-as-junior-developer/) - Early in your career, you can learn 10x more in a supportive team in 1 year, than coding on your own - Every company has problems, every company has technical debt. - Being overly opinionated on topics you lack real-world experience with is pretty arrogant. - Many conference talks cover proof of concepts rather than real-world scenarios. - Dealing with legacy is completely normal. - Architecture is more important than nitpicking. - Focus on automation over documentation where appropriate. - Having some technical debt is healthy. - Senior engineers must develop many skills besides programming. - We’re all still junior in some areas. - How to Build Good Software (https://knowledge.csc.gov.sg/ethos-issue-21/how-to-build-good-software/) - A good high-level summary of fundamental engineering practices. - The root cause of bad software has less to do with specific engineering choices, and more to do with how development projects are managed. - There is no such thing as platonically good engineering: it depends on your needs and the practical problems you encounter. - Software should be treated not as a static product, but as a living manifestation of the development team’s collective understanding. - Software projects rarely fail because they are too small; they fail because they get too big. - Beware of bureaucratic goals masquerading as problem statements. If our end goal is to make citizens’ lives better, we need to explicitly acknowledge the things that are making their lives worse. - Building software is not about avoiding failure; it is about strategically failing as fast as possible to get the information you need to build something good. - How to be a -10x Engineer (https://taylor.town/-10x) - Nullify the output of 10 engineers. - Hold 10 engineers hostage in a technical discussion. - Waste 10 weeks of wages on cloud costs. - Waste 400 hours of engineering on bad architecture. - Incur 400 hours of bug triage. - A Bunch of Programming Advice I’d Give To Myself 15 Years Ago (https://mbuffett.com/posts/programming-advice-younger-self/) - If you (or your team) are shooting yourselves in the foot constantly, fix the gun - Assess the trade-off you’re making between quality and pace, make sure it’s appropriate for your context - Spending time sharpening the axe is almost always worth it - If you can’t easily explain why something is difficult, then it’s incidental complexity, which is probably worth addressing - Try to solve bugs one layer deeper - Don’t underestimate the value of digging into history to investigate some bugs - Bad code gives you feedback, perfect code doesn’t. Err on the side of writing bad code - Make debugging easier - When working on a team, you should usually ask the question - Shipping cadence matters a lot. Think hard about what will get you shipping quickly and often - Expert Generalists (https://martinfowler.com/articles/expert-generalist.html), martinfowler.com, proposes an interesting take on the “T-shaped engineer” - The Characteristics of an Expert Generalist: Curiosity, Collaborativeness, Customer Focus, Favor Fundamental Knowledge, Blend of Generalist and Specialist Skills, Sympathy for Related Domains - Assessing Expert Generalists: hiring and career progression - Growing Expert Generalists: From Tools to Fundamentals - “Why does our attention keep drifting toward tool expertise? It isn’t because people are shortsighted or lazy; it’s because the fundamentals are hard to see amid the noise.” - Expert Generalists still need Specialists - Expert Generalists in the Age of LLMs - “Similarly to a specialist, an LLM can rapidly answer questions that an Expert Generalist will have when working in a new domain.” - “Rather than looking for “the answer”, they prompt them to generate questions, explaining mechanisms, and providing examples and even tools that help explore the underlying mechanisms of an idea.” ## Other general material and list of resources ### Other lists - liuchong/awesome-roadmaps: A curated list of roadmaps. (https://github.com/liuchong/awesome-roadmaps) ### Books - 📖 The Imposter’s Handbook (https://bigmachine.io/products/the-imposters-handbook) - $30. From the author: “Don’t have a CS Degree? Neither do I - That’s why I wrote this book.” - 📖 The Computer Science Book (https://thecomputersciencebook.com/book/) - 📖 The Software Engineer’s Guidebook (https://www.engguidebook.com/): Gergely Orosz

Similar Articles

@ai_super_niko: https://x.com/ai_super_niko/status/2070299861757616606

X AI KOLs Timeline

This article discusses whether computer professionals still need to learn technical skills in an era where AI can write code. The author argues that surface-level technologies like syntax and APIs are depreciating, but deeper capabilities such as algorithms, design architecture, and judgment become more important. The focus of learning should shift from beginner-level skills to the knowledge required of senior engineers.

@wsl8297: When learning AI, the scariest part is getting stuck at "understanding the theory" and freezing when it's time to write code — not knowing where to start, and unable to find decent practice projects. I unearthed a practical treasure trove on GitHub: AI-Project-Gallery. It collects 30+ high-quality AI projects, covering classic topics like house price prediction and disease classification, as well as hot applications like Gemini chatbot and document generator...

X AI KOLs Timeline

This post shares a curated GitHub repository containing over 30 practical AI projects, covering domains from regression to generative AI, with many end-to-end examples, suitable for learners and developers.

@manateelazycat: AI is powerful, but newcomers in computer science still need to accumulate knowledge to solve complex problems. Let me re-share the computer science foundational books I previously recommended. As for my own reading habits, especially when learning computer science, I prefer books that are easy to understand and explain why the code works the way it does. Only by understanding the underlying principles can you apply them later.

X AI KOLs Timeline

A seasoned developer shares a curated list of computer books accumulated over many years, covering mainstream languages such as Python, C++, Java, and Rust, along with multiple technical fields, emphasizing the importance of building a solid foundation for solving complex problems.

@0x404page: Damn! Brothers! The AI era has already arrived right before our eyes! It's terrifying to think about... 99% of people are still grinding away in 996 work schedules, while truly smart people are already using AI to make money on the side and quickly improve themselves! Freebie lovers, this is hitting you straight in the face!!! I dug up 5 top-notch projects on GitHub for you, all free and open-source practical...

X AI KOLs Timeline

This tweet shares 5 free and open-source GitHub projects, covering practical resources for AI side hustles, programmer side businesses, passive income, etc., encouraging users to leverage the AI era to quickly improve themselves.

@FakeMaidenMaker: Folks, we've dug up another AI engineering treasure: Hands-On-AI-Engineering. Just open-sourced, it already hit 2.3K stars. One repo stuffed with over 50 real AI projects that you can run directly. The most practical part is it doesn't talk about vague theories; each project is a complete little…

X AI KOLs Timeline

Recommends the freshly open-sourced GitHub repo Hands-On-AI-Engineering with 2.3K stars, containing over 50 runnable AI projects covering RAG, AI agent, OCR, and more. Each project provides full code and instructions, suitable for hands-on learning.