4 ms·
> Engineers make dozens of architectural decisions every day. > Two really key fundamental knowledge areas if you're goal is to build actually reliable and rel
by pbiggar 10y ago
> Engineers make dozens of architectural decisions every day.
> Two really key fundamental knowledge areas if you're goal is to build actually reliable and relatively efficient software.
I would challenge you on this, and suspect that you're looking at a relatively thin slice of developers: can you clarify why you believe this to be the case. As a counter-example, a lot of modern web development is building frontends (mobile or JS), where good code organization matters, but systems architecture doesn't matter so much.
- DougWebb 10y agoI've been building web-based frontends for my entire professional career, and my systems architecture skills have been invaluable throughout. Web frontends don't stand alone; they run on server, they make use of networks and networking hardware, they talk to other services on the same server and other server, and they interact with the operating system. Being able to understand all of those moving parts is crucial to producing a high-quality frontend that's not going to fall apart as soon as it gets put under stress, and that will be maintainable and extensible over time.
- pbiggar 10y agoCan you clarify why CS skills are necessary, vs the ones you learn in bootcamps (which I would guess are much more specific to this use case)? I agree they do all these things, but in a way that can be taught quickly and is mostly learned through experience, no?