Feedback: I try to answer “how to become a systems engineer”

Re:Feedback: I try to answer “how to become a systems engineer” by travisgriggs on Wednesday May 31, 2023 @11:11AM (#36139262)

Amen to this. When I explain to full stack web devs that I do bare metal C, Python + Linux on edge nodes, server side processing, and native mobile apps they either say “you should AWS, we really like AWS” or “wow, so you’re like the real kind of full stack”.

Self deprecation and lauding aside, I’m curious what new titles others would propose? When I migrated into the field many moons ago, the two titles I saw mostly were “analysts” and “programmer”. The first had underpaid connotations, the second was rife with social awkwardness cues that Hollywood had run with for a while.

[ Parent | on HN ]

Re:Feedback: I try to answer “how to become a systems engineer” by toomuchtodo on Wednesday May 31, 2023 @11:19AM (#36139361)

I've used the term "Deep Generalist" before. Broad knowledge, deep capabilities. You know enough to know what you need to learn and execute on demand.

Historically known as or referred to as a "Renaissance Man" [1] or polymath [2].

[1] https://en.wikipedia.org/wiki/Renaissance_Man

[2] https://en.wikipedia.org/wiki/Polymath

[ Parent | on HN ]

Re:Feedback: I try to answer “how to become a systems engineer” by travisgriggs on Wednesday May 31, 2023 @12:37PM (#36140345)

Hmmm... Maybe I'll marinate in something like PolyWareIst for a while :D

[ Parent | on HN ]