Topic
Software Engineering
Learn Software Engineering as a connected topic across chapters, concepts, simulations, and interview reasoning.
10 Concepts13 Articles3h 34m
Overview
Learn Software Engineering as a connected topic across chapters, concepts, simulations, and interview reasoning.
How this topic helps
Java
Architecture
Clean Code
Solid Principles
Learning Path in this Topic
Series that contain articles from Software Engineering. Select a path to filter the article list.
Articles
13 matched articles
Article 1Java 21 to 25: Virtual Threads, Pattern Matching, and Structured ConcurrencyTLDR: Java 21 LTS makes virtual threads a production-ready replacement for bounded thread pools — your newFixedThreadPool(200) can become newVirtualThreadPerTaskExecutor() and handle 10× the concurren22 minArticle 2Java 14 to 17: Records, Sealed Classes, Text Blocks, and Pattern MatchingTLDR: Java 14–17 ran a deliberate four-release preview-to-stable conveyor belt. Records replaced 50-line POJOs with one line. Text blocks ended escape-sequence chaos in multi-line strings. Sealed clas25 minArticle 3Java 8 to 11: Lambdas, Streams, Modules, and the End of BoilerplateTLDR: Java 8 introduced the most impactful set of language features in Java's history — lambdas eliminated anonymous inner classes, streams replaced imperative loops, and Optional made null handling e16 min
Article 4Java 8 to Java 25: How Java Evolved from Boilerplate to a Modern LanguageTLDR: Java went from the most verbose mainstream language to one of the most expressive. Lambdas killed anonymous inner classes. Records killed POJOs. Virtual threads killed thread pools for I/O work.25 minArticle 5Understanding KISS, YAGNI, and DRY: Key Software Development PrinciplesTLDR
TLDR: KISS (Keep It Simple), YAGNI (You Aren't Gonna Need It), and DRY (Don't Repeat Yourself) are the three most universally applicable software engineering mantras. They share a common enemy: 15 minArticle 6Simplifying Code with the Single Responsibility PrincipleTLDR
TLDR: The Single Responsibility Principle says a class should have only one reason to change. If a change in DB schema AND a change in email format both require you to edit the same class, that 11 minPage 1 of 3