this post was submitted on 13 Jul 2026
514 points (99.4% liked)
Greentext
8510 readers
501 users here now
This is a place to share greentexts and witness the confounding life of Anon. If you're new to the Greentext community, think of it as a sort of zoo with Anon as the main attraction.
Be warned:
- Anon is often crazy.
- Anon is often depressed.
- Anon frequently shares thoughts that are immature, offensive, or incomprehensible.
If you find yourself getting angry (or god forbid, agreeing) with something Anon has said, you might be doing it wrong.
founded 2 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
That's because an "IT engineer" is like an "engineer in chemistry". You have so many sub-disciplines that a given engineer can't be expected to know everything. Nobody is surprised if an organic chemist doesn't know much about heat exchanger optimisation, or a chemical process engineer is confused by organic synthesis.
In the same way, I've met devops guys that know surprisingly (to me) little about the intricacies of hand writing multi-threaded high performance calculation code. In the other hand, they're wizards at stuff like load balancing and optimising how we use sub-processes for I/O, CPU-bound or memory bound tasks. You would think the two are very similar, but even then it quickly becomes clear that people really become specialists in their field.