Shaukat Ali

I have received this question more times than I can count. Are jobs gone? Is AI taking over everything? Why are internships not coming through? What do I do with my degree or my skill? Here is my honest answer — not a motivational one. AI has made things easier, and harder at the same time. Because AI can now do multiple things, the person who knows how to get the right things done from AI is preferred over the one who does not. That is the new baseline. Learn the basics of AI regardless of which path you choose — not to become an AI engineer, but to use it well in whatever you are doing. Beyond that, I see three paths. Each one has its own direction. The mistake most people make is not choosing one and going deep on it. Path 1: Build a Personal Product This is the path I am on. I will be honest about where my experience ends. Start by finding a problem — ideally one you personally face. That is your built-in validation. If you have the problem, others likely do too....

A few days ago I saw a post on Facebook. Someone sharing that he had started learning AI, done some projects, and was now earning from it. I asked him how. He said he got a client through LinkedIn. I asked him to elaborate. He said let's talk. Seventeen minutes on WhatsApp. That was the whole conversation. But it connected more dots than months of reading about "the opportunity in AI." The problem with how most people learn AI AI is a wide field. Machine learning. Deep learning. Model development. Model deployment. Data analysis. Data analytics. Automation. Most people learning AI are aware of all of these — and that awareness becomes the problem. They keep exploring, keep switching, keep adding things to the list. A year passes and they are still learning. He told me something simple: to stand out and to get clients, you have to focus on one thing. His one thing is RAG — Retrieval Augmented Generation. Not AI in general. Not even a broad category within AI...

I was collecting user feedback on Iqra a few weeks ago. One of the users pointed out a bug. A section of the app was not working correctly. I knew the section. I had made changes to it recently — and shipped them directly to production without running through my usual testing flow. A user told me about the bug. Not my emulator. Not my test release. A user. I fixed the bug, made a few more improvements, added some things to the app. When I finally sat down to build the test release properly, this came back to me. So here it is — written down, for anyone building a product right now. The flow that actually protects you Every change, no matter how small, goes through three stages before it reaches your users. First, test on the emulator. Catch the obvious breaks early, before anything leaves your machine. Second, publish a test release and run it on a real device. The emulator lies sometimes — screen sizes behave differently, performance feels different, interactions that ...

Yeh sawaal mujhse pehle bhi pucha gaya hai. Aur honestly, ab mere paas ek clear jawab hai. Seedhi baat karta hun. Pehli cheez — clarity. Akele Baith jaunga. Aur khud se yeh teen sawaal puchhunga: Main kya seekhna chahta hun? Kyun? Aur kab tak? Simple lagta hai. Lekin zyada tar log yahan skip kar dete hain. Aur phir woh confusion aati hai jo kabhi khatam nahi hoti. Meri apni example deta hun. Flutter seekhna chahta hun — kyun? Apni app banana, usse monetize karna. Premium sell karna ya subscription lena. Kab tak? Ek saal. 365 din. Aur goal? 200 ya 1000 users. Bas. Itna hi kafi hai shuru karne ke liye. Warna kaam karte raho aur pata hi nahi kab success hai aur kab failure. Phir requirements dekhta. Flutter ke liye kya chahiye? Flutter khud. App development. Product marketing. Toh Flutter sikhna shuru karta. Pehle 2-3 lambi videos — sirf flow samajhne ke liye. Widgets kya hain, cheezein kaise connect hoti hain. Yaad karne ke liye nahi — bas ek mental map. Phir 2-4 ...

Bhai aap ny Flutter kese sikha — yeh sawaal mujhse kai baar pucha gaya hai. Aaj honestly bata deta hun. Seedhi baat karta hun. Maine Flutter sikhne ke liye koi special course nahi kiya. Koi bootcamp nahi. Koi structured plan nahi tha. Mere paas already C++, C#, HTML, CSS, JavaScript, PHP, Python ka background tha. Toh Flutter ek nayi language ki tarah nahi thi — ek nayi duniya thi jisme samajhna tha ke cheezein kaise chalti hain. Maine 2-3 full-length videos dekhe. Har ek 1 hour se zyada ki. Lekin goal yeh nahi tha ke sab yaad ho jaye. Goal sirf yeh tha ke flow samajh aaye. Components kya hain, cheezein kaise connect hoti hain. Bas. Phir maine project shuru kar diya. Aur yahan se asli story shuru hoti hai. Pehla hafte — setup. Sirf setup. Dependencies download hoti thi. Ghanton tak. Mere paas 4Mbps connection hai — ek typical Pakistani developer ki tarah - shayd kch zyada. Ek cheez download hoti, kuch aur missing hota, phir kch aur, phir kch aur. 7 din. S...