About

The Practical Developer is a blog about software development, written by Waqas Shahid, an Engineering Manager based in Karachi, Pakistan, with more than 12 years of experience leading distributed software teams across SaaS, eCommerce, Cybersecurity, and EdTech.

The aim of this blog is to explain the languages, frameworks and tools that working developers actually use, in plain language, with practical examples you can try yourself. Articles here cover programming languages, web development, databases, DevOps and cloud, testing, and software architecture.

Waqas has worked as an Engineering Manager, Team Lead, and Principal Software Engineer. His most recent role was Engineering Manager at KnowledgeCity, Inc. (January 2026 - May 2026, remote). Before that, he was Engineering Manager at Polymer Solutions Inc. (December 2024 - September 2025) and at RepairDesk Inc. (March 2024 - November 2024), and Team Lead at Daraz.pk (Alibaba Group) from January 2018 to March 2024. He holds a BS in Computer Science from SZABIST, Karachi (2010-2014). He writes here in his own time, sharing what he has learned building and shipping real software.

If you have a question, a correction, or a topic you would like covered, please use the Contact page. You can also see his professional background on the Resume page linked in the menu above.

Comments

Post a Comment

Popular posts from this blog

Rust Explained: Memory Safety Without a Garbage Collector

You run a small command line tool that parses a daily export file, and twice a month it crashes on a row nobody expected. The file is fine on Monday, a supplier adds a column on Tuesday, and by Wednesday your tool has died at 3 a.m. with a message nobody on call can explain. The crash is a memory or data handling mistake that a stricter language would have caught before the program ever ran. That is the problem Rust is built to solve: programs that are fast and also refuse to compile when they mishandle memory. Rust gives you C level speed without a garbage collector pausing your program. The trick is a set of rules, checked by the compiler before your program ever runs, called ownership. Every value has exactly one owner, the variable that holds it, and when the owner goes out of scope the value is cleaned up automatically. Move the value to another variable, and the first one can no longer use it. fn main() { let line = String::from("A1,2,120.50"); let moved = lin...
Read more

Jest Explained: Testing JavaScript Without the Setup Headache

A customer buys a notebook and two pens, and the shop charges them 29.28. Then one changed line in the basket code makes the same order come to 29.27, or to zero. Nobody notices until a customer complains, because nobody rechecked the maths after the change. That is the job a test does: a small program that runs your code, checks the answer, and tells you the moment the answer changes. Jest is the tool most JavaScript developers use for that job, and it is popular because it removes the setup that used to put people off testing. Install it, write a test that reads like a sentence, run one command, and you get a pass or a precise failure. What I would check before using it My judgement, from writing and reviewing JavaScript for years, is this: use Jest when the behaviour you are protecting is worth more than the few minutes it takes to write the test, which is true for almost any code that handles money, user data, or anything a customer will see. I would not write a test suite for a ...
Read more

Three.js Explained: 3D Graphics in the Browser

An online shop sells a water bottle, and the product page shows one photo from the front. Customers cannot see the back, cannot judge the size, and cannot tell how the cap works, so they ask questions, or they buy elsewhere. A spinning 3D model would answer all of it, but the web is flat by default: HTML and CSS lay out rectangles, and the browser's low-level 3D API, WebGL, takes hundreds of lines to draw a single cube. That is the gap Three.js closes. It wraps the graphics pipeline in friendly concepts, scenes, cameras, lights, and meshes, so a developer can build a 3D product viewer or a data visualisation in an afternoon instead of a month. A minimal scene follows the same pattern every time: create a scene, add a mesh, add a light, point a camera at it, and animate it in a loop, each frame rotating the mesh slightly so it appears to move. That loop is the heartbeat of every Three.js app. What I would check before using it My judgement, from building web pages and watching 3D...
Read more