A blog about modern PHP, the web, and programming in general. Follow my newsletter and YouTube channel as well.

Stitcher Engineering Blog offers insights, tutorials, and updates on building scalable, reliable, and high-performance systems for podcasting and audio streaming. Covering topics such as backend architecture, media processing, and content delivery, Stitcher Engineering Blog provides resources for developers and engineers working in the audio streaming industry. Developers can learn about building resilient systems, optimizing media workflows, and delivering high-quality audio experiences through Stitcher's blog posts and technical articles.

stitcher.io

The post discusses the concept of 'theoretical engineers' in software development, comparing them to theoretical physicists, but highlighting the rapid evolution in technology that often renders their conclusions outdated. The author emphasizes the importance of balancing theoretical knowledge with practical realities, acknowledging that real-world projects require pragmatism and adaptability due to the human elements involved.

Theoretical engineers

A theoretical engineer knows the architecture of the infrastructure implemented. The co-ordinating frameworks. The best person for this is a traditionally trained architect. In time you will have architects doing this. It is a very early stage at the moment.

That’s basically a System Administrator. But also this comment is very surface-y. Theory can be “this framework sucks because A, X, 9, + reason” or “we have to take a software that has minimal electrical use which will make sure we save money, deliver fast experience and accessible software while reducing complexity.”
Basically the difference between a Junior, a Senior.
This post sounds rather like some salty short comment. Author is literally commenting in a blogpost on a reddit comment that criticizes his other blogpost. Wild days.