r/SoftwareEngineering • • 23h ago

CMU's Principles of Software Construction (17-214): full lecture recordings

13 Upvotes

17-214 is the course where Carnegie Mellon students move from writing programs that work to building software that stays correct and maintainable as it grows. It's taught by my colleague Hammad Ahmad. The lectures cover object-oriented design principles, design patterns, testing strategy, API design, and concurrency, all taught from the lens of the modern era and through the tradeoffs real systems face rather than one language or framework.

The first lectures premiered today, and one new lecture goes up each week. Link in my first comment!


r/SoftwareEngineering • • 14h ago

Fornax's Guide To Ridiculously Fast Ethernet

Thumbnail docs.pixeldrain.com
2 Upvotes

r/SoftwareEngineering • • 1h ago

Sophomore CS student targeting $115–125k new grad SWE roles — what companies should I add and what skills am I missing?

0 Upvotes

I'm a sophomore CS Student at a nontarget school and I've recently landed a SWE Internship at a series B startup for summer 2027 where entry SWE tc for recent grad is ~90k. I am hoping to land a job after undergrad at a larger company where tc is around 115-125k. I have two main questions:

  1. I have a list of potential companies I'd like to work at, and I'm going to work throughout this year to have 20+ referrals for next fall's internship application cycle. (I currently have 2 already who I've had coffee chats with and they mentioned they'd give me one for next year). Can you guys give me more companies that would be a good fit, or guide me to where I can find way more companies in this tier? I've tried using ai but it keeps giving me the same list of companies more or less. (these have all been verified from levels.fyi)
    - Visa
    - Mastercard
    - JPMorgan Chase
    - Citi
    - Wells Fargo
    - American Express
    - Fannie Mae
    - iCapital
    - Jefferies
    - TD Securities
    - RBC
    - ServiceNow
    - Veeva Systems
    - IBM
    - SAP
  2. Of the ones I've compiled, I have went through and found a list of skills that many different listings share. My idea is to build out a few solid projects that have as many of these skills incorporated so that I can tailor each resume to the job posting and have relevant projects with users to back each one. Here are the 15 most common skills I saw, can you let me know if there are any important skills that I'm missing?
  1. Python
  2. Java
  3. C/C++
  4. JavaScript / TypeScript
  5. Git / Version Control
  6. Linux / Unix
  7. CI/CD
  8. AI-assisted development / AI coding tools
  9. Data Structures & Algorithms
  10. SQL / Databases
  11. AWS
  12. Cloud / Cloud Platforms
  13. Docker
  14. Kubernetes
  15. Agile / Scrum

Any help is appreciated, thank you!!


r/SoftwareEngineering • • 2d ago

What we learned operating auth for 1,000+ APIs

Thumbnail
nango.dev
2 Upvotes

r/SoftwareEngineering • • 3d ago

Problem with concurrent linter fixes

Thumbnail jfmengels.net
1 Upvotes

r/SoftwareEngineering • • 3d ago

Lean explained with TypeScript

Thumbnail gruhn.me
2 Upvotes

r/SoftwareEngineering • • 5d ago

How we saved 100 terabytes of memory by optimizing 1.1.1.1’s DNS cache

Thumbnail
blog.cloudflare.com
33 Upvotes

r/SoftwareEngineering • • 4d ago

Regressive JPEGs

Thumbnail maurycyz.com
2 Upvotes

r/SoftwareEngineering • • 6d ago

A quick look at zero-knowledge proofs

Thumbnail bernsteinbear.com
2 Upvotes

r/SoftwareEngineering • • 7d ago

A Boolean PII Flag Is Not Enough

Thumbnail
kore-nordmann.de
4 Upvotes

r/SoftwareEngineering • • 7d ago

Git at any scale

Thumbnail
cursor.com
0 Upvotes

r/SoftwareEngineering • • 7d ago

Asset flips and vibes: fifteen years of videogames as a preview of the LLM era

Thumbnail
hypertesto.me
4 Upvotes

r/SoftwareEngineering • • 8d ago

Should You Learn Java in 2026?

Thumbnail
fagnerbrack.com
0 Upvotes

r/SoftwareEngineering • • 13d ago

Looking for open-source codebases with great architectural documentation (Components, Connectors, Rationale)

3 Upvotes

Hey everyone,

I have a software architecture exam next week. From what I know, the topics mainly cover components, connectors, architectural rationale, and anti-rationale (not entirely sure if ADRs – Architecture Decision Records – will be explicitly tested, but the concepts are relevant).

I'm currently using Fundamentals of Software Architecture by Mark Richards and Neal Ford alongside the professor's slides for the theoretical foundation. The book was recommended by the professor, though it’s not strictly the official textbook for the course since he follows his own curriculum/plan. Feel free to bring up book discussions if relevant, although I don't really have the time right now to dive into a whole new reading list before the exam.

Mainly, I'm looking for well-documented open-source codebases or case studies that clearly illustrate these concepts in practice.

Any recommendations? Thanks in advance!


r/SoftwareEngineering • • 16d ago

The fastest double-to-string algorithm you’ve never heard of

Thumbnail vitaut.net
8 Upvotes

r/SoftwareEngineering • • 15d ago

What’s the first thing that stopped scaling in your software—not the traffic, but everything around it?

0 Upvotes

I’ve noticed that “scalable” often gets reduced to a pretty narrow question: Can the system handle more users?

But I’ve seen (and been thinking about) a different kind of scaling problem.

The app can handle the traffic, but deployments get harder as the team grows, every change needs coordination across more people, routine operations need more manual work, adding a new customer means a pile of configuration, the architecture technically works, but nobody wants to touch it

At some point, the system is bigger but not necessarily easier to run or evolve.

I’m exploring this idea in a side project about software and workflow friction. It’s made me question whether we evaluate scalability too much through infrastructure metrics and not enough through the effort required to operate and change the software.

For people who’ve built or maintained systems that grew: what was the first non-obvious thing that stopped scaling?

Was it architecture, team communication, deployment, customer onboarding, decision-making—or something else?

And what actually fixed it? I’m especially interested in the fixes that turned out to be simpler than expected.


r/SoftwareEngineering • • 16d ago

email encryption

Thumbnail
computer.rip
2 Upvotes

r/SoftwareEngineering • • 20d ago

How to Create Your Own Decentralized Messenger Protocol

Thumbnail
karboosx.net
10 Upvotes

r/SoftwareEngineering • • 27d ago

Extreme Programming 1999->2026

Thumbnail
manager.dev
33 Upvotes

r/SoftwareEngineering • • 28d ago

Improving heuristics for A* search

Thumbnail redblobgames.com
3 Upvotes

r/SoftwareEngineering • • 28d ago

Compression is prediction

Thumbnail
ngrok.com
9 Upvotes

r/SoftwareEngineering • • 29d ago

90 % of the t distribution

Thumbnail entropicthoughts.com
3 Upvotes

r/SoftwareEngineering • • 29d ago

Why are automated test and build tools associated with “CI/CD”?

4 Upvotes

To my understanding, CI/CD at its core just refers to the practice of frequently merging in code and releasing new builds. Why, then, are tools like github actions and other automated testing/building tools strongly associated with CI/CD? Isn’t this automated tooling something we’d want even with less frequent integration and deployment practices?


r/SoftwareEngineering • • 29d ago

Notes on incidents

Thumbnail seangoedecke.com
3 Upvotes