https://datatweets.com/courses/software-engineering/engineering-foundations/Recent content in Engineering Foundations on DATATWEETSHugoenCopyright (c) 2025 DatatweetsSun, 05 Jul 2026 09:00:00 +0200https://datatweets.com/courses/software-engineering/engineering-foundations/lesson-1-core-principles-of-software-engineering/Sun, 05 Jul 2026 09:00:00 +0200https://datatweets.com/courses/software-engineering/engineering-foundations/lesson-1-core-principles-of-software-engineering/This lesson breaks down the six ideas that separate maintainable code from a tangled mess: modularity, abstraction, encapsulation, reusability (DRY), simplicity (KISS), and restraint (YAGNI). Every example comes from Ledgerly, a small invoicing and subscription-billing app, showing a ‘before’ version that violates the principle and an ‘after’ version that fixes it. By the end, you can recognize each principle in real code and explain why it matters.https://datatweets.com/courses/software-engineering/engineering-foundations/lesson-2-the-solid-principles/Sun, 05 Jul 2026 09:00:00 +0200https://datatweets.com/courses/software-engineering/engineering-foundations/lesson-2-the-solid-principles/SOLID is five rules for object-oriented design: Single Responsibility, Open/Closed, Liskov Substitution, Interface Segregation, and Dependency Inversion. Using Ledgerly’s Invoice, PaymentGateway, and Subscription classes, this lesson shows a real violation of each principle next to its fix, with output from actually running the code. You will finish able to spot a SOLID violation in a code review and explain how to correct it.https://datatweets.com/courses/software-engineering/engineering-foundations/lesson-3-the-software-development-lifecycle/Sun, 05 Jul 2026 09:00:00 +0200https://datatweets.com/courses/software-engineering/engineering-foundations/lesson-3-the-software-development-lifecycle/This lesson walks the Ledgerly team through the six phases of the software development lifecycle: requirements analysis, design, implementation, testing, deployment, and maintenance. Each phase is grounded in one real feature — automatically emailing customers about overdue invoices — with runnable Python showing what implementation and testing actually produce. You will also see why the SDLC is a repeating cycle rather than a one-time checklist.https://datatweets.com/courses/software-engineering/engineering-foundations/lesson-4-development-methodologies/Sun, 05 Jul 2026 09:00:00 +0200https://datatweets.com/courses/software-engineering/engineering-foundations/lesson-4-development-methodologies/A development methodology is the set of rules a team uses to plan, build, and release software. This lesson follows the three-person Ledgerly team as they pick two-week Scrum sprints for building invoicing features, run a Kanban board with work-in-progress limits for support tickets, and consider a stricter Waterfall-style process for a compliance feature. You compare Scrum’s roles and ceremonies, Kanban’s pull-based flow, and a decision guide for choosing, or blending, methodologies based on team size, requirement stability, and regulatory pressure.https://datatweets.com/courses/software-engineering/engineering-foundations/lesson-5-guided-project-planning-ledgerly/Sun, 05 Jul 2026 09:00:00 +0200https://datatweets.com/courses/software-engineering/engineering-foundations/lesson-5-guided-project-planning-ledgerly/In this guided project you join the Ledgerly team as a new engineer and take one real feature from idea to code: a 7-day overdue escalation notice. You write user stories and acceptance criteria, choose and justify Scrum for the work, map the feature onto all six SDLC phases, and build a SOLID-respecting OverdueInvoiceNotifier that depends on NotificationService and InvoiceRepository abstractions instead of concrete classes. A real Python test then proves that dependency inversion is what makes the feature easy to verify without sending a real email.