Disillusionment was a crucible for my career. I went through it and wouldn't have it any other way. On the other side of it you attain focus on what is valuable to you, which is singularly useful for evaluating subsequent jobs. However, the crucible for me consisted of: depression, burnout, tendonitis. It sucked. From that, I decided I'd never do webdev again, including so-called backend. The web as a medium is not w…
I’ve recently come to a similar conclusion around “Focus” being something in short supply in most workplaces and no matter how often I point out its power (with examples), people push to solve 3-5 large scale problems concurrently. I’m not sure where I’ll find more focused environment but I’m sure I want little todo with the constant “hustle” mentality.
Surviving Disillusionment
91–100 of 179 posts
Re: Surviving Disillusionment
#92Disillusionment was a crucible for my career. I went through it and wouldn't have it any other way. On the other side of it you attain focus on what is valuable to you, which is singularly useful for evaluating subsequent jobs. However, the crucible for me consisted of: depression, burnout, tendonitis. It sucked. From that, I decided I'd never do webdev again, including so-called backend. The web as a medium is not w…
I'm not really well compensated for my work, but am somewhat paralyzed by the fact that I just don't know what to look for in a job anymore. I considered looking for a devops role in a company that prioritizes ownership of their systems (i.e. implementation of their own pipelines on their own metal rather than aws or similar), but it seems like the likelihood of finding a company like that which also values good infrastructure practices is pretty unlikely. I find that when I ask about whether finding such a role is realistic in chat rooms or forums about devops work the responses range from confused to derisive.
Did you find the crowd that resonated with your sentiments through contributions to open source? I've been thinking about looking into open source meetups in my area as a way of expanding my understanding of what I want to do.
Re: Surviving Disillusionment
#93Earlier quoted context omitted.
1) I have for a long time. Now with Kindles, I don't have to load 10 paperbacks into my computer bag every time I go on a global jaunt. A lot of time in airplanes and hotels gives you a lot of time for this (on average - which is why I said "per week", not "per day"). But, most under 250 page non-fiction books can be polished off in less than two hours. A lot of people spend two-hours/day watching some Netflix movie…
I've spent a long time trying to speed read and I'm still much slower than where I'd like to be. How are you able to read through 2 pages per minute and still have context on what's going on? Do you have any advice for learning to do that?
Re: Surviving Disillusionment
#94Earlier quoted context omitted.
"Touchy-feely" doesn't really explain to me what potion you hold that would be criticized. What is it you usually read? Why would your comments on the emotional content on a book ostracize you?
I guess it depends on workplace culture? I have worked and/or consulted at places where I would not have been (in general) afraid to be bold. Books like "Think" by Simon Blackburn don't bother me to comment on. They are pretty light treatments of the underlying topics, but (as philosophy), they are framed as rational discourses. (Whether they are or not is a different topic). Topics about things like emotional intell…
I think what this really means is that the more moderate you are, the more likely you are to feel stifled. Whether you're a liberal or conservative, the farther you are to one side the easier it is to know when and around who you can speak. Either you're in a stronghold for your respective group, or you wait until you're within the safe-haven of like-minded people in that area. As a moderate, you hold some views of both sides, and all you ever want to do if discussion comes up is explain how there are reasons why you hold these views that are you believe are rational, but to do so risks people categorizing you as "the other" from both sides. You learn to keep you mouth shut at all times, not just in one place or the other.
Re: Surviving Disillusionment
#95The reason I got into tech/coding as a teen was the diy punk rock ethos. I remember spending weeks trying to figuring out if I could break drm in the latest video game ('tricking' starforce in splinter cell 3 was such a cool thing). Then I moved on to academia where I felt the ethos extended. Academia was life consuming and by the end I just had to leave. Now that I'm job hunting post-phd, I'm trying to rekindle that…
Re: Surviving Disillusionment
#96His mention of Masters of Doom was interesting, because that book is really what got me into programming. The reality of corporate programming when compared to the freewheeling hang-out-with-your-friends-eating-pizza-listening-to-metal-inventing-cool-things programming described in the book has been a real bummer. Does that style of programming even exist any more?
Re: Surviving Disillusionment
#97Disillusionment was a crucible for my career. I went through it and wouldn't have it any other way. On the other side of it you attain focus on what is valuable to you, which is singularly useful for evaluating subsequent jobs. However, the crucible for me consisted of: depression, burnout, tendonitis. It sucked. From that, I decided I'd never do webdev again, including so-called backend. The web as a medium is not w…
I feel similarly but pretty much knew by the end of college that I wasn't interested in the typical web dev roles. I wound up in database development for my last couple jobs and now have ended up in charge of a lot of systems I built myself that interact with those databases and serve as the backend (and pseudo-frontend?) for all kinds of integrations for a small manufacturing company. I'm not really well compensated…
That's interesting. Conflicts of values like those can be deep and hard to reconcile. It becomes a sort of paper cut you can't quite get away from, because everyone's too invested in perpetuating the status quo.
I have to imagine there are companies that care about that, however. (There have to be those that aren't magnets for the hyper-competitive, too.)
> Did you find the crowd that resonated with your sentiments through contributions to open source?
A bit. I had a nice side quest through OSS, where I learned a lot about shipping, customers (e.g. users), and using it as a way to try out other domains/technologies. Ultimately, it was more something to help me pivot than a place to stay, mostly because I need to make money. But I am grateful for those that build those communities.
Re: Surviving Disillusionment
#98Disillusionment was a crucible for my career. I went through it and wouldn't have it any other way. On the other side of it you attain focus on what is valuable to you, which is singularly useful for evaluating subsequent jobs. However, the crucible for me consisted of: depression, burnout, tendonitis. It sucked. From that, I decided I'd never do webdev again, including so-called backend. The web as a medium is not w…
You got my curiosity! Can I ask you in which field are you working on?
Re: Surviving Disillusionment
#99His mention of Masters of Doom was interesting, because that book is really what got me into programming. The reality of corporate programming when compared to the freewheeling hang-out-with-your-friends-eating-pizza-listening-to-metal-inventing-cool-things programming described in the book has been a real bummer. Does that style of programming even exist any more?
Re: Surviving Disillusionment
#100I struggle with this and I am only two years into my career. I look back on my CS education and miss it so much. About three months ago, I started a ritual where I would spend 60 minutes before work every morning reading books about the internals of popular software or programming languages, histories of technology, etc. It rekindles my love for computing that brought me to CS in the first place. Instead of constantl…
It took me all of quitting, years of depression and accidentally restarting my career through a tech support gig to rediscover the massive joy I had solving problems with code.