In the darkest of days, I discovered how to remote login to my computer at work through the company vpn. I then proceeded to work overtime at night in secret for a week or so, writing documentation and refactoring code.

I finally woke the fuck up and realized that I shouldn't be obsessing over proprietary codebases that do not belong to me, and I should put this misguided energy into my own projects.

So yeah, as a bad dev habit I'm working on fixing, this fits the bill.

Last year the rewrite of an ancient system (VB6/mainframe COBOL) was started. Instead of moving to modern architecture management decided to rewrite the app's functionality into our last gen WinForms client/server arch. I set up a meeting to present alternatives and plead for some level of modernization. After presenting and asking management to plan for five to ten years in the future instead of just this year's budget my director said, "In five to ten years I'll be retired on a beach in Tahiti and this will be your problem to solve." It was the last straw and I left the company shortly after. Last week I found out the director was force retired out of the company. I sent her a congratulations slip and a cocktail umbrella with "Tahiti" written on it.

My tech lead keeps assigning me incident tickets in the company's worst legacy app because I solved some bug in it a while ago. I'm the only one who gets assigned these.

If this keeps going, I know for sure that I will be regarded as the designated developer for this application. Then I will be truly fucked.

Management has been promising we'd leave .NET framework for 2 years now. Never fucking happens. A new ASP.NET project was just started last week and yup, OF COURSE, its .NET Framework 4.8.

I'd even be happy with one of the earlier .NET Core versions at this point for fucks sake. I have no clue why tech leads are so happy to create a brand new project on a deprecated framework version.

And yes, I have checked thoroughly. Our whole infrastructure works with .NET Core onward. People are just too lazy to learn new stuff.

Stuff like switching to .NET 6, actually doing unit testing, improving our CI/CD pipeline, refactoring problematic codebases, etc. -> all this stuff is the kind of things they promise me I can work on later whenever I'm so bogged down with work that I'm looking for a light at the end of the tunnel. All empty promises.

Ideally we should be on .NET 6 since its LTS and just stay on the LTS versions as the year goes on.

I'm supposed to be the introverted, non-people person! But the client meetings I'm in for my college senior project go off the rails into awkward mumbling unless I step in and take the tiniest bit of effort in driving a meeting.

Am I doomed folks to become a BA or other person dealing with clients all day, pls end me now

That feeling when Linux has better support for image formats... 😂

I've tried to open ARW files on Windows all day, no luck. Works 'out of the box' on my Antergos system.

Just finished a defect fix, and turns out there's another unrelated but harder bug in the codebase. We are in the last few days of the release.

I told my tech leads that it was an unrelated problem and showed them in detail. I told them I was starting work on it now, but there should probably be a new defect entered for it.

They actually said for me to piggyback the old defect and let this go under the radar. Actually laughed it off like it was no big deal. Like WTF! I don't think its very unreasonable for devs to want separate defects for separate bugs. They're worried about analytics and shit, but I'm the one left holding the rug, looking like I spent a week on a trivial defect.

The company I work at severely limits the days we can take off, like most requests I put in will be denied. Additionally, I don't get paid that well or even get paid for time off or holidays. Obligatory: the job I work at currently is co-op, I'm still in college.

Yesterday and today I was severely burnt out so I said I was sick when I wasn't really so I could get some (unpaid) time off. It's likely that the current release we're targeting at work will be in jeopardy because of this. I feel so guilty, should I be? I really needed this time, I doubt I could have continued much longer without this.

TLDR, please help me justify not giving a shitty job my unconditional 100% and being shitty back every once in a while

I graduate college in December and I got my first fulltime job offer today! I've been working in my university's oit department for 3 semesters, lol most of rants are about that job. I guess a lot of my frustration stemmed from being capable but hitting a wall in the sort of things I worked on. I didnt feel like I was growing and had no avenues to express concerns/feedback towards the end. Plus the job was not one where they could give me a job after graduation, so I just felt unseen and discardable day to day.

But turns out this job worked out for me! There's an opening in a whole other division that does api development and data warehousing with Snowflake/Attacama and they want me specifically for it. If the benefits/pay ends up being decent, I'm leaning towards accepting it.