What's in a title?: Difference between revisions
Jump to navigation
Jump to search
m
→I am a Software Quality Engineer
mNo edit summary |
|||
| Line 52: | Line 52: | ||
* and much more. | * and much more. | ||
All of these lend themselves to varying degrees of automation, without | All of these lend themselves to varying degrees of automation, whereas without automation, some of these tasks can become repetitive, tedious, and time consuming. I hold the view that creating the whole interconnected ecosystem necessary to efficiently analyse and monitor the quality of a software solution is a genuine engineering activity. | ||
---- | ---- | ||
| Line 60: | Line 60: | ||
---- | ---- | ||
== My old (pre 2024) intro ... == | == My old (pre 2024) intro ... == | ||
In the blurb at the top of my CV I used to call myself a '''Full Stack Agile Quality Analyst''' (original text below). However, I feel it no longer fully resonates with me, some of the words like "Full Stack" and "Agile" have had their day. We now generally expect people to adjust to the context they've been placed in, to simply get on and do the job as best they can with the resources available. To be able to recognise the things that need doing the most, to communicate concerns and ideas, and to have a shared commitment to achieve the most for our users, customers, team mates, and organisation. Full Stack seems to me to mean you're happy to google for (new) solutions to a problem on your plate, rather than simply handing it over to another person in the organisation. In addition, Agile seems to have become a de-facto industry norm. Of course Agile is hard to do properly, but saying you're into Agile development seems superfluous these days. | In the blurb at the top of my CV I used to call myself a '''Full Stack Agile Quality Analyst''' (original text below). However, I feel it no longer fully resonates with me, some of the words like "Full Stack" and "Agile" have had their day. We now generally expect people to adjust to the context they've been placed in, to simply get on and do the job as best they can with the resources available. To be able to recognise the things that need doing the most, to communicate concerns and ideas, and to have a shared commitment to achieve the most for our users, customers, team mates, and organisation. Full Stack seems to me to mean you're happy to google for (new) solutions to a problem on your plate, rather than simply handing it over to another person in the organisation. In addition, Agile seems to have become a de-facto industry norm. Of course Agile is hard to do properly, but saying you're into Agile development seems superfluous these days. | ||