George Prokopakis retweeted
Τι αναθέτουμε στην τεχνητή νοημοσύνη και τι πρέπει να προσέχουμε στις αποφάσεις μας αυτές; kathimerini.gr/opinion/56455…
This is exactly what I see everywhere I go and what I hear from everyone I talk to: they need more people, not fewer.
In fact, many companies are telling me they are stuck because they can't find enough talent in the market.
They are already using the latest-and-greatest AI-thingies out there, but they don't have enough warm bodies to operate them.
These agents aren't magic. They, for the most part, aren't autonomous. They are cool and all, but they need people who know their stuff.
This is even more acute for building software. Yes, anyone can vibe-code simple apps here and there today, but building working software for thousands of user is still very demanding, and agentic coding helps but doesn't work without experts driving it.
Unpopular opinion: In 5 years, we'll need more software engineers than we do today. Not fewer.
Everyone is calculating how many developers AI can replace. If a team of 3 can now do the work of 10, surely the other 7 are out of a job?
I think that completely misses what's about to happen.
For decades, the biggest constraint on software wasn't the lack of problems worth solving. It was the cost of solving them.
Millions of businesses still run on spreadsheets, emails, WhatsApp messages, and outdated software. Not because they're happy with it, but because spending $200,000 on a custom system never made financial sense.
Now imagine that same system costs $20,000. Suddenly, millions of businesses that couldn't afford software development become potential customers. Projects that were never viable become viable. Companies that already build software can afford to do ten times more.
And here's the part people underestimate: the cheaper software becomes, the more reasons we'll find to build it.
Of course, some jobs will disappear. Certain tasks that once required entire teams will be handled by a single engineer. But assuming the amount of software the world needs is fixed is a pretty strange assumption, especially in an industry where we've barely scratched the surface of what can be automated.
I could be wrong, but I think we're heading toward an explosion in software demand, not the death of software engineering.
We're confusing the declining cost of writing code with the declining demand for software engineers. They're not the same thing.
George Prokopakis retweeted
"Almost every software development organization has at least one developer who takes tactical programming to the extreme: a tactical tornado. The tactical tornado is a prolific programmer who pumps out code far faster than others but works in a totally tactical fashion. [...] In some organizations, management treats tactical tornadoes as heroes.
"However, tactical tornadoes leave behind a wake of destruction. They are rarely considered heroes by the engineers who must work with their code in the future. Typically, other engineers must clean up the messes left behind by the tactical tornado, which makes it appear that those engineers (who are the real heroes) are making slower progress."
@JohnOusterhout, A Philosophy Of Software Design, 2018
Sound familiar?
George Prokopakis retweeted
Is this the future of software engineering?
AI has made code generation dramatically faster. But that doesn’t necessarily mean software development is getting faster.
That was one of the most interesting points from my conversation with Kirill Skrygan, CEO of JetBrains at the launch of JetBrains Air last week.
As coding accelerates, the bottlenecks are moving elsewhere: code review, technical debt, maintainability, observability, knowledge sharing, governance and understanding whether AI is actually delivering ROI.
We discuss why solving those problems requires thinking beyond tools for individual developers, and instead looking at the whole software engineering organisation, from ICs and team leads through to engineering directors and CTOs.
It’s an interesting perspective on where AI-assisted software development goes next.
In the attached video, Kirill explains what JetBrains Air is and the problems it’s designed to solve.
In the full interview, we go deeper into his experience with AI and agentic coding, how software engineering is changing, and why JetBrains believes the next generation of tooling needs to support the whole engineering organisation, not just the individual developer.
You can watch the full interview on YouTube: youtu.be/SY3XJnLIriI
George Prokopakis retweeted
Experience gives perspective. Programming is not dead, and never will be.
It's late September 2026. Sometime in September 1976, just after I entered college, I wrote and ran my first serious program. I have now been a programmer for literally 50 years.
And man, I have seen it *all*. Punched cards to glass ttys on minicomputers to workstations to the earliest micros. I've written business software, communication programs, development tools, games, language implementations, kernel device drivers, graphics libraries, a few critical pieces of infrastructure, and all manner of odd programs for which there is no taxonomy. Coded in a score of languages some of which are now forgotten. I've run over 70 open-source projects and contributed to at least as many more.
Along the way I noticed a few things, and wrote about them, and that made me famous. But I'm not here to write about that today. I'm here to write about what it means to be a programmer and a technologist with the Singularity upon us.
I have lost count of the number of times I have been told "programming is over". You kids may think this is a new claim that came into the world with LLMs. Hah! There's been that kind of talk at every step function in the quality of our programming tools. I first heard it when compilers were replacing hand-hacked assembler in the early 1980s, and I wouldn't be a bit surprised if somebody said it earlier when in-memory code replaced plugboards.
One constant amidst all this change is that the intentions in a user's head do not magically turn into executable instructions that a computer can run. Another constant is the mindset of the people who specialize in bridging the gap between wish and algorithm. A programmer is a programmer is a programmer - the tools are secondary.
"But it's different this time!" some people will say, "AIs are superhuman now!" So? What did you think the optimization stage of a compiler was, chopped liver? We've been relying on tools that exceeded human capabilities all along - we built them precisely because our meatbrains could not otherwise keep up with the demands of the job.
It's been a hell of a ride, that 50 years. I've succeeded and failed and succeeded again. Done a lot of work I'm proud of. Built at least a few things that look like they're going to last. None of that goes away because, hypothetically, an AI might have made me faster.
The work is never done, even if the tools can talk to us now. Because intentions still have to be communicated; people who specialize in that and develop right mindset to do it still have a major advantage over people who don't.
If you're feeling depressed because you spent years or decades developing hand-coding skills that are obsolete now? Buck up. You still have the most important asset - a mind that knows how to think that way.
I'm facing the winds of the Singularity with a smile. Because 50 years and I'm still standing - still shipping code that people can use, still learning, still refusing to be paralyzed by the pace of change.
The best therapy for your uncertainty? Get to work on something.
George Prokopakis retweeted
Someone new to coding showed me their vibe-coded project. 90,000 lines of code. They were proud. I didn't know where to start. 🧵
George Prokopakis retweeted
I recently received an email titled “An 18-year-old’s dilemma: Too late to contribute to AI?” Its author, who gave me permission to share this, is preparing for college. He is worried that by the time he graduates, AI will be so good there’s no meaningful work left for him to do to contribute to humanity, and he will just live on Universal Basic Income (UBI). I wrote back to reassure him that there will still be plenty of work he can do for decades hence, and encouraged him to work hard and learn to build with AI. But this conversation struck me as an example of how harmful hype about AI is.
Yes, AI is amazingly intelligent, and I’m thrilled to be using it every day to build things I couldn’t have built a year ago. At the same time, AI is still incredibly dumb, and I would not trust a frontier LLM by itself to prioritize my calendar, carry out resumé screening, or choose what to order for lunch — tasks that businesses routinely ask junior personnel to do.
Yes, we can build AI software to do these tasks. For example, after a lot of customization work, one of my teams now has a decent AI resumé screening assistant. But the point is it took a lot of customization.
Even though LLMs can handle a much more general set of tasks than previous iterations of AI technology, compared to what humans can do, they are still highly specialized. They’re much better at working with text than other modalities, still require lots of custom engineering to get it the right context for a particular application, and we have few tools — and only inefficient ones — for getting our systems to learn from feedback and repeated exposure to a specific task (such as screening resumés for a particular role).
AI has stark limitations, and despite rapid improvements, it will remain limited compared to humans for a long time.
AI is amazing, but it has unfortunately been hyped up to be even more amazing than it is. A pernicious aspect of hype is that it often contains an element of truth, but not to the degree of the hype. This makes it difficult for nontechnical people to discern where the truth really is. Modern AI is a general purpose technology that is enabling many applications, but AI that can do any intellectual tasks that a human can (a popular definition for AGI) is still decades away or longer. This nuanced message that AI is general, but not that general, often is lost in the noise of today's media environment.
Similarly, the progress of frontier models is amazing! But not so amazing that they’ll be able to do everything under the sun without a lot of customization. I know VC investors who are scared to invest in application-layer startups because they are worried that frontier AI model companies will quickly wipe out all of these businesses by improving their models. While some thin wrappers around LLMs no doubt will be replaced, there also remains a huge set of valuable applications that the current trajectory of progress of frontier models won’t displace for a long time.
Without accurate information about the current state of AI and how it is likely to progress, some young people will decide not to enter AI because think think AGI leaves them no meaningful role, or decide not to learn how to code because they fear AI will automate it — right when it is the best time ever to join our field.
Let us all keep working to get to a precise understanding of what’s actually possible, and keep building!
[Original text: deeplearning.ai/the-batch/is… ]
George Prokopakis retweeted
The 3rd edition of my book Deep Learning with Python is being printed right now, and will be in bookstores within 2 weeks. You can order it now from Amazon or from Manning.
This time, we're also releasing the whole thing as a 100% free website.
I don't care if it reduces book sales, I think it's the best deep learning intro around, and more people should be able to read it.
George Prokopakis retweeted
Some people today are discouraging others from learning programming on the grounds AI will automate it. This advice will be seen as some of the worst career advice ever given. I disagree with the Turing Award and Nobel prize winner who wrote, “It is far more likely that the programming occupation will become extinct [...] than that it will become all-powerful. More and more, computers will program themselves.” Statements discouraging people from learning to code are harmful!
In the 1960s, when programming moved from punchcards (where a programmer had to laboriously make holes in physical cards to write code character by character) to keyboards with terminals, programming became easier. And that made it a better time than before to begin programming. Yet it was in this era that Nobel laureate Herb Simon wrote the words quoted in the first paragraph. Today’s arguments not to learn to code continue to echo his comment.
As coding becomes easier, more people should code, not fewer!
Over the past few decades, as programming has moved from assembly language to higher-level languages like C, from desktop to cloud, from raw text editors to IDEs to AI assisted coding where sometimes one barely even looks at the generated code (which some coders recently started to call vibe coding), it is getting easier with each step.
I wrote previously that I see tech-savvy people coordinating AI tools to move toward being 10x professionals — individuals who have 10 times the impact of the average person in their field. I am increasingly convinced that the best way for many people to accomplish this is not to be just consumers of AI applications, but to learn enough coding to use AI-assisted coding tools effectively.
One question I’m asked most often is what someone should do who is worried about job displacement by AI. My answer is: Learn about AI and take control of it, because one of the most important skills in the future will be the ability to tell a computer exactly what you want, so it can do that for you. Coding (or getting AI to code for you) is a great way to do that.
When I was working on the course Generative AI for Everyone and needed to generate AI artwork for the background images, I worked with a collaborator who had studied art history and knew the language of art. He prompted Midjourney with terminology based on the historical style, palette, artist inspiration and so on — using the language of art — to get the result he wanted. I didn’t know this language, and my paltry attempts at prompting could not deliver as effective a result.
Similarly, scientists, analysts, marketers, recruiters, and people of a wide range of professions who understand the language of software through their knowledge of coding can tell an LLM or an AI-enabled IDE what they want much more precisely, and get much better results. As these tools are continuing to make coding easier, this is the best time yet to learn to code, to learn the language of software, and learn to make computers do exactly what you want them to do.
[Original text: deeplearning.ai/the-batch/is… ]
George Prokopakis retweeted
If you desire to be a victim intensely enough, everything will look like an insult and everyone will look like they are mocking you.
Even when no one is thinking about you at all.
George Prokopakis retweeted
Functional programming, object programming, and structured programming are all just techniques to aid the organization of code. In any project of moderate size all three will be necessary. The three are synergistic. Together they are better than when kept separate.
George Prokopakis retweeted
The best leaders are those who, when the time comes, will put the interests of the collective -- their team, their users, their country -- above their own personal ambitions.
George Prokopakis retweeted
Programming is thinking + syntax. Maybe 90% thinking and 10% syntax. While you can automate away syntax, you can only ever outsource thinking to someone/something that can think. Attempts to outsource thinking to a syntax generator do not end well.
George Prokopakis retweeted
Whatever people don't like doing, but HAVE to (regardless why), is could be an opportunity for a product or service.
Either make it so they don't have to do it, or so it takes 1/10th the time/energy/attention.
George Prokopakis retweeted
Make Something Wonderful. Read the new online book we designed at LoveFrom with the Steve Jobs Archive. — “Think of your life as a rainbow arcing across the horizon of this world. You appear, have a chance to blaze in the sky, then you disappear.” book.stevejobsarchive.com
George Prokopakis retweeted
I’ve had some toxic jobs. Lesson learned:
When things go bad, good people leave, eventually followed by people who thought they could change things but got buried because too many good people left. Those left are bad people or hostages.
The good people are your canary.
George Prokopakis retweeted
🥳 PHP 8.1 is released!
🔗 Read all about it at: php.net/archive/2021.php#202…
♻️ Migration Guide: php.net/migration81
🐘 Many thanks to the contributors for everything they implemented, and the RMs to get this amazing new version released!
❓ What's your favourite new feature?
George Prokopakis retweeted
The results for the State of Laravel 2021 survey are online and you can even filter the analysis by the provided answers! 🚀🎉 I am thanking everyone who participated and thus contributed to the insight into the #Laravel community.
Please RT for reach ❤️ stateoflaravel.com
George Prokopakis retweeted
I’ve reviewed thousands of resumes. Best ways to make your resume pop:
• You have a few seconds to catch the eye. Find a way to do so. What makes you standout?
• Cut out filler words & keep it short.
• Discuss projects (not duties) and describe a few powerful tasks you did.



















