There is a question I hear often, usually in Arabic, usually asked a little shyly: "Is it too late for me? My English is weak. Can I still become a real developer?"
I build apps in Arabic and in English, and I run developer clubs inside an app whose readers mostly write in Arabic. So here is the honest answer. It is two answers, and they point in opposite directions.
Answer one: yes, you can start, and the door has never been wider
Look at the numbers first.
- About 1.5 billion people speak English, but only around 360 million speak it as a first language (Ethnologue estimates via Statista, Babbel). Most English in the world is spoken by people like you: people who learned it, imperfectly, as adults or teenagers.
- English is still the language of about half of all websites whose language can be detected, but that share has been falling for years, from over 60% to under 50% (W3Techs).
- Programming languages use English keywords, but
if,forandreturnare about as hard to learn as road signs. Nobody fails at code because of the wordwhile.
And then there is the change nobody predicted five years ago: you can now ask an AI assistant to explain an error message, a paper or a documentation page in your own language, and ask follow-up questions until it makes sense. The cost of reading the technical world in English just collapsed.
History agrees, too. Ruby, one of the most loved languages of the 2000s, was created in Japan, and its early community and mailing lists were largely in Japanese. Great software has been born outside English many times.
So if your question is "Can I start?", the answer is yes. Start today, in your language.
Answer two: no, you cannot stay at the top without it, at least not yet
Here is the part people do not like to hear.
Tech is not only code. It is the conversation around the code: issues, pull request reviews, conference talks, job interviews, design debates at 11pm, the README that convinces a stranger to try your project. Today that conversation happens mostly in English.
If you cannot take part in it, three things happen quietly:
- You learn late. New tools are explained in English first, and the translation arrives months later, if ever.
- You stay invisible. Your work can be excellent and still nobody outside your circle finds it, because it is described only in a language they do not search in.
- You get paid less. Global remote work, open-source sponsorship and most fellowships expect you to write and speak in English.
AI translation helps you read. It does not yet help you be present: speaking in an interview, defending your design in a review, telling the story of your product in your own voice.
So what should you actually do?
My advice is to separate four skills instead of saying "my English is weak":
| Skill | How much you need to start | How much you need to grow |
|---|---|---|
| Reading technical English | A little, with AI help | A lot |
| Writing (issues, commits, READMEs) | Short sentences | Clear paragraphs |
| Listening (talks, videos) | Subtitles are fine | Most of it |
| Speaking (interviews, calls) | Not needed | Enough to explain your work |
Then train them like any other skill: fifteen minutes a day of spaced review beats one heroic weekend a month. I wrote about this in Arabic for our readers: fifteen minutes a day with spaced repetition and graded readers, the calm path to English.
And write in English early, badly, in public. Your first README will be clumsy. Your tenth will be fine. Nobody remembers the first one.
The bigger question
I think the honest future is this: AI will keep lowering the wall for understanding the world in English, while English stays the room where being seen happens, for a while. The developers who will win are not the ones with perfect grammar. They are the ones who start in their own language and refuse to stay invisible in it.
I would like to hear from you, especially if English is not your first language:
- What helped you most to move from reading English to speaking it at work?
- Do you think AI translation will make English less important for developers in ten years, or more?
- Should communities like ours teach programming in local languages first, or switch to English as early as possible?
Saifuddin Ahmed builds Ishraqa Daily, a place to read, build and learn together, and founded OtwoX Digital Solutions. More at saifuddin.dev and LinkedIn.
I drafted this piece with an AI writing assistant. The experience, the opinions and the questions are my own.

