2

I hate it when I fuck up an update and don't realize it until the next morning.

Did an update last night. Had a large amount of bugs that I had to fix. Some caused by me not testing all the way, some caused by some other guys doing maintenance last night and me not knowing about it.

Woke up to a text from my boss asking if I even tested the program last night. Yeah, I just made sure it loaded after the nightmare amount of bugs I had. I just missed a portion of the program. So I fixed the portion of the program and then he asked me to roll the program back and try again tonight.

What makes this even better is I was really hoping for this to go smoothly. I'm also doing another program release and its going really fucking badly too, security is fucking the shit out of me. My peer review is Monday. I haven't gotten a raise in a year and a half since I started at this company and I was going to ask for one. But this kind of dashes my confidence on the rocks.

Comments
  • 2
    Is there no QA process at all?

    At our place it's a case of
    - reproduce on prod
    - reproduce on staging
    - push fix to staging and QA verify
    - push to prod
    - verify

    That can catch the bugs but also detect repercussions elsewhere in the system
  • 0
    @FakeDeveloper not really unfortunately. We're a two person department as of recently. We try to do all the QA we can. I try to automate unit testing as much as I can too. UI testing is pretty time consuming so I've only had a few projects where I've been able to sit down and automate some interfaces.

    I get a lot of pressure to constantly produce software. So I don't have a lot of time to be in the QA stage of things. I compensate by trying to automate testing, but that only gets you so far.

    We're pretty under staffed right now so it's been a scramble trying to push stuff out. A lot of stress leads to missed stuff in prod.
  • 2
    I'd bring that up with your boss, if they get hissy about things breaking and wanting fixes, tell them we need more QA time or a QA team. I agree automated testing will only get you so far and if you have no time for it then no time is spent looking at the testing to improve it. Things take time and if you're having to crank out dev work constantly with no time for process improvement, then things will break, or worse you'll burn out
  • 0
    @FakeDeveloper I've brought up a QA guy a few times. Hell, I've even brought just hire an intern and they could test stuff and automate unit tests for us all day. But it always leads to a dead end.

    In this specific case we didn't even have a QA environment setup for testing this site I deployed. It had gone directly to prod. But in most cases our security guys get to dictate what they see as separation of systems and then afterwards our environments are so far skewed from one another you might as well drop the new binaries on machine running on the ISS.

    I've been trying to get my boss to get the azure pipeline setup for about a year now and he's at least getting the vp to talk about it. But it feels so slow I might as well not even try to contribute sometimes.
Add Comment