I&#x27;m a software engineer at a SaaS company whose product is a large (mostly just complicated) java webapp.  The company has seen a good amount of growth over one year and things are starting to explode on the software side of things.  Mainly, the fact that the code is fragile spaghetti that has zero unit tests (untestable by design) and there is a lack of software development process.<p>My issue is that I am feeling pressured from having to handhold QA after I fix a bug.  I spend more time doing this than actually writing code.<p>Here is a typical process to fix a bug in our application:
1. A bug is found
2. The reporter logs a ticket into JIRA often lacking how to reproduce the bug, and what the expected results are.
3. The SE gets assigned the ticket and needs to contact the reporter to find out how to reproduce and figure out what the expected result is.
4. After development, it is up to the SE to show the QA person how to test this new feature or confirm that the bug is fixed.<p>A few comments on QA:
They are non-technical.  Documentation is poor, so the SE&#x27;s need to show QA how to reproduce the bugs and what the expected result is. SE&#x27;s tried making step-by-step videos on how to test the code change, but that has proven to be a waste of time, as SE&#x27;s are still asked to be hands on with QA.  Sometimes there will be a bug deep in the architecture that can&#x27;t be reproduced in the front-end.  QA is very lost at how to test these.  Also, we get a lot of cases, where QA thinks that a test failed, but it turns out that they just had lack of knowledge of the acceptance criteria and prior functionality.<p>Management doesn&#x27;t want to enforce a process because it slows everything down.<p>Honestly, I&#x27;m pretty lost here because I can hardly articulate the intricacies of the entire situation.  Is this common? I&#x27;d really like to get some sage knowledge on what&#x27;s going on here, cause all I see is a painful cycle.
Ask HN: How can I influence a change in this development process?