Skip to content
Hallway
0:00 / 0:00

#softwarearchitecture#modulardesign#c

Architecting LARGE software projects.

Eskil Steenberg

37K subscribers • 6 videos on Hallway

YouTube
  • Recommended by 2 people: 2 in engineering communities.
  • Presented by Eskil Steenberg
  • An opinion. It argues one side of a question engineers disagree on.

Intermediate. Assumes working knowledge.

231K views1 year ago2 recommendations

Software designTools and practiceSoftware architectureDesign patternsSimplicity and complexity

Eskil Steenberg explains his approach to breaking down large software projects into manageable, independent modules for development teams.

This is a video where i will go over my general approach to architecting large software project and breaking them down in to manageable modules that can be built by individual developers. You can find my work on: quelsolaar.com Socials: @eskilsteenberg Regularly stream on: twitch.tv/quel_solaar Join our Discord at: discord.com/invite/Scg6trNUyW

Why it's here

2 people recommend this

What people say. Highly recommended as an insightful guide to modular software architecture from an experienced C developer.

u/grimvianin r/C_Programming • Recommends

Again a great video by the C guru, Eskil Steenberg: Architecting LARGE software projects. [video
37View on Reddit

u/Better_Pirate_7823in r/C_Programming • Recommends

Architecting LARGE software projects by Eskil Steenberg (2025)
11View on Reddit

u/Natehhgghin r/compsci • Mentions

On “what is the alternative to object-orientation?”

…c as separate as possible. and always prioritize what data is needed to solve the problem first. And there's a lot of emphasis on reusing datatype as much as possible, and how powerful typed unions, and fat structs can be. Mike Acton has a great talk at cpp con, that is a good primer on the subject, why it's important, and what it looks like. [video Anton Mikhailov had some a good demonstration of how you can take a simple api, and as you add in high level features, the complexity of the api starts to explode, and how that turns into adding more unavoidable error conditions. [video Eskil Steenberg on how to architect large systems without classes. [video Casey Murato…
1View on Reddit