Re:Computer Sciences Courses That Don't Exist, but Should
by Drdrdrq on Friday September 11, 2015 @12:19AM
(#10202002)
I understand your frustration, but the field has become too big for a single (average) person. When problems arise , you team up with someone who knows more about the issue or you learn on the spot. Nothing wrong with not knowing everything.
[ Parent
| on HN ]
Re:Computer Sciences Courses That Don't Exist, but Should
by toomuchtodo on Friday September 11, 2015 @12:51AM
(#10202071)
That's not my problem. My problem is the illusion presented that you don't need to understand the underlying infrastructure. Far too often I see infrastructure as an afterthought, secondary to the code.
Re:Computer Sciences Courses That Don't Exist, but Should
by voltagex_ on Friday September 11, 2015 @10:54AM
(#10203988)
What kind of organisations have you worked in? I've been lucky (?) to work in an organisation with a dedicated network/infrastructure team. My work life got a lot better when I gained more understanding of how the network was put together (vis-a-vis load balancers, DNS, data center locations etc).
I still don't have a "low level" understanding of the network I use.
Re:Computer Sciences Courses That Don't Exist, but Should
by toomuchtodo on Friday September 11, 2015 @11:09AM
(#10204085)
I've always managed or been on infrastructure teams at other orgs; my latest gig is at a startup, and I'm the only infrastructure guy. Perhaps that is the problem.
Re:Computer Sciences Courses That Don't Exist, but Should
by voltagex_ on Friday September 11, 2015 @11:13AM
(#10204107)
Good chance to educate others? I know I'll be looking for an opportunity to work with an infrastructure guru at some stage in the future.
Re:Computer Sciences Courses That Don't Exist, but Should
by toomuchtodo on Friday September 11, 2015 @11:14AM
(#10204112)
I'm going to embrace it as such! Thanks!
Re:Computer Sciences Courses That Don't Exist, but Should
by skarap on Friday September 11, 2015 @10:36AM
(#10203878)
More likely when problems arise you "team up" with someone who knows [almost] everything.
And I agree with other posters that this isn't something new. That's the separation between senior and junior specialists (and no - if one doesn't know what network latency is, that one is not a senior frontend engineer).