Senior DevOps, located in Mexico City. Originally from Australia but have been living in Mexico City for over 8 years. In my down time, you can find me taking pictures and documenting life in Mexico
I wish I had thought about this before joining my current project, because knowing what I know now, it may have changed my destination.
Now don't get me wrong I love my current job but the politics at the moment. Our Engineering team is less than 15 people myself included if you had told me that I would have passed on the job, I know what happens in small teams it ends up being a handful of talented people doing the job while others do the bare basics. Due to the fact its a small team it can sometimes get a little heated, when it comes to the feedback. I have found that larger teams of more than 20 people its more sustainable.
Also if I new our development process I would have never joined, what is is that no testing lets keep pushing into production and fix the bugs as we go.... Real makes for fun times, being on the phone to the customer explaining the latest patch broke the system, and they will need to wait a few hours while we debug the system.
Try being on a team building the software calculating loads to go on rockets to and from the International Space Station, without testing. No, seriously. And, of course, they did Friday commits (cuz why not?) The sad thing is, it was the most capable team of devs I've ever worked with; they were just ridiculously overworked and management insisted that new features were always more important than testing.
I joined as a front end lead and, after kicking and screaming each retrospective about testing, finally stepped on toes and created my own team to create our own testing framework. Within a month we were at 90% test coverage.
I got fired and replaced with unpaid interns, but I'll take that any day over killing astronauts or answering to a Congressional investigation over it.
Omg that's wild. I just can't understand the logic of that! How do they sleep at night, really?? Is it a total lack of empathy, inability to think of others, or what.
How many bugs would you said you guys were able to catch with the introduction of testing with a project like that, which was previously completely untested?
OMFG so many. I knew I was on borrowed time for calling out management, but even some of the other teams were probably gunning for me when they started getting test failures and test coverage alarms on commit (which is stupid, because they had both the authoring app and the test runner on their local). Like, hearing dozens of grumbles of "God damn it" from nearby cubicles each day, for the first week especially. The devs I commandeered to work on it would IM our group "DRINK!" (we made it into a mock drinking game) every time it happened.
I really wish I had the foresight to open source it before giving it to them. I'm sure it was quickly abandoned after I left.
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
I wish I had thought about this before joining my current project, because knowing what I know now, it may have changed my destination.
Now don't get me wrong I love my current job but the politics at the moment. Our Engineering team is less than 15 people myself included if you had told me that I would have passed on the job, I know what happens in small teams it ends up being a handful of talented people doing the job while others do the bare basics. Due to the fact its a small team it can sometimes get a little heated, when it comes to the feedback. I have found that larger teams of more than 20 people its more sustainable.
Also if I new our development process I would have never joined, what is is that no testing lets keep pushing into production and fix the bugs as we go.... Real makes for fun times, being on the phone to the customer explaining the latest patch broke the system, and they will need to wait a few hours while we debug the system.
I'll definitely be asking about testing next time I'm job hunting. Once you've lived with automated testing, you don't want to go without!
Try being on a team building the software calculating loads to go on rockets to and from the International Space Station, without testing. No, seriously. And, of course, they did Friday commits (cuz why not?) The sad thing is, it was the most capable team of devs I've ever worked with; they were just ridiculously overworked and management insisted that new features were always more important than testing.
I joined as a front end lead and, after kicking and screaming each retrospective about testing, finally stepped on toes and created my own team to create our own testing framework. Within a month we were at 90% test coverage.
I got fired and replaced with unpaid interns, but I'll take that any day over killing astronauts or answering to a Congressional investigation over it.
Omg that's wild. I just can't understand the logic of that! How do they sleep at night, really?? Is it a total lack of empathy, inability to think of others, or what.
When it comes to government prime contractors, you'd have about the same level of effectiveness by just setting piles of cash on fire.
How many bugs would you said you guys were able to catch with the introduction of testing with a project like that, which was previously completely untested?
OMFG so many. I knew I was on borrowed time for calling out management, but even some of the other teams were probably gunning for me when they started getting test failures and test coverage alarms on commit (which is stupid, because they had both the authoring app and the test runner on their local). Like, hearing dozens of grumbles of "God damn it" from nearby cubicles each day, for the first week especially. The devs I commandeered to work on it would IM our group "DRINK!" (we made it into a mock drinking game) every time it happened.
I really wish I had the foresight to open source it before giving it to them. I'm sure it was quickly abandoned after I left.