With bullshit jobs, could you expand on finding meaningful work? It's something that has eaten me up the last while (non meaningful work and being unsure what direction to head to find it)
I've searched a few reviews of the book but largely seemed to focus on how many jobs are pointless rather than finding non pointless stuff
Any advice on finding a working logical argument? I find myself stuck in unhelpful loops sometimes i.e. Do I enjoy my job? Do I have a sense of purpose in my job?
I realise the answer will be personal and only I can provide it but I'm consistently failing and it's impacting my mood
Improve testability throughout applications by working with their team, setup and maintain test frameworks (hopefully improving them over time), determine what tests should be automated and those that shouldn't, write automated tests, coach team members on writing automated tests and testing in general, add new tools/processes to improve testing, investigate the application in-depth to find risk areas.
I'd be curious if HN think the above includes things that shouldn't be there or is missing a number of items? I'd be curious what the 80/20 for an automation engineer looks like?
I think you're jumping to an awful lot of conclusions there?
The reason I'm targeting automation is that it tends to be done really badly in most companies. At the moment I feel I do it pretty well but always seek to improve. At the moment I don't feel like I'm improving much and want to avoid things staying static for long. Therefore I'm trying to re-evaluate the basics or gain new insight and get back on track
wow, thank you for your incredibly detailed reply. I'll ensure I refer back to it again and again. Often I have the problem I'm in the midst of right now, I focus on specifics rather than the bigger picture and the general things you need to keep in mind while working.
Thank you very much for going to the time and effort of that reply, I really appreciate it.
2) Automated browser/ui tests, hopefully I'll get to move more toward the api/service/functional level as well. First stop will be to essentially build a regression suite.
Other
1) Nope.
2) Using agile
3) Not constrained other than by management and other workload. Essentially I can make testing here what I want and I want to make it good. I'm fighting some pretty old ideas on a regular basis.
4) Basically no, they've hired me and another guy to 'develop' it but I had zero testing experience and the other guy has a few years, though has never led.
5) No, it's Patrick!
I feel I have a knack for doing some unexpected things when I have freedom to think and I'm not hugely rushed. Unfortunately I don't get much support from management. For example, I found an unexpected bug which I and several devs thought was a 'show-stopper', the product owner thought this was, 'testers running through unrealistic scenarios.'