Ask Lemmy
A Fediverse community for open-ended, thought provoking questions
Please don't post about US Politics. If you need to do this, try [email protected]
Rules: (interactive)
1) Be nice and; have fun
Doxxing, trolling, sealioning, racism, and toxicity are not welcomed in AskLemmy. Remember what your mother said: if you can't say something nice, don't say anything at all. In addition, the site-wide Lemmy.world terms of service also apply here. Please familiarize yourself with them
2) All posts must end with a '?'
This is sort of like Jeopardy. Please phrase all post titles in the form of a proper question ending with ?
3) No spam
Please do not flood the community with nonsense. Actual suspected spammers will be banned on site. No astroturfing.
4) NSFW is okay, within reason
Just remember to tag posts with either a content warning or a [NSFW] tag. Overtly sexual posts are not allowed, please direct them to either [email protected] or [email protected].
NSFW comments should be restricted to posts tagged [NSFW].
5) This is not a support community.
It is not a place for 'how do I?', type questions.
If you have any questions regarding the site itself or would like to report a community, please direct them to Lemmy.world Support or email [email protected]. For other questions check our partnered communities list, or use the search function.
Reminder: The terms of service apply here too.
Partnered Communities:
Logo design credit goes to: tubbadu
view the rest of the comments
This is 100% it. Worked in IT 15+ years, started with building desktops, servers, virtual machines, building networks, troubleshooting in-depth kernel issues, tracing TCP/IP chatter, which built a really broad platform for my current job as principal cloud architect. I and peers of my vintage understand how to troubleshoot down to a low level, and we understand the implications, benefits risks and constraints of putting certain cloud technologies together even through the multiple levels of abstraction.
We've had the benefit of experiencing these technologies grow and develop first hand, we understand how they fit together and where to look when something isn't working. Recent graduates have not had the benefit of that journey, are so used to operating at the top layer of the abstraction that works most of the time, that I find they really struggle to decompose a problem, simplify and troubleshoot one logical component step at a time. Problem solving is a learned skill and multiple layers of abstraction make knowing where to start very difficult if the error message isn't crystal clear.