That's certainly encouraging, thank you. I can certainly continue to learn new things through self-study and experimentation: it's been a relief to find that I'm so far undiminished in that regard. A disadvantage of my current job perhaps is that I am not having to much advance my skills; in principle they encourage it, but in practice not much makes sense beyond writing simple Python scripts (I hadn't used Python before, but between OOP and Perl 5 and Haskell I am finding it easy to use) and perhaps a chance to use React.js in due course. In my previous job I was working plenty on the whole technology stack from PL/SQL to Tomcat to jQuery and that was largely stuff with which I largely wasn't much familiar when I started. At home now I've got to grips with OpenBSD I'm trying to again make time to learn Erlang, I'm enjoying that.
I telecommute really well actually: I am more creative and productive (through being less distracted), they get some of my otherwise-commuting time as work time, and I'm happy to write up thoughts and share code and chat via IRC or H.323 or whatever to stay in touch, communicate where I'm going, and happy to frequently provide evidence of progress. I'd also be okay with spending the occasional week on-site if they cover reasonable expenses. In fact, my current de facto supervisor lives in Germany and I work plenty with a guy in Edinburgh so I'm kind of half-telecommuting from my desk in the office as it is, expensive headset at hand. While I lived in Cambridge, England, I moonlighted designing and implementing a sort of composable-components equation-solving simulator for engineered devices paid as a consultant for OSU's Center for Automotive Research. I've also done remote UNIX sysadmin just fine. However, I think I've only telecommuted for people I'd previously worked in person for; I'm not sure how hard it'd be to convince people who don't already know me to let me start off mostly telecommuting, though one'd think they'd be glad to save the overhead of providing office space and facilities.
![[personal profile]](https://www.dreamwidth.org/img/silk/identity/user.png)
timeasmymeasure
no subject
Date: 2016-02-04 09:01 pm (UTC)I telecommute really well actually: I am more creative and productive (through being less distracted), they get some of my otherwise-commuting time as work time, and I'm happy to write up thoughts and share code and chat via IRC or H.323 or whatever to stay in touch, communicate where I'm going, and happy to frequently provide evidence of progress. I'd also be okay with spending the occasional week on-site if they cover reasonable expenses. In fact, my current de facto supervisor lives in Germany and I work plenty with a guy in Edinburgh so I'm kind of half-telecommuting from my desk in the office as it is, expensive headset at hand. While I lived in Cambridge, England, I moonlighted designing and implementing a sort of composable-components equation-solving simulator for engineered devices paid as a consultant for OSU's Center for Automotive Research. I've also done remote UNIX sysadmin just fine. However, I think I've only telecommuted for people I'd previously worked in person for; I'm not sure how hard it'd be to convince people who don't already know me to let me start off mostly telecommuting, though one'd think they'd be glad to save the overhead of providing office space and facilities.