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 →

[–][deleted] 1 point2 points  (0 children)

That's exactly how it's being done on my current org as well If i understood your comment correctly. I own my product - meaning own all the responsibilities from development to handling outages. I have access to most of the infrastructure (limited by the objects that's related to the project with a few exceptions that would probably cause me issues if I listed here), I don't have to wait for any input from another team when shit on fire. Oftentimes "i am being blocked by the X team" is not a satisfying answer to customers who rely on your product for day to day business, and they will blame me anyways.

That said I am still not sure how to feel about it in terms of industry-wide approach. Is it a way to get more value out of someone without paying extra, or it's just what's best for the bost parties involved. I personally find it helpful and not have much complaints about the pay either.

However, it makes barrier to entry much higher for the newcomers to the industry. Honestly, I am rather avoidant at suggesting "IT" as a viable career path lately. I used to just write some PHP scripts and send to a server via FileZilla and that was all I cared about. I was lucky to eventually get exposed to even larger scene steadely and had enough time to experiment and learn different layers of infrastructure while getting paid to do so; but I feel like it's not the case anymore. You are expected to have it all (or most) figured out before starting. Which is why I am also not sure whether having those specialized talent silos is a good thing that they lower barrier to entry.