🇬🇧🇮🇷 Technical Lead Software Architecture Engineer - Full Stack Web Developer - Creator of #ParsClick - Loves @laravelphp, @vuejs, @reactjs
London, England
Joined June 2009
- Tweets3.8K
- Following1K
- Followers1.9K
- Likes7.6K
Pinned Tweet
برای یکی از مشتریهام اپ دوستیابی «شیطونک» رو ساختم 💕
چند نفر با گوشی اندرویدی میخوایم که تستش کنن و حداقل ۱۴ روز نصب نگهش دارن.
اگه پایهاید، ایمیلتون رو دایرکت کنید تا به لیست تسترها اضافهتون کنم 🙏
play.google.com/apps/testing…
1
2
362
Azimi retweeted
Absolutely legendary update just dropped.
Azimi retweeted
AI can write code in seconds.
So why are companies still looking for great engineers?
Because writing code was never the whole job.
The real skill is knowing what to build, how to build it, and how to make it work in production.
Here’s the roadmap to becoming an AI engineer in 2026 🧵
1. Master the Fundamentals
Before jumping into AI, build a strong foundation.
→ Python, JavaScript, or C++
→ Data Structures & Algorithms
→ OOP and problem-solving
→ Databases and APIs
→ Computer science fundamentals
AI can generate code, but understanding it is what makes you a better engineer.
2. Learn Real-World Software Engineering
Knowing how to code isn't enough. You need to know how to ship.
→ Frontend and backend development
→ Git and collaboration
→ Cloud computing
→ CI/CD and DevOps
→ System design and scalability
→ Security and performance
This is where you stop writing code and start engineering systems.
3. Learn to Build With AI
This is where the game changes.
→ AI coding assistants
→ LLM APIs and prompt engineering
→ Function calling and structured outputs
→ RAG and vector databases
→ AI agents and automation
→ Model evaluation and observability
Don't just learn how to use AI tools. Learn how to build products with them.
4. Learn Production AI Engineering
A demo that works once isn't a production-ready product.
You need to understand:
→ Hallucinations and failure handling
→ AI security and guardrails
→ Testing and evaluation
→ Latency and cost optimization
→ Monitoring and reliability
→ Deploying AI systems at scale
This is what separates AI experimenters from AI engineers.
5. Build Projects That Solve Real Problems
Tutorials teach you concepts. Projects teach you engineering.
Build an AI agent. Connect it to real tools. Add authentication, error handling, logging, and deployment.
Then test whether it actually solves the problem.
That's how you turn knowledge into experience.
The biggest mistake you can make right now?
Learning to prompt AI without learning how software works.
AI is making coding faster, but engineering still requires judgment.
The developers who thrive won't be the ones who write the most code.
They'll be the ones who know what to build, understand what AI generates, and can turn it into reliable products.
Learn the fundamentals. Master the tools. Build real things.
That's the path to becoming an AI engineer.
Save this roadmap for your learning journey.
Azimi retweeted
Who's gonna tell vibe coders about...
1. SQL Injection
2. XSS
3. CSRF
4. CORS
5. SSRF
6. IDOR
7. Path Traversal
8. Mass Assignment
9. Clickjacking
10. Content Security Policy
11. Security Headers
12. Input Validation
13. Server-Side Authorization
14. Row-Level Security
15. Least Privilege
16. RBAC
17. Secrets Management
18. .env in .gitignore
19. API Key Rotation
20. Secret Scanning
21. Hashing vs Encryption
22. Password Salting
23. bcrypt & Argon2
24. JWT Expiry
25. Refresh Tokens
26. OAuth 2.0
27. OpenID Connect
28. Session Fixation
29. MFA
30. Brute Force Protection
31. Account Enumeration
32. Timing Attacks
33. File Upload Validation
34. Webhook Signature Verification
35. TLS Certificate Expiry
36. HSTS
37. Encryption at Rest
38. Dependency Vulnerabilities
39. Supply Chain Attacks
40. Threat Modeling
41. Indexes
42. EXPLAIN ANALYZE
43. N+1 Queries
44. Full Table Scans
45. Connection Pooling
46. Database Migrations
47. Down Migrations
48. Transactions
49. ACID
50. Isolation Levels
51. Deadlocks
52. Optimistic Locking
53. Pessimistic Locking
54. Normalization
55. Denormalization
56. Foreign Keys
57. Unique Constraints
58. Cascading Deletes
59. Soft Deletes
60. UUIDs vs Auto-Increment
61. Cursor-Based Pagination
62. Full-Text Search
63. Read Replicas
64. Replication Lag
65. Sharding
66. Partitioning
67. Hot Partitions
68. Postgres VACUUM
69. Materialized Views
70. Backups
71. Testing Your Restores
72. Point-in-Time Recovery
73. Change Data Capture
74. Outbox Pattern
75. ORM Lazy Loading
76. CAP Theorem
77. Eventual Consistency
78. Strong Consistency
79. Raft Consensus
80. Leader Election
81. Split Brain
82. Quorums
83. Clock Skew
84. Distributed Locks
85. Consistent Hashing
86. Bloom Filters
87. Two-Phase Commit
88. CQRS
89. Event Sourcing
90. Race Conditions
91. Backpressure
92. Load Shedding
93. Bulkheads
94. Jitter
95. Retry Storms
96. Cascading Failures
97. Thundering Herd
98. Cache Invalidation
99. Cache Hit Ratio
100. TTLs
101. Cache Warming
102. Write-Through vs Write-Back
103. Redis Eviction Policies
104. CDNs
105. Cache-Control Headers
106. ETags
107. Dead Letter Queues
108. Poison Messages
109. At-Least-Once Delivery
110. Exactly-Once Semantics
111. Message Ordering
112. Kafka Consumer Groups
113. Partition Keys
114. Background Jobs
115. Webhook Retries
116. DNS
117. DNS Propagation
118. HTTP Status Codes
119. HTTP Method Semantics
120. Keep-Alive
121. HTTP/2
122. WebSockets
123. Server-Sent Events
124. Long Polling
125. gRPC
126. Protocol Buffers
127. API Versioning
128. OpenAPI Specs
129. Backward Compatibility
130. Request Size Limits
131. Compression
132. Latency vs Throughput
133. Egress Fees
134. VPCs
135. Subnets
136. NAT Gateways
137. Firewalls
138. Security Groups
139. Service Mesh
140. Ingress Controllers
141. Health Checks
142. Liveness vs Readiness Probes
143. Graceful Shutdown
144. Connection Draining
145. Stateless Services
146. Failover
147. Multi-Region
148. Availability Zones
149. Single Points of Failure
150. Disaster Recovery
151. RTO & RPO
152. SLAs
153. SLOs
154. Error Budgets
155. Incident Response
156. On-Call
157. Runbooks
158. Postmortems
159. Chaos Engineering
160. Graceful Degradation
161. Autoscaling
162. Horizontal vs Vertical Scaling
163. Cold Starts
164. Capacity Planning
165. Load Testing
166. Memory Leaks
167. OOM Killer
168. Structured Logging
169. Log Levels
170. Log Rotation
171. Distributed Tracing
172. OpenTelemetry
173. Correlation IDs
174. Metrics Cardinality
175. p99 Latency
176. Alert Fatigue
177. Error Tracking
178. Profiling
179. Flame Graphs
180. Infrastructure as Code
181. Terraform State
182. GitOps
183. Blue-Green Deployments
184. Canary Releases
185. Rollbacks
186. Feature Flags
187. Environment Parity
188. Staging Environments
189. 12-Factor Apps
190. Multi-Stage Builds
191. Non-Root Containers
192. Image Scanning
193. Resource Requests & Limits
194. Pod Disruption Budgets
195. Semantic Versioning
196. Lockfiles
197. Reproducible Builds
198. Branch Protection
Azimi retweeted
Introducing Flock PHP 1.0 beta!
A 100% free and open source local development environment for Laravel and PHP, native on macOS and Windows.
No paid tier, every feature included.
Download now at flockphp.com
1/3
Azimi retweeted
Pollora: run WordPress inside a Laravel 13 application
laravel-news.com/link/19253?…
هوش مصنوعی میتواند تمام نرمافزارهای ادوبی را بسازد؟ youtube.com/shorts/ledMJkBfo… via @YouTube
99
Azimi retweeted
It's pencils down, people. Writing code by hand is no longer an economically viable skill for most programmers at most companies. But the future of making software has never been brighter. Don't you dare black pill this beautiful moment! youtu.be/vDjW_dRyKXY?si=6Fsf…
Azimi retweeted
How many pencils, how many humans, how many hours would it have taken to recreate the Adobe suite by hand?
Todos los productos de Adobe reimplementados desde cero, gratuitos y de código abierto
→ getartcraft.com/apps
ALT Interfaz de herramientas creativas para edición de imágenes, ilustración, video y desarrollo de bibliotecas.
Why AI hasn’t replaced software engineers, and won’t open.substack.com/pub/aisnak…
81
Azimi retweeted
This is one of the things how Anthropic earned disrespect from the community, slowly over many months.
Claude(.)md and .claude/skills
They want to be UNIQUE.
Branding, I get it.
But, as a result, it make them unique in a BAD way.
Azimi retweeted
نظرسنجیهای ایران اینترنشنال با نتایج وحشتناکی به پایان میرسد.
جامعهای که بیش از ۸۰ درصد مردمش، در آرزوی ترک وطن هستند و بیش از ۹۰ درصد جوانانش تمایلی برای ازدواج و فرزندآوری ندارند، باید نخبگان و سیاستمدارانش را به وحشت بیاندازد.
همه چیز در آستانه انفجار است. حتی معجزه هم نمیتواند ناجی این حکومت باشد.
