I went and did a masters degree in Ecology (well, Conservation Ecosystem Management specifically) during covid which I really enjoyed. A lot of it was completely out of my comfort zone after 20+ years in tech but a surprising amount did translate, such as the maths/stats and writing R code.
I felt it made me a better 'thinker' if that makes sense? Learned to be more critical (in a good way) and consider subjects I'd never come across before. I even went and created (and won!) a business pitch to a government org to handle some habitat surveys which was a great experience.
ah great, yet another reason to make me feel old today! :) But seriously, 30 years old game and it still holds up really well. OpenTTD is one of those that I always have installed
Well no, I clearly wasn't saying there is no ageism at all. I was taking issue with the comment regarding developers having to leave tech over 50 years old.
The idea that you must retire from tech before 50 is so incredibly false I have difficulty believing this view is even shared here.
Perhaps in some of the "trendy" "bro-culture" startups you'd have a more difficult time as an older developer but even in those places, the level of experience and skills older devs bring can be extremely valuable.
But say you were laid off in your 40's, now what? Well, there are so many bigger, less volatile companies out there with solid pay that are desperate for senior people with experience. There's also consulting for those who have spent a career building up a network of contacts. You can still leverage those old contacts for future opportunities as well.
Governmental work and such is also a place where age is not a concern. Here I agree you might not make as much money but employment is always available to developers who are skilled, experienced and flexible.
I took a break from software to complete a masters degree in ecology a little while ago and loved it. So much potential for software to improve that field. My research was based on using remote sensing to detect change in ecosystems, which proved to be very useful when monitoring raised peat bogs - vitally important ecosystems.
I'm back in the software world now but still spend time doing surveys and trying to think of ways I can combine both skillsets into a viable and impactful business.
+1 for Authy, though I keep the backups and multi-device turned on for convenience.
My old phone died and I had no way of getting into some of my 2FA secured accounts a while back and it was a wakeup call that eventually led to using Authy.
Absolutely! I made a comment in https://news.ycombinator.com/item?id=32668694 just recently about this. My company hired a guy who passed their tests, yet the guy who joined us for work was barely able to move a mouse around the screen, let alone get stuck in as a "Senior DevOps Engineer".
After we finally fired him I did a little digging. His resume was very similar to 100's of others found across linkedin, a list of devops keywords basically. Almost all of the people he had "worked" with in a previous company had the same text and even looked very similar.
I'm pretty sure that the company gets these people in the door and they try to last as long as possible earning western senior dev salaries. Rince and repeat a few times a year and it probably earns them a decent amount.
My employer hired a guy from this company! I wasn't involved in the interview process but was tasked with mentoring him. His resume was covered with DevOps buzzwords and he obviously said the right things in the interview, but the guy could barely move a mouse around the screen...
He took extremely long to do anything and then when he presented the work, it was very wrong and obviously copied from a bunch of stack overflow answers.
To this day I'm astounded my employer hired him and even more so that it took 2 months to fire him. Just think, he was on a senior salary for a couple of months for doing nothing... not a bad scam if you can do that a few times a year.
I recently moved from software dev to devops and this sounds about right! I'm supposed to understand the product teams entire codebase, write the tooling, create/update terraform for the infra, implement CI/CD stuff plus act as some kind of IT guy with AWS access.
Don't get me wrong, it makes a nice change from pure development, but it's clear that in most places, 'DevOps' is not so clearly defined.
In some countries they banned landlords from evicting tenants during the pandemic to stop stuff like this happening. They then asked banks to provide mortgage holidays so that the landlords could afford to keep non paying tenants. In my opinion this is a good example of government intervention for the greater good.
Is there any political will in the US to do the same? Could something like this ever be considered in congress or would it be seen as too 'socialist' maybe?
I'm currently working on a combined approach - deal with it + fix it via therapy/CBT/Mindfulness. Dealing with it by practicing gratitude for the benefits it provides and the goals it allows me to work towards. Current plan is to use this approach for 5-7 years working towards FIRE and then move into something more fulfilling with less pressure to secure a high salary.
We are lucky that tech pays so well that we could, in theory, retire early. It is very difficult to keep that in mind when you're miserable at work though...
Just wanted to let you know that I'm exactly the same way. In fact, I've even thought perhaps I was the one with the psychological defect where I simply can't stand the 9-5 grind, regardless of the pay, status or type of work. No amount of hobbies, travel or social efforts have made a dent in the deep, existential dread I feel after only a few days in a "normal" job.
Unfortunately, while I have had some successes working for myself, I tend to find down periods come along where I need to work again and I convince myself it will be different this time. It usually never is, the only difference being the length of time I can stomach being employed and even then it's a difference of a few weeks at most.
Is this actually a defect that needs some kind of therapy to correct? Or is it an acceptable way to be? Who knows but I thought I'd let you know that it's not just you.
Counting lines of code is definitely not a useful metric, however, you can extract a lot of information via the Github API that I believe can help with managing a tech team. It's exactly why I created getdevinsight.com as I think too many managers rely on bad metrics like lines of code and we can do better.
I wanted a way for dev team leaders to see at a glance, in plain english, how their team was doing so I created DevInsight. Feedback and thoughts very much appreciated!
I felt it made me a better 'thinker' if that makes sense? Learned to be more critical (in a good way) and consider subjects I'd never come across before. I even went and created (and won!) a business pitch to a government org to handle some habitat surveys which was a great experience.