A book review for Pride and Paradev by Alister Scott.
This is an entertaining and thought-provoking “collection of agile software testing contradictions”—exactly what it says on the tin.
After reading this book, I now identify confidently as a paradev: anyone on a software team that isn’t a specialist. Ever since my start in web development 12 years ago I’ve considered myself a generalist rather than a “pure” developer or designer because I don’t spend all my time building or creating new things. Software testing is an excellent fit for me because I love breaking things, finding details to make existing products better through improved flow and efficiency.
Using a quirky yet concise question-and-answer format, Scott covers such topics as “Are software testers the gatekeepers or guardians of quality?” (Yes, you can be an advocate of quality without being a gatekeeper; it all depends on your attitude, your tone, and how you present your findings.) and “Should acceptance criteria be implicit or explicit?” (Keep acceptance criteria focused on what is required, not what is obvious.) and “Do agile software testers need technical skills?” (Sometimes non-technical testers without the deep skill set see things with better eyes.)
This short and approachable book will make you think critically about software testing. Highly recommended for anyone working with software, not just us breakers.
[Available on Leanpub for iPad/Kindle/PDF.]
Software developer—and former technical writer—Jim Grey gives advice to technical writers looking to stay in software as a focus on user experience (UX) replaces the need for technical writers.
Software technical writing is a dying career (but here’s what writers can do to stay in the software game) | Stories from the Software Salt Mines.
…the writing is on the wall. If you’re not finding fewer technical writing job openings yet, you will soon. Fortunately, your skills transfer to other jobs in software development organizations. You will need to build some new skills for many of these jobs, but you might be able to land that first new job without them and build them as you work.
New roles suggested include testing and quality assurance, product management, and UX/design.
…I think this trend toward effective UX is better for the user, and gives writers good paths for growth.
I love these tips and specific role descriptions. I’d say this advice applies to anyone who loves writing and documentation and wants to move into product design and development.
(Technical side notes: I found this post via the WordPress.com Reader’s suggested blogs to follow. I then posted it to this site using the Press This function in WordPress, called “WordPress Post” under Advanced Settings in the new WordPress.com interface. Screenshot example.)