top | item 43338549

(no title)

betimsl | 11 months ago

> Why?

Huge interest in the field. Schools unable to teach the craft properly.

discuss

order

xraider42|11 months ago

I kinda concur and i think there is also a business needs mismatch. OP's approach requires a very holistic and integrated view on things, a lot of experience and academic knowledge. It would probably be a better approach, but it requires upping the requirements who can be a SE and how its taught, software might not be a commodity in this world.

The beauty of today's "cloud native" approach is that everything is basically just a layer on top of another layer and you can be completely ignorant of everything below and make stuff that even if inefficient, works. We can churn out a lot of people and yes, they will make crap, but crap that satisfies the needs of the business and creates real or perceived value for it. Arguments can be made that long-term its a loss since the codebase will rot faster, but everybody responsible will be long gone and don't care, they don't have incentives for this.

A week ago I interviewed a guy who delivered multiple projects over his 10 year career in large companies and he had no idea what's multithreading or concurrency. The academic in me weeps, but the manager/engineer in me was impressed that you can be so completely ignorant of all lower layers, but still produce said value. Would it be possible in the noted holistic approach ?