svavs

Boatmurdered is one of the greatest LP ever - a stunning tale

I haven't used Android as a daily phone since the EVO (I know, its been a while). One issue I had with Android and custom firmware was the time involved. Being on a computer all day, and often times at night, having to deal with tech support issues on my device is a hard stop (for me, personally, plenty of people love it).

That's the nice part of Apple's ecosystem - its pretty simple and requires minimum intervention.

The reason I wanted to be clear about that is I have heard stories about people quitting on the spot.

I believe the delay in my company releasing their plan for return to office has a lot to do with IT. We are having issues with finding enough folks as is. I couldn't imagine what it would be like if 30% put their notice in.

This is something that has come up within our company (we are still waiting on official guidance). I love WFH, for all the reasons you've read in other posts.

If we have to return, I won't quit. That's reckless, imho. But my resume will be updated and I will be open to remote positions. Many of my colleagues feel the same way.

Completely agree! My company has pretty strict rules for creating infrastructure in our upper environments. Devs are not able to do it and we want everything to run through our CI/CD pipeline. We either have to ask our cloud team to create the bucket or hack up our build file to add it.

It would be nice, on the first run of terraform init, if it would check for the remote state bucket and then ask if you would like to create it if it does not exist.

The grain industry. Specifically grain elevators.

There are a few mid-sized companies that control a large chunk of that industry. Since they don't have much competition, innovation is more or less at a stand still. Companies like bushel ag are changing that, but lots of opportunity.

Nope. We are judged by our individual performance by how many points (tasks) we complete. Since this has been a metric, unit testing is always an afterthought. During code checks / reviews, some developers will ask others to add unit tests, which will be hastily written.

I wish I could say I figured this out, but I haven't. While not exactly your same situation, most of those points hit home for me.

I think it's really good that you are realizing this now in your career, rather than toughing it out for a decade or more (like me).

Have you considered maybe software engineering isn't the right career for you? Perhaps you would find more meaning in another profession.

> Nobody is doing anything they don't want to do. Nobody is forced to build open source software.

Many job postings list OSS contributions as a requirement / desirable for employment. So, I'm not sure if your statement holds up.

I personally know developers that contribute to OSS because of this. And many that have burnt out because of the constant need to contribute.

Most OSS contributors do it for fun - but there is a section that do it because it's becoming part of the interview / job hunting process.

For the people that are hiring / have hired people from these posts, what do you look for? What makes a post stand out?