https://ai-solutions.wiki/software-engineering/Recent content in Software-Engineerings on AI Solutions WikiHugoen-usTue, 31 Mar 2026 00:00:00 +0000https://ai-solutions.wiki/software-engineering/gitignore-patterns/Tue, 31 Mar 2026 00:00:00 +0000https://ai-solutions.wiki/software-engineering/gitignore-patterns/A .gitignore file tells Git which files and directories to exclude from version control. Without it, running git status in a typical project would show hundreds of generated, cached, and temporary files alongside your source code, and an undiscriminating git add . would commit files that have no place in a repository. Understanding how .gitignore works and what to exclude is one of the first practical skills for working with Git effectively.https://ai-solutions.wiki/software-engineering/version-control-fundamentals/Tue, 31 Mar 2026 00:00:00 +0000https://ai-solutions.wiki/software-engineering/version-control-fundamentals/Version control is the practice of tracking and managing changes to files over time. In software development, it means that every modification to source code is recorded with a timestamp, an author, and a description of intent. This record forms a complete, queryable history of a project: what changed, when, who changed it, and why. Version control is so foundational to modern software practice that the question is no longer whether to use it but which system to use and how to use it well.https://ai-solutions.wiki/software-engineering/extreme-programming/Thu, 26 Mar 2026 00:00:00 +0000https://ai-solutions.wiki/software-engineering/extreme-programming/Extreme Programming (XP) is a software development methodology created by Kent Beck and first described in his 1999 book Extreme Programming Explained: Embrace Change. XP emerged from Beck’s work on the Chrysler Comprehensive Compensation System (C3) project in the mid-1990s, where he began applying and refining practices that prioritized rapid feedback, simplicity, and direct collaboration between developers and customers. XP predates the Agile Manifesto by two years. When seventeen software practitioners gathered in Snowbird, Utah in February 2001 to produce that document, XP was already a functioning methodology with a published body of practice.https://ai-solutions.wiki/software-engineering/kanban-methodology/Thu, 26 Mar 2026 00:00:00 +0000https://ai-solutions.wiki/software-engineering/kanban-methodology/Kanban is a method for managing and improving knowledge work that David J. Anderson developed by adapting principles from the Toyota Production System (TPS) for software development teams. Anderson formalized this approach between 2004 and 2007 while working at Microsoft and Corbis, and published his synthesis in Kanban: Successful Evolutionary Change for Your Technology Business in 2010. The word “kanban” is Japanese for “signal card” or “visual card.” In Toyota’s manufacturing system, physical kanban cards authorized the production or movement of parts, preventing overproduction by making the entire production system visible and self-regulating.https://ai-solutions.wiki/software-engineering/agile-manifesto/Thu, 26 Mar 2026 00:00:00 +0000https://ai-solutions.wiki/software-engineering/agile-manifesto/In February 2001, seventeen software practitioners gathered at The Lodge at Snowbird ski resort in Utah to discuss lightweight alternatives to documentation-heavy software development processes. The result was the Agile Manifesto - a 68-word statement of values and an accompanying set of twelve principles that has since reshaped how the majority of commercial software teams organise their work. Historical Context: The Heavyweight Process Problem By the mid-1990s, software organisations had accumulated a substantial body of formal process methodology.https://ai-solutions.wiki/software-engineering/scrum-framework/Thu, 26 Mar 2026 00:00:00 +0000https://ai-solutions.wiki/software-engineering/scrum-framework/Scrum is a lightweight framework for developing and sustaining complex products. It was first formally described by Ken Schwaber and Jeff Sutherland in a 1995 paper presented at OOPSLA, and has been maintained since 2010 in the periodically updated Scrum Guide - the authoritative definition of the framework. The current version is the 2020 Scrum Guide, which removed prescriptive detail and reinforced Scrum’s identity as a framework rather than a full methodology.https://ai-solutions.wiki/software-engineering/waterfall-methodology/Thu, 26 Mar 2026 00:00:00 +0000https://ai-solutions.wiki/software-engineering/waterfall-methodology/Waterfall is the oldest formal software development lifecycle (SDLC) model still in active use. It organises a project into a fixed sequence of phases - each one completed before the next begins - producing a fully specified, fully documented system before any integration or delivery occurs. The model is frequently cited as the antithesis of Agile, but the historical record is more nuanced than that framing suggests. The Royce Paper and What It Actually Said The waterfall model is commonly attributed to Winston W.