Haha wow very similar. There's a guy here in a neighboring team that I used to work under that literally just falls asleep at his desk and snores. Comes in at 9:20, leaves at 3 some days.

Which general domain or area are you working in? Is this your first job?

I also have some imposter syndrome about being a "real" dev. I think that's because there's so many ways to go from here. Whereas, for example, if you were a doctor you would basically lock in your area of practice and then put your head down and get it done. For us, you could: build your own product, climb corporate ladder at BigCorp, startup world, freelance, freelance while traveling, consult, be a product manager instead, etc.

The cushy part is tough to give up, but the free hours don't really make up for the existential dilemma that eats at my soul every day... I know right, first world problems.

Actually, this is not the first job I've had where people pass out regularly. I sympathize with my bosses a little bit because big corps make it hard to get rid of people - I assume to avoid liability issues. But I do feel that it is the bosses job to keep them out of the way.

I've been on some pretty bad teams and management just tells the lead to task them and deal with it. I once was in a meeting with our manager and the whole team minus the sleeper in which he told all of us (the lead and all junior devs) that it is our responsibility to the team to motivate mr. sleepy. Aside from dead weight, he was also rude and not personable. But I would be too if I had to sleep through the day to get a paycheck.

It's not so much imposter syndrome as it is my unwillingless to let go of good money for a sane workplace. I'm fairly confident I could get a job in a reasonable work environment with legit devs, but i would have to cut my salary by 1/3 or 1/4. And getting paid less to do work - even if it makes me happy to feel productive doesn't seem like a wise choice, on paper at least.

One problem is that people understandably don't want to create a dev process for maintaining outdated applications on obsolete, unsupported hardware. That's simply be because a nice dev process is something that looks forward into the future. You do it because you believe you're developing some nice stuff that you believe will be going somewhere.

I see dev process less for sustainability of the code and more for the sake of sanity. I have been asked to rebuild tools that we only have the executable for and no source.

I think the problem lies more in that people are set in their ways and don't want to change. I'm not so hellbent on using hip new tools - like git or an issue tracker - but I push really hard to get people to communicate and interact. Unfortunately, everyone has carved out a niche and there's an understanding to stay out of each others' part of the project.