—About
How I Think About Engineering
I'm Afzal Imdad — a full-stack and blockchain engineer based in Karachi, Pakistan. I've been building production software since I was 15, working across frontend, backend, smart contracts, and AI — often all in the same project.
I think in systems. Every application I build, I approach as a set of interconnected concerns: data flow, state management, API boundaries, contract security, deployment topology. I'm not drawn to frameworks for their own sake — I choose tools based on what the system needs.
What makes my path unusual is that I've been doing production engineering — smart contracts, GraphQL APIs, Web3 dashboards, payment gateways — while still completing my secondary education. I'm currently finishing my Matriculation (Science) while leading full-stack development at Zenveus.
Experience
Where I've Worked
Principles
Architecture & Engineering
SOLID
Five object-oriented design principles — Single Responsibility, Open/Closed, Liskov Substitution, Interface Segregation, and Dependency Inversion — that make software easier to maintain and extend.
Clean Architecture
Robert C. Martin's architecture pattern that isolates core business logic from external concerns through concentric layers, ensuring the system remains testable and framework-independent.
Domain-Driven Design
An approach to software development that centers the implementation around a model of the core business domain, using ubiquitous language to bridge developers and domain experts.
GoF Design Patterns
The 23 classic Gang of Four patterns — creational, structural, and behavioral — providing reusable solutions to common object-oriented design problems.
CQRS
Command Query Responsibility Segregation separates read and write operations into different models, allowing independent scaling and optimization of each pathway.
Circuit Breaker
A resilience pattern that prevents cascading failures by wrapping calls to remote services in a circuit breaker that monitors failures and trips open when a threshold is exceeded.
Bulkhead
A fault isolation pattern that partitions system resources so that failure in one component does not cascade to others, similar to watertight compartments in a ship's hull.
SAGA Pattern
A distributed transaction pattern that breaks a long-running transaction into a sequence of local transactions, each with a compensating action to handle failures.
Two-Phase Commit
A distributed atomic commit protocol where a coordinator ensures all participants either commit or abort a transaction through a prepare phase and a commit phase.
CAP Theorem
Brewer's theorem states that a distributed data store can only simultaneously provide two of three guarantees: Consistency, Availability, and Partition tolerance.
Consistent Hashing
A hashing technique that minimizes key remapping when nodes are added or removed from a distributed system, forming the backbone of distributed caches and partitioned databases.
Raft Consensus
An understandable consensus algorithm that manages replication logs in distributed systems through leader election, log replication, and safety guarantees.
Paxos
A family of protocols for solving consensus in a network of unreliable processors, providing a theoretical foundation for distributed coordination despite message loss.
Skills
Domain Proficiency
Certifications
Earned & Planned
Earned
Planned
AWS Solutions Architect
Amazon Web Services
Azure Developer Associate
Microsoft
GCP Professional Developer
Google Cloud
CKA / CKAD
CNCF
HashiCorp Terraform Associate
HashiCorp
Docker Certified Associate
Docker
OpenJS Node.js Developer
OpenJS Foundation
Meta Front-End Professional
Meta
MongoDB Developer Associate
MongoDB
TensorFlow Developer Certificate
AWS ML Specialty
Amazon Web Services
CompTIA Security+
CompTIA
Ethereum Developer Certification
Ethereum Foundation
Certified Solidity Developer
Blockchain
Chainlink Developer Certification
Chainlink
Soft Skills
How I Work
Systems Thinking
I see applications as interconnected systems, not isolated features.
Self-Directed Learning
I learned production engineering while completing secondary school — through documentation, shipping, and iteration.
Technical Communication
I write clearly about architecture decisions and translate complex systems for non-technical stakeholders.
Adaptability
I switch between frontend, backend, smart contracts, and infrastructure as the project demands.
Ownership
I take responsibility for the full lifecycle — from requirements to deployment to monitoring.