Software Engineer’s Problems — With ‘Shift-left’ everything, what’s left on the right? A view from the middle.
A prospective client once said, “We are starting up a new testing team, we need 20 Java engineers with mortgage domain experience”!
He also said they are trying to shift-left, in a big way!
This was 2017 and somewhat understandable, given the testing stack and the fact that test automation was a big theme for a lot of our financial services clients.
Starting in 2018-2019, I have started seeing signs that, developers asked to be experts in AWS infrastructure setup, VPC (Virtual sub-nets), and yeah, we also want them to validate and remediate security and application pen testing issues on their own, auto-generated security code smells by CI pipeline.
Then shortly after, Gartner apparently said, we need to shift right?!?
Now in, 2020, we started seeing clients look at development teams for help in setting up the highly resilient Kubernetes and Kafka environments, and setting up monitoring on the cloud. Developers now need to be experts at submitting and managing IaC — Infrastructure as Code — e.g., Terraform scripts!
The concept of shift-left, or specifically, shift-left-testing originated at the time of Agile and DevOps coming into prominence (for large organizations, anyway), back in 2016/17, as part of shifting testing focus early and often, during the SDLC loop.
Now, as you might have seen and (hopefully) agree with me, that somehow everything we do as part of SDLC is shifting left — Now, shifting left for me, means — i.e., engineering team and product team. But for some, they incorrectly assume, it is “engineering team”.
So, what’s left on the right? It was Technology Operations, but, now, since everything automated? What are operations, mean?
Major components of the right moved to left, it started off with DevOps, now, we have DevSecOps, CloudOps, InfraOps, NoOps — you name it, we have it — all focused on Developer owning them :)
So, 10- years ago, we had something like this, in terms of SDLC:
