Me: Do you want it done quickly or do you want it done right?

Manager: Yes

Of course we deployed on Friday. How else are we gonna have a nice quiet weekend.

The guy worked 4 days building a nice challenging feature.
Fucking spend 30 more minutes to write a documentation on how it works bc is like you did nothing.

Me: Im testing a new feature that is not on production yet for 30m and can not make it work. (I asked the developer for any idea why is not working)
Dev: i just tested, works fine.
Me: i just tested again with no luck. I’m i missing anything?
Dev: (Developer comes to my desk). Lets see what you doing wrong here. (After 5seconds). You have been redirected to the production site and you've been testing there all this time.
Me: 😩

Anyone else has a love/hate relationship with Mageno, or just hate?
:p

Me: Im testing a new feature that is not on production yet for 30m and can not make it work. (I asked the developer for any idea why is not working)
Dev: i just tested, works fine.
Me: i just tested again with no luck. I’m i missing anything?
Dev: (Developer comes to my desk). Lets see what you doing wrong here. (After 5seconds). You're not on UAT. You have been redirected to the production and you've been testing there all this time.
Me: 😩

LastPass or 1Password for teams?

Other suggestions are welcomed but need to pick on of the above.

Fuck QA
Love QA
Fuck QA
LOVEEE QA

Couple of advices from the QA guy

1) Don’t do the bare minimum bc the PM asks that. The people that write up the tasks/requirements don’t know their shit sometimes. Or even worse, they just copy paste what the client asked.
2) Confront the PM and ask more time to build something robust and scalable. When shit don’t work, people will blame the devs which is not fair. Is not easy but put your foot down when you’ve being asked to build shitty stuff bc the client want it ready now.

Discovered devrant today. I'm reading for three hours strait