Hope you're using Kotlin

Good devs are rare so treating them like shit works in nobody's favour. To be fair, no one deserves to be treated like shit, but devs enjoy being in a market where they are always in demand, so there's no reason not to leave a toxic workplace.

@C0D4 @pandasama @Lensflare Now that we've established that mid and senior both can take a project from start to finish, there must be something in their approach that differentiates these two levels of engineers. What do you think that is?

@electrineer lol thanks for the non-answer

@electrineer higher pay, of course. But what would you expect from a person who got there deservedly?

@electrineer what's up with your profile 😮🤔

Our team always made good use of time before the pandemic but ever since WFH kicked in, a lot of meetings go way over the time limit. All other things about WFH are great though.

@PonySlaystation awesome!

@PonySlaystation and PHP is pay ha pay because it makes you pay

@C0D4 @sariel Damn. We don't do releases or release branches. Just merge to main once it's done and approved. If the feature is not ready to be released to the users we put it under a feature toggle.

@PonySlaystation map the business logic in a miro board and burn the whole thing down. Only a fresh start can save this codebase

@PonySlaystation The sum of their estimates is 4 story points but I guess the actual effort was 2 points.

@PonySlaystation I'm assuming they only made the junior devs work on it who didn't know any better. Happened to me when I was starting out. They made me work on a codebase that had a controller with 8000 lines of code. With no seniors to guide me, I added 4000 of my own. Don't ask what happened next.

@PonySlaystation cute when people try to write their own frameworks because they're too lazy to learn how Symfony/Laravel/anything works

Gradle is the best package manager but people are not ready for that conversation

Did you get someone from fiverr to write that

My past employer did a similar thing to me after I was involved in a car accident that nearly killed my whole family. I quit as soon as I got my paycheck for the month. Burned my entire savings while trying to find a new job but totally worth it. That thing still haunts me.

Good rant

I love it when there's a long discussion in a pull request about the naming of a class/enum. Epic way to kill time and still be doing actual work.

@useVim with TypeScript you can

Don't understand why in some companies they only let the manager talk to the client. What do they gain from this? If devs could talk to clients, things would happen in a much more efficient way and the client would have greater transparency into the process.

@Voxera are y'all hiring? 😂

Sounds like the company is prioritizing dev productivity and mental health by giving them whatever they need to get the job done. Ask for a curved 34" monitor next.

Whoa dude

I think if you're about to reach a point where you are an expert in your company's legacy systems, it's time to leave asap.

@pandasama Sorry you're in this situation. This should be a wake up call for the company to invest a bit of time in improving the tech.

It never happens. Enjoy it while it lasts.

My favourite is when the recruiter lies to you about the range and it achieves absolutely nothing other than a bunch of people wasting their time having inconsequential discussions.

Legacy code is okay as long as the company is committed to actively working on modernizing it. If you are stuck with adding features and fixing a shitload of bugs in a legacy codebase, it's time to leave and look for a place where you'll be able to work with better tech and learn to tackle new challenges.

I would just quit. If I can't use IntelliJ it's a deal breaker.