Everyone generally agrees code reviews are a good idea right? And some form of testing is kinda a requirement before releasing.

Nope not my boss at the moment. None of my work has been checked in any way but is going out to thousands of users.

If I take the heat for bugs I'm gonna hit back so hard

I have the same situation today and I do feel you man. Tell us how it went and stay strong! #no time for test #friday release

Hahaha that's so true, happened with me last week when my head released an iOS app on iTunes just to find out it had massive device specific bug.

The only excuse for this is if you are part of a 2 person company, your boss, and you.... but even then, your boss could double as QA

for the love of God, NO RELEASES ON FRIDAY

I had a boss one time tell me not to testing just concentrate on developing and let the users do that. Well I just did testing anyway - it is part of development. Idk about the value of regular code reviews though..

It's your code, not your bosses. It will ultimately fall on you if things go out messed up. This I can pretty much guarantee. That said, CYA (cover your a**) and review and test it yourself. No one blames the one who should have caught it, just the one who didn't.

Based on what I'm hearing, your boss is beyond incompetent. How long have you been working there?

@kdiggity The boss decides how I spent my time though. You decide where you want to work.

I too was forbidden to write test in a former company. Hence I went were code quality matters.

This reminds of one of my former rants:

https://devrant.com/rants/320838

I bookmarked this this article by Eric Elliot long ago and share it liberally until everyone at work gets sick of me.

Thank you Mr. Elliot if you're out there.

https://medium.com/javascript-scene...

To follow up a few people's comments.
Don't get me wrong, generally the job is good, I'm just having a rant about this one thing that pissed me off (it's the first day I've gone home unhappy).
I've been working here just under 2 months, it's basically a junior role but they don't call it that. In that time no one has checked my code, no one else is working on this project and they have been fairly hands off in just leaving me to it, which seems crazy to me but is nice in some ways. Theres about 15 devs so plenty of people could be checking my stuff. The company has some other more serious projects that they do testing and generally have better practices for so it seems they aren't taking this one so seriously, even though they still want to make it a big project with lots of users generating lots of money etc.

My bosses excuse for wanting to push out the update is that it crashes currently in production so this update will be an improvement, then we'll do another update once everythings finished next week. Thing is it's been broken in production for months and they haven't bothered fixing it, now all of a sudden it's urgent and we'll be doing two updates in two weeks. Not to mention it could be broken in different ways now because no one else has even looked at it apart from me (I have no confidence in my ability to write bug free code even after doing some tests myself 😆 )

@allthingsinmod thank you that's a good article. Im totally on board with the thinking that TDD is a good thing, especially when it comes to writing tests before fixing a bug to ensure you never have that same problem again. Testing is definitely a skill I need to work on though

Well that sad truth. Boss usually want product ship fast to customer despite of code quality

@allthingsinmod that's a great link. bookmarked!