Letter from the Editor – June 2021

Because of the type of work I do (consulting projects at different companies), I’ve been lucky in my Software Development career to have worked on a bunch of software projects specific to hardware devices or integrating new hardware into software systems. Starting with the Palm Pilot, I worked on some operating systems (OS) projects, firmware, drivers, and the like. Some of the skills I developed I never used again… but, many skills opened up doors to other jobs and my knowledge in testing hardware integration, particularly automating testing of wifi-enabled smart devices (IoT) and voice systems. 

Had I stayed in the area of my first few jobs where I was building some subject matter expertise, my domain knowledge would have increased, but the technical knowledge gained proved more beneficial. Working on a variety of projects for various companies forced me to learn a variety of technical skills I would not have learned had I stayed at one company. Building a wider variety of skills is important to anyone’s career, or whether you will become a “Full-Stack” Tester or not. But in these days of Digital Modernization or Full-Stack Product Teams, floating between testing tasks from database to browser to mobile to back end is the new norm.  

The same situation happened when I jumped to a data and database project at a different company. This was a completely different product development and testing situation. Over time, I gained a pretty wide variety of tools for my toolbelt: Device and OS, driver, firmware, and hardware integration testing skills; web and server testing skills, followed by database skills; jobs that were only API testing; jobs that were IoT, wifi-connected devices; jobs that were testing cloud systems… I could go on.

Now we are in a world of Digital Modernization. The big benefit here is that with Digital Modernization, the whole idea is modernizing with new technologies, cutting-edge technologies, and data––lots of data. But, we can’t forget modernizations like automating processes, adding connected devices, or moving to the cloud; these are all typical for Digital Modernization.

For many teams, the issue with Digital Modernizations is having the skills to build and test new and complex systems. Lately, what is becoming more common in product development vernacular and where the conversation turns to is the phrase “Full-Stack Development.” The full-stack tech worker is the jack of all trades. “Full-stack” is most commonly referred to as “Full-Stack Developer” but also as “Full-Stack Tester.” The point here is that they’re a multi-skilled team member who can go from front end to back end with added skills in the newest technologies. This is a tall order for any team, but in Digital Modernization, we’re now not only testing web systems, but also devices to data, to servers, and to the cloud. And, of course, the testing should be automated.

There’s a lot of discussion today around this idea of both Full-Stack Development and Testing. Adding to your technology skills regardless of what you do is essential, but there are really 3 options here:

  1. You can try to learn as many skills as you can. Be careful about only scratching the surface or only having high-level knowledge. You do not want to be a jack of all trades, but master of none.
  2. You can have a complete skill set across the team. Have multiple people on the team be sufficiently skilled in general but also have a new area of expertise. This way the entire team when looked at holistically is full-stack.
  3. Outsource to fill out the skill set. Then, you’ll have the freedom to build more skill overtime or have individual experts and the team before stack. Outsourcing can give you the flexibility to hire for specific technology gaps on a team. You can also outsource all the tech need and keep internal teams focused on domain/subject matter testing. This is particularly helpful with new technologies added into your modernization projects.

Building skills and growing in technical skill, testing skill, as well as domain knowledge is a tall order. But, it is the nature of our job! And, the goal behind LogiGear Magazine has always been to help you in this effort.

As you begin or continue your Digital Transformation journey, we want you to know that LogiGear is here to help you at every step of the way, and that’s precisely why we’ve dedicated this issue to DXs. Our cover story breaks down the 4 key components of a DX, as well as the 7 pillars of an effective DX strategy. When it comes to a DX, you hear many reasons as to why you should embark on a DX journey, but sometimes the benefits aren’t always clear; in our article 4 Business Benefits of Digital Transformation, we outline 4 overarching benefits that you can expect to reap after a successful DX implementation. While this piece focuses more so on the overall business and organizational benefits, we also created Digital Transformations Effect on QA to give a voice to and hear the opinions of the people putting in the work to actually push the DX forward. Our infographic, What’s Driving Digital Transformations, takes a step back to look at the external forces of the global business market that are driving these mass digital strategy adoptions, as well as commonly cited roadblocks to a DX implementation. Finally, in this issue’s Blogger of the Month, Jabil delves into a survey they ran that asked tech leaders what the biggest challenges to DX was, as well as recommendations on how to overcome them.

We hope you enjoy our June 2021 Magazine––Happy Digitizing!

Michael Hackett
Michael is a co-founder of LogiGear Corporation, and has over two decades of experience in software engineering in banking, securities, healthcare and consumer electronics. Michael is a Certified Scrum Master and has co-authored two books on software testing. Testing Applications on the Web: Test Planning for Mobile and Internet-Based Systems (Wiley, 2nd ed. 2003), and Global Software Test Automation (Happy About Publishing, 2006). He is a founding member of the Board of Advisors at the University of California Berkeley Extension and has taught for the Certificate in Software Quality Engineering and Management at the University of California Santa Cruz Extension. As a member of IEEE, his training courses have brought Silicon Valley testing expertise to over 16 countries. Michael holds a Bachelor of Science in Engineering from Carnegie Mellon University.

The Related Post

There is a growing software development dynamic of teams without Testers. When I first went into Software Quality, I learned one thing right away: My role was user advocate. My main job was to find bugs. This is the Lean principle called Amplified Learning. We learn about behavior by testing. Even then, validation was not ...
Change is constant. What’s different today is the rate of change. Moore’s law resulted from the observation that that the rate of change in computing power is exponential. The products, services and software landscape appears just as dynamic. At the same time, we pretty much take for granted the ubiquitous presence of software running our ...
If you are reading this issue, you are probably aware of the impact on the business world of cloud computing. Most people do not have a good grasp on what the cloud is or how people and products can use it. BTW, you are already a cloud user. If your email is stored somewhere “on ...
LogiGear Magazine June Issue 2021: DX & CX’s Impact on Software Testing
Digital Transformation is changing the global business environment with efficiency, security, and connectedness; learn how to overcome common roadblocks to DXs so that you can reap the benefits of a digitized business model.
On the whole, everyone wants to do a great job, have a better work environment, happy clients and customers, and to be employed by a company earning lots of money. All great goals! But this is not always the case. When it is not, you can suggest process improvements, better tool use, different estimating techniques, ...
DevOps can be a big scary thing. Culture change, constant collaboration— whatever that means— a big new set of tools… it’s a lot. What most teams want is to have a smooth running software development pipeline. I have stopped using the phrase “DevOps,” and now I say “Continuous Delivery.” There are many reasons for this.
I remember the times when test teams sat in their own area and we were not allowed to “bother” developers.
I spend about half my work time in the role of a consultant assessing, auditing and examining software development team practices and processes for the purpose of process improvement. I am regularly surprised to find teams that lack basic skills, management support, tools, information, access to users, Product Owners and to developers. And yet they’re ...
Test automation is a big topic. There are so many different areas to talk about: tool choice, jumpstart, cross platform, services, cloud… Each of these areas have changed so much in the recent past that they could each be worth their own magazine issue.
Hi everyone and welcome to our fourth edition of LogiGear Magazine. This month we finish Michael Hackett’s piece on “Agile in Testing” with part five, Tools.
As we settle into autumn, we’re taking the time to start some new traditions. This is LogiGear magazine’s first issue on SMAC. SMAC—social, mobile, analytics and cloud. We will be doing more issues in the next few years on these topics since so much of the product world is moving to this development stack.

Leave a Reply

Your email address will not be published.

Stay in the loop with the lastest
software testing news

Subscribe