,
4 tweets,
2 min read
Read on Twitter
@ScribblingOn I *think* what helped me (in hindsight) had to do with three things: good systems theoretical knowledge (I spent, and still do, a good portion of my spare time reading about OS internals and how things worked together (Linux, bsds, etc)), maintain a full stack myself 1/
@ScribblingOn (easier today than in late nineties and early noughties - things like my own DNS, mail servers, lamp stack etc), and probably the most important, offering myself to do all the "sysadmin" work. If where I worked there was a need for a new system, ask the admin to guide me 2/
@ScribblingOn through the changes while asking "why is that important?" or "how did you decide that?" or "how did you arrive at that conclusion?". This probably meant I worked 12h days often (AND I DO NOT ADVOCATE THAT) but I learned a lot. I also collected a lot of hardware to experiment 3/
@ScribblingOn which helped understand different devices and temperaments. Then one day I just applied for what at the time was a sysadmin position and got it. And here's the last, also important, bit: through it all I got lucky with the mentors, my managers, and my teams. Fin
