Software Engineering

Watch

• Learning Software Engineering During the Era of AI | Raymond Fu | TEDxCSTU ↗TEDx Talks
• A.I. Revolution | Full Documentary | NOVA | PBS ↗NOVA PBS Official
• Software Testing Explained: How QA is Done Today ↗AltexSoft

Read

• The Mythical Man-Month: Essays on Software Engineering ↗A timeless exposition on the inherent challenges of large software projects, revealing that adding more people to a late project only delays it further.Frederick P. Brooks Jr.
• Design Patterns: Elements of Reusable Object-Oriented Software ↗The definitive catalogue of object-oriented design solutions, providing a common vocabulary for architects to construct robust and flexible systems.Erich Gamma, Richard Helm, Ralph Johnson, John Vlissides
• Clean Code: A Handbook of Agile Software Craftsmanship ↗An indispensable guide to writing maintainable, readable, and efficient code, essential for any professional aspiring to software craftsmanship.Robert C. Martin
• No Silver Bullet - Essence and Accident in Software EngineeringA prescient analysis arguing that no single technological breakthrough will ever fully conquer the inherent complexity of software development.Frederick P. Brooks Jr.
• The Pragmatic Programmer: From Journeyman to Master ↗A practical compendium of wisdom for developers, offering actionable advice on everything from coding practices to career development.Andrew Hunt, David Thomas

Voices to follow

• Martin Fowler ↗His extensive writings and advocacy for agile methodologies, enterprise architecture, and refactoring have profoundly influenced contemporary software development practices.Chief Scientist, ThoughtWorks
• Grady Booch ↗A seminal figure in object-oriented design and the Unified Modeling Language (UML), his contributions are foundational to architecting complex software systems.Chief Scientist for Software Engineering, IBM Research
• Mary Poppendieck ↗She is celebrated for translating lean manufacturing principles into effective strategies for software development, emphasising speed, quality, and customer value.Independent consultant and author
• Robert C. Martin ↗Known as 'Uncle Bob', he champions clean code, agile principles, and software craftsmanship, offering pragmatic guidance for building robust and maintainable systems.Independent consultant and author
• Kent Beck ↗As a progenitor of Extreme Programming (XP) and Test-Driven Development (TDD), he has championed iterative, test-first approaches to software design and quality.Software engineer and author

Glossary

• AlgorithmAn algorithm is a set of clear, step-by-step instructions or rules that a computer follows to solve a problem or complete a task. For example, the steps you follow to search for a friend's name in your phone's contact list (like sorting alphabetically) are an algorithm.
• BugA bug is an error or flaw in software that causes it to behave unexpectedly or incorrectly. For example, when a game suddenly freezes or crashes, it's often because of a bug in its code.
• CodeCode (or programming code) is the set of instructions written in a special language that computers understand, telling them exactly what tasks to perform. For example, when a developer writes "print('Hello World!')" in Python, that's a line of code.
• DebuggingDebugging is the process of finding and fixing errors (called bugs) in computer code to make sure the software works correctly. For example, when a programmer carefully checks their code line by line to figure out why a button isn't working, they are debugging.
• DeploymentDeployment is the process of making software available for users to access and use, often by installing it on servers or distributing it as an app. For example, when a new app update appears in your phone's app store, it means the developers have deployed that new version.
• SoftwareSoftware refers to the programs and data that tell a computer or device what to do, making it perform specific tasks. For example, the apps on your phone like WhatsApp or Instagram are types of software.
• TestingTesting is the process of checking software to make sure it works as expected, meets all requirements, and doesn't have any major errors. For example, before a new version of a video game is released, many people play it to find any bugs or problems, which is a form of testing.
• User Experience (UX)User Experience (UX) is how a person feels when using a software product, including how easy, efficient, and enjoyable it is to use. For example, if an app is confusing to navigate and crashes often, it has a poor user experience; if it's smooth and intuitive, it has a good one.
• User Interface (UI)The User Interface (UI) is the visual parts of a software application that you interact with, like buttons, menus, and text boxes. For example, the layout of buttons and the chat window you see when you open a messaging app is its user interface.
• Version ControlVersion control is a system that records changes to a file or set of files over time so that you can recall specific versions later. It's like having a "save history" for your code. For example, when a team of students works on a group project document, version control allows them to see who changed what and to go back to an earlier draft if needed.

Threads 7

Where this connects to other fields, and why it's worth knowing.

• Organizational Design & People Business

  Here's a spooky rule programmers learned, Conway's Law: whatever a piece of software looks like inside, it ends up mirroring how the teams that built it talked to each other. Three separate teams tend to build three clunky, separate parts. So sometimes you can't fix the code without first fixing who sits with whom on the org chart.

• Nuclear Weapons Risk Global Risks

  The scariest near-launches, like Soviet officer Stanislav Petrov in 1983, came from broken sensors and buggy software screaming 'incoming missiles' that weren't there. So nuclear danger is largely a bug-hunting, reliability problem. Every step toward letting code decide to launch makes the software itself, not the enemy, the thing most likely to kill us.

• Logic and Valid Reasoning Philosophy

  Proving a math theorem and writing a bug-free program turn out to be the very same act. A discovery called the Curry-Howard correspondence says a proof literally is a program, and the theorem it proves is that program's type. Logic and coding aren't cousins; they're the same thing wearing two outfits.

• Social Institutions Sociology

  The QWERTY keyboard was designed to slow typists down, yet we all still use it, because no single person can make everyone switch at once. The 9-to-5 workday and imperial units survive the same way, not by being good but by being stuck. Societies carry 'technical debt,' outdated code they can't easily rewrite, just like old software.

• Curriculum Design Education

  Planning a course so you learn addition before algebra is the exact same puzzle a computer solves when it figures out which code to build first: sort everything so nothing comes before the thing it depends on. So a course where students hit a wall isn't bad teaching, it's a broken dependency order, a loop where A needs B but B also needs A.

• Legal Systems Around the World Law

  One kind of legal system grows like code that everyone keeps patching, where every judge's ruling is a new commit stacked on centuries of old ones. The other kind is a clean rewrite from a single master rulebook. They're two rival philosophies for keeping a giant set of rules working without it ever crashing, exactly the debate programmers have about messy code versus a fresh start.

• Genetic Engineering & CRISPR Health

  When an app update breaks, coders just roll back to the old version. A 'gene drive' released into wild animals is like an update with no undo button. Once it starts copying itself through a whole forest of creatures, there's no going back.