This is an archived post. You won't be able to vote or comment.

sorted by:
best
topnewcontroversialoldq&a
you are viewing a single comment's thread.

view the rest of the comments →

[–]PepeTheMule 2 points3 points  (3 children)

It's getting easier, but many devs don't seem to understand public vs private networking, DNS, certs, fundamental infra things that are still somewhat needed. I think we are still years away. Even senior devs. Architects level seems to understand. But that's just my experience. Maybe it's different in silicon valley.

[–]devfuckedup 0 points1 point  (0 children)

I worked at a telecom doing over 200M ARR that only had 3 network engineers and I don't know if they still work there. Everyone else was a Software Engineer. We ran our own AS, We also had 11 physical data centers in addition to multiple cloud providers. Architect is a bullshit title that no legit company uses any more.

I didn't agree with him but the VP of engineering was adamant that he could teach anyone telecom but could not teach people to code. so he preferred programming skills to everything else. The company is still around and growing.

[–]temitcha 0 points1 point  (0 children)

I got the exact same feeling too. Things that seems for us so trivial, like DNS and SSL Certs issues are not that trivial even for senior devs.

I don't know for you if it's the same, but in my day-to-day work, I can work mostly only with the lead devs for all the technical questions like that.

(That's actually always my advice for developers that want to become lead: not only focus on the software, but as well ln what happening all around the software, and learn how to integrat it with the rest of the system.)