4 ms·

This is a bit wishy washy but generally scans true. For a newbie 2 and 6 are what I'd consider the main points. 2. You will not get as much help as you need -

This is a bit wishy washy but generally scans true. For a newbie 2 and 6 are what I'd consider the main points. 2. You will not get as much help as you need - Because you're the new kid and they are dropping you on a legacy configuration job. Welcome to support baby. This ain't FAANG. You're not getting help because no body knows how to deal with what you looking after. 6. You won't understand everything you're doing And truthfully neither will your peers. Someone will understand saml, they will do the saml and you'll try not to mess it up. Someone will understand the pipeline well, and you'll try not to mess it u. Some will understand the container system etc. My own hard truth: 8. If you write doco it will be something you can show you boss that will set you apart. Writing is hard. Expressing technical ideas in writing is very hard.

qayxc 7y ago
> Writing is hard. Expressing technical ideas in writing is very hard. That. I'm always baffled by the amount of positive feedback a well written document or well-structured presentation can get you as opposed to weeks of hard work and craftsmanship that no non-technical person is ever going to notice.
- finnthehuman 7y ago
  The work that will impress the most is usually found at the boundaries between skillsets, not in the nitty-gritty of one feild. It's the bikeshed problem in reverse. Nobody can understand your reactor design well enough to be impressed by the impressive things you did. They can have their socks knocked off by your bikeshed though. Even if your reactor design would get positive feedback from fellow reactor designers and your bikeshed is a laughing stock among bikeshed builders. Not to say that technical writing is frivolous or lower skilled as bike sheds are to reactor design, this is just the go-to story about approachability.

qayxc 7y ago

> Writing is hard. Expressing technical ideas in writing is very hard. That. I'm always baffled by the amount of positive feedback a well written document or well-structured presentation can get you as opposed to weeks of hard work and craftsmanship that no non-technical person is ever going to notice.

finnthehuman 7y ago
The work that will impress the most is usually found at the boundaries between skillsets, not in the nitty-gritty of one feild. It's the bikeshed problem in reverse. Nobody can understand your reactor design well enough to be impressed by the impressive things you did. They can have their socks knocked off by your bikeshed though. Even if your reactor design would get positive feedback from fellow reactor designers and your bikeshed is a laughing stock among bikeshed builders. Not to say that technical writing is frivolous or lower skilled as bike sheds are to reactor design, this is just the go-to story about approachability.