Re^3: Not enough [hours|perl] in the day

Hah, thanks! I finally threw in the "sys admin" towel and made the switch. It only took getting laid off from another company to push me into the new path, and I'm glad it happened.

I've been going back through the 'Nodes I wrote' to see if 1) there's been progress on any of those subjects, 2) if I can learn anything else from them, and 3) too see how much (if any) I've grown since then. I find it educational and sometimes embarrassing at the same time. :)

Comment on Re^3: Not enough [hours\|perl] in the day

Replies are listed 'Best First'.
Re^4: Not enough [hours\|perl] in the day by stevieb (Canon) on Mar 22, 2017 at 20:26 UTC
I did the same with the sysadmin/neteng towel. I'm glad you're doing something you like. That's huge for me personally, and I'm sure anyone else who doesn't go to work in the morning thinking "I fskcing hate my job". I too go back through my posts here periodically. Sometimes I cringe, other times I think "wow, I just ran into this last week and wrote four lines of code where five years ago, I knew a way to use only one" :) I find reflection to be important overall for moving forward. Did you find anything that you couldn't find an answer for yet?	[reply]
Re^5: Not enough [hours\|perl] in the day by sierpinski (Chaplain) on Mar 22, 2017 at 20:34 UTC
Not yet, but I've only started going through my nodes. Glad to hear you made the switch as well. I learned a lot in operations, but I've been wanting to write more code for a long time now.	[reply]
Re^6: Not enough [hours\|perl] in the day by stevieb (Canon) on Mar 22, 2017 at 20:56 UTC
To be honest, I didn't know where I was going to head. I left my last job and took seven months off where all I did was camp out in the Rocky Mountains for weeks at a time. I then found an interesting position as a solution architect in and about the same area I lived in that I applied for and received. That included a lot of custom per-client Python coding. Some of the politics I don't agree with, but it's a bit more of a flat structure where I have direct access to people like the CTO where I can discuss stuff with. I also get to make my own design decisions without 18 layers of red tape hindering me. Someday I'll code Perl professionally. For now, I am very happy doing what I do, with the ability to interact with Perl sites during breaks in my day, and writing a boatload of open source code for the CPAN. I'm still in frequent communication with people from my past jobs so I'm up to speed on things such as core Internet routing etc, but stepping back and being able to blame engineers and IT departments has become something I like :) (Of course, I do this mostly politely and with respect, as I know what it's like to work there.)	[reply]