The Scene
WWDC, April 2010, Steve Jobs takes the stage, and among other things, he declares Apple will ban Adobe Flash from its devices, especially iOS.
Silence dropped on Flash communities everywhere, Flex, Air, Flash Studio, and my beloved ActionScript3… soon-to-be dead. Years of honing skills, best practices, and architecture would soon be unwanted, unpaid skills.
What It Meant to Be a Flash Developer
Flash and the technologies around it were not a gimmick or your typical 6-month new shiny framework, it had a vibrant ecosystem and worldwide communities, entire enterprises trusted it (I remeber working for a spin-off project for the New York Stock Exchange (NYSE) at the time, using only Flex and ActionScript3), because it offered true cross-platform support, before it became a buzzword. Real craftsmen with real careers were built upon these technologies.
The Six-Month Gauntlet
After the announcement on WWDC, as it is natural, some were in denial, argued that the whole situation is a bubble, and that Flash would come back and refuse to become a beginner again.
Others like myself decided to take the leap of faith and dive into HTML5, CSS, and JavaScript/JQuery, Angular was also starting to emerge.
I remember the uncertainty, code that looked weird and foreign, and the late nights driven mostly by anxiety about the next day. Overall, this phase lasted about six months, then suddenly code started to become easy and familiar, and late nights were now driven by the joy of exploration, and anything seemed possible.
That wasn’t the last time
The emergence of hybrid frameworks, the rise of the low-code movement, Objective-C making way for Swift, Java pushed over by Kotlin, framework after framework, developers come across this pattern all the time, whether they take the time to think about it or not. Creative destruction has happened in this industry since its inception. Smart investment and remaining versatile were always crucial for survival.
Now Look Around
GenAI is doing to the traditional dev role what the iPhone did to Flash. The skills shifting: from pure implementation to orchestration, from writing code to directing agents, from feature delivery to system architecture at a higher level of abstraction.
We can clearly see all the same behaviours, effects, and anxieties. We can also see these champions who have embraced the changes and started their path of re-inventing themselves. They still need to do the occasional late-night dance with the documentation and changelogs, but history has shown that if they continue on this path, they will come out stronger and more able to handle the new era.
The Veteran’s superpower
What Flash survivors had in common: they were willing to be beginners again. Curiosity over ego. Versatility over depth in a dying niche. As veteran engineers, we have already proven we can survive a stack extinction (or more) — that resilience is the skill. We all need to bring ourselves to remember that feeling of discovery and achievement, that moment when the new stack became familiar, and we secretly told ourselves, “I can do this!”
Impostor syndrome can hit hard on this journey, but we can counter it by reminding ourselves of past successes.
Brave New World
Have you wondered what the reinvented developers will look like now? Prompt engineer, orchestrator, automation architect, agent designer.
This isn’t “less” engineering — it’s engineering at a higher altitude.
The Flash developers who didn’t adapt aren’t in the industry anymore — or they are, but they’re fighting for relevance. The GenAI moment is right now, not in two years. Educate yourself. Experiment. Tweak. Break things.
The ones who read history are the ones who survive it.
Enjoy!
We’ve Been Here Before: What the Death of Flash Taught Us About Surviving the GenAI Era was originally published in Level Up Coding on Medium, where people are continuing the conversation by highlighting and responding to this story.
