|
Hello Reader, The way agents are built just changed. AWS published a new library this week that lets you write prompts directly inside your code, and the LLM generates the actual logic at runtime. Just a comment describing what you want. Here is what that looks like in practice. Instead of writing a full Python function to pull 30 days of stock data from Yahoo Finance, you write one line: "Use the Yahoo Finance Python package to retrieve the historical price of the stock in the last 30 days." The agent reads that at runtime, generates the code, and runs it. The output is a full HTML report comparing stock trends. Twenty to thirty lines of prompts did what used to take hundreds of lines of code. This is not vibe coding. Vibe coding still produces human-readable code that someone has to read, maintain, and explain. This removes that bottleneck entirely. The code is optimized for the LLM to read and generate, not for a developer to review. Before I became Principal Solutions Architect @AWS, I was in Mainframe for 10+ years. One thing I realized during my struggles of switching from legacy technology to the cloud (and eventually Big Tech) was, you always have to be laser focused on what any big change means for your career. Let's explore that next. What this means for your career If coding becomes a less critical factor in building agents, what fills that gap? System design knowledge. You are not held down by memorizing syntaxes anymore. Solutions Architects, equipped with the knowledge of customer, and infrastructure trade offs, can create POCs faster. Solutions Architects become more valuable as the code layer gets abstracted away. Three things to watch for For the next couple of years, traditional coding and prompt-in-code will coexist. After that, full hand-written code will likely be reserved for high-performance, low-latency systems where every millisecond matters, similar to how assembly language still exists in hedge funds. General software will shift to this new model. The attack vector shifts with this model. Static and dynamic code scanning tools are built to analyze code. When the logic lives in a natural language prompt, those tools do not apply. Security tooling will need to catch up, and that gap is real. This can't be used for highly regulated compliant workloads yet. Code generation is also nondeterministic. The same prompt can produce different code on two separate runs. One run might be efficient. The next might not. There is no guarantee of consistency yet. What to do now Learn the Strands Lab framework from AWS. Other companies will release similar tools, and getting familiar with the pattern now puts you ahead. More importantly, build something with it and add it to your body of work. Recruiters and hiring managers are looking for people who understand where the industry is going, not just where it has been. The people who will win in this shift are generalists who understand systems, not specialists who only know syntax. Keep learning and keep rocking 🚀, Raj P.S - If you want to get an AWS Solutions Architect job without coding or learning every AWS service, the 8th cohort for AWS SA Bootcamp is launching on May 16th, 12 PM ET (Eastern Time) via live webinar. Please register for the webinar below:
Here’s what you get when you show up LIVE:
And good news - it already worked for last cohort's students who secured cloud jobs in top companies, including at AWS, Microsoft, Google, JPMorgan, Reddit, and some of them didn't even have cloud experience 💰. Spots are limited, so don't miss it! |
Free Cloud Interview Guide to crush your next interview. Plus, real-world answers for cloud interviews, and system design from a top AWS Solutions Architect.
Hello Reader, As a former Principal Solutions Architect at AWS, and Distinguished Cloud Architect at Verizon, I conducted 300+ interviews. And every cloud interview has this question. Every. Single. One. "How will you make your application scalable for a big traffic day?" And almost every candidate gives the same answer: "I'll use an Auto Scaling Group with EC2s and a load balancer to distribute traffic." Technically correct. Completely average. Three years ago that answer was fine. Today it...
Hello Reader, "Are microservices better than monolith?" - this is a very popular interview question and real world project topic. Another variation of this is asking differences between monolith and microservices. Let me clear something up right away: monolith is not the bad guy. When I conducted hundreds of interviews at AWS as Principal Solutions Architect, I have seen candidates walk into interviews ready to trash the monolith and declare microservices the winner. That is the wrong move....
Hello Reader, Not all System Designs are created equal! To make matters complicated, there are so many designs out there. As a former Principal Solutions Architect at AWS and Distinguished Cloud Architect at Verizon, I have taken over 300+ interviews, and I have seen three patterns coming over and over in interviews. In this newsletter edition, we will go through 3 System Design patterns that appear the MOST in cloud interviews and actual projects. If you nail these 3, you will be ahead of...