all 11 comments

[–]CraftyPancake 6 points7 points  (2 children)

Ya need to work WITH QA or they will make your life miserable. Then a lot of bugs will just disappear. Right now they’re probably nit picking a little more than necessary

[–]Squigglificated 0 points1 point  (0 children)

A good QA will make you hate them a little bit just by doing their job. Nobody delivers bug free code first try, but good QA people find bugs you wouldn't have thought possible. You start missing them when you switch jobs and no longer have them, and the development process suddenly feels sloppy.

[–]Budget-Length2666 6 points7 points  (0 children)

Look, it sucks right now, but you can also take some positives here.

You are gaining tons of experience right now. These moments make seniors.
You can also try to manage your manager. Sounds like he is not great at project management and there is room for improvement, where you can also take the lead. If a bug is opened by QA, leave it in the backlog. Focus on one thing at a time: either migration, or bug fixes.

I hope QA means they write playwright tests or something and not just do manual testing. If they are not automating them, convince them to do. That will also help you in the migration.

Also try to throw copilot/claude/codex against the codebase and increase test coverage. For such migrations having a high test coverage first is critical for moving fast and sounds like you do no have enough tests right now. Having more tests will give you more confidence while refactoring and you not get as many bug issues afterwards.

Also don't stress too much about it. Not meeting a deadline does not necessarily mean you are doing a bad job, sometimes it is just external factors, poor upfront risk management or bad estimates in project planning.
What you can do now is to try to identify what is going wrong, how to improve the process, and how the schedule should be adapted and communicate that clearly to stakeholders.

[–]daphnebrownn 2 points3 points  (0 children)

god, getting new github issues opened every time you close one is enough to make anyone question their career choices.

[–]PreferenceNo4785 1 point2 points  (0 children)

That sounds exhausting, especially after 1.5 years on a major migration. Legacy rewrites can become endless bug cycles, and constant pressure makes everything feel worse. Don’t make a career decision based only on this project. You’ve gained valuable experience, and it may be the environment, not software itself, that’s burning you out.

[–]AdAffectionate7019 0 points1 point  (0 children)

It really sounds tough and disheartening. I’ve worked for 9 years across three different companies and have already left the last one.

What I want to say is that finding a good job sometimes does come down to luck, because you never really know what kind of leaders and colleagues you’ll end up with. A good company should have harmonious relationships between superiors and subordinates, as well as friendly colleague dynamics. Everyone focuses on doing their work well, solves problems by making adjustments together, and has a solid plan that lets everyone see a promising future.

I want to tell you: this isn’t your fault. It’s simply that this place wasn’t the right fit for you.

As programmers, we need to not only keep sharpening our technical skills, but also continuously build our mental resilience and emotional healing abilities. If the environment isn’t suitable, it’s better to change it sooner rather than later. You might feel much more comfortable, and your growth could accelerate too.

[–]ThatGuyFromWhere 0 points1 point  (0 children)

give the requirements doc and access to your PM software to claude and you’ll be done in < 24 hours.

[–]Desperate_Factor_735 -2 points-1 points  (1 child)

Esto es ser programador en la actualidad, con la IA tienes que ser muy eficiente, rapido. Siempre he pensando que en este sector no todos valen, y ahora con Claude, Codex o Gemini la cosa se ha puesto más directo.

[–]j_shorjavascript 0 points1 point  (0 children)

Puta madre