This week's book giveaway is in the Reactive Progamming forum. We're giving away four copies of Reactive Streams in Java: Concurrency with RxJava, Reactor, and Akka Streams and have Adam Davis on-line! See this thread for details.
I have been in my current role for 1 year but lately I have been very frustrated. I was hired as a Java Developer at my current company and spent the first 6 months building a web application using Hibernate and Spring MVC. Everything went well and I really enjoyed my job, I felt like I was learning and doing exactly the type of work that made me happy.
After 6 months, the development work was completed and I was asked to help out on a different project in a QA role. Initially my work was Test Automation with Selenium, although it wasn't application development I was still coding in Java. However, I was asked to help out more on Manual QA because the QA team was falling behind. Now for the past 6 months, I have been nothing but Manual Testing. In the beginning I did learn a few things like bug reporting, how to create test plans, etc, and I felt that made me a better overall developer. However, I find manual testing extremely boring, the work is not challenging, just extremely repetitive
I can't see myself doing this type of work for another 6 months, even 1 month would be too much. At this point in my career (year 3), I want to keep improving my development skills and I feel that this role is not helping me. I am thinking about quitting, we are currently downsizing our dev team, so theres likely no opportunity to be moved back to dev, also our management team doesn't prioritize test automation. Any advice for me? Has anyone else been in a similar position? I have normally always been willing to help out in any area (dev, operations) but this is not why I had in mind when I joined this company.
Sounds to me like it's time to up periscope for your next position. It sounds like you have had some good experience previously in your current job, but if there's no chance to continue development, doing continuing manual testing isn't going to do anything for your skill set or career.
Bear Bibeault wrote:Sounds to me like it's time to up periscope for your next position. It sounds like you have had some good experience previously in your current job, but if there's no chance to continue development, doing continuing manual testing isn't going to do anything for your skill set or career.
Thanks for the reply, I'm thinking the same thing Bear
Guess I should dust off and polish up that resume!
I have worked as a support engineer for a short while. Like with your job, it still involved programming. It was developer support of a software library. Nevertheless somebody like a recruiter only looks at your last job. So, I repeatedly said to them I have far more programming experience than support experience, I repeatedly said my second and third line developer support of a library involved a lot of programming, nevertheless the recruiters kept on pushing me towards a next support role.
Ok, this is what I don't understand. When people do Manual testing, why don't they just record it while they are testing it? They are automating the testing while doing the manual testing right? Yes, if you are using Selenium, the recording won;t be perfect, and you will need some time fixing it, but that's still a little bit better than not recording it, right?
What I would suggest is
a) While you are doing manual testing, start recording your test
b) Spend some extra time fixing up some of your tests
c) Next time you are asked to test the same thing again, use your recording. This will free up your time to fix other recordings
posted 5 years ago
I took the advice I received and decided to look for a new job.
Within two weeks I received two offers both with a significant pay increase.
I'm excited since I will be doing Java development once again
* +25% $$$ (salary)
* Small company
* Enhancements to existing application (~10 years old)
* Using older technologies
* Casual dress code (jeans / polo)
* 5 minute drive from my house
* +28% $$$ (hourly / contract to hire)
* Very large company, larger team
* Newer technologies / agile development
* Formal dress code (slacks / dress-shirt)
* 5 minute drive from my house
I'm leaning towards company B, the newer technologies and faster pace of development sounds fun
I really appreciate all the feedback I received !!!