Mulualem Eshetu
@mulualem.bsky.social
Software engineer working on AI products.
I write about UX, agentic AI, and how complex systems reach users.
🔗 mulualem.dev
I write about UX, agentic AI, and how complex systems reach users.
🔗 mulualem.dev
September 16, 2025 at 7:27 PM
September 14, 2025 at 10:34 AM
September 8, 2025 at 6:11 AM
September 7, 2025 at 7:00 AM
If your workflow relies on fragile hacks, every update is a ticking time bomb. 🚨
Build on stable foundations → future you will thank you.
Build on stable foundations → future you will thank you.
September 6, 2025 at 1:05 PM
If your workflow relies on fragile hacks, every update is a ticking time bomb. 🚨
Build on stable foundations → future you will thank you.
Build on stable foundations → future you will thank you.
September 6, 2025 at 9:19 AM
Performance isn’t just raw speed, it’s clarity, stability & sustainability.
Write code humans can maintain, then optimize what truly matters. ✅
♻️ 📌 🔔
Write code humans can maintain, then optimize what truly matters. ✅
♻️ 📌 🔔
September 5, 2025 at 7:12 PM
Performance isn’t just raw speed, it’s clarity, stability & sustainability.
Write code humans can maintain, then optimize what truly matters. ✅
♻️ 📌 🔔
Write code humans can maintain, then optimize what truly matters. ✅
♻️ 📌 🔔
September 5, 2025 at 9:02 AM
Recursion in code is fine.
Recursion in your system design? A nightmare.
✅ Keep layers clear
✅ Avoid circular dependencies
✅ Document flows
Peak engineering = clarity, not clever hacks.
♻️ 📌 🔔
📷: ᴍᴇᴍᴇ ᴄʀᴇᴅɪᴛ ᴛᴏ ᴏʀɪɢɪɴᴀʟ ᴄʀᴇᴀᴛᴏʀ
Recursion in your system design? A nightmare.
✅ Keep layers clear
✅ Avoid circular dependencies
✅ Document flows
Peak engineering = clarity, not clever hacks.
♻️ 📌 🔔
📷: ᴍᴇᴍᴇ ᴄʀᴇᴅɪᴛ ᴛᴏ ᴏʀɪɢɪɴᴀʟ ᴄʀᴇᴀᴛᴏʀ
September 4, 2025 at 12:43 PM
Recursion in code is fine.
Recursion in your system design? A nightmare.
✅ Keep layers clear
✅ Avoid circular dependencies
✅ Document flows
Peak engineering = clarity, not clever hacks.
♻️ 📌 🔔
📷: ᴍᴇᴍᴇ ᴄʀᴇᴅɪᴛ ᴛᴏ ᴏʀɪɢɪɴᴀʟ ᴄʀᴇᴀᴛᴏʀ
Recursion in your system design? A nightmare.
✅ Keep layers clear
✅ Avoid circular dependencies
✅ Document flows
Peak engineering = clarity, not clever hacks.
♻️ 📌 🔔
📷: ᴍᴇᴍᴇ ᴄʀᴇᴅɪᴛ ᴛᴏ ᴏʀɪɢɪɴᴀʟ ᴄʀᴇᴀᴛᴏʀ
September 4, 2025 at 8:13 AM
September 3, 2025 at 8:14 AM
September 2, 2025 at 4:54 AM
Committing your .env isn’t bold, it’s dangerous. 🚨
✅ Exposes API keys & secrets
✅ Risks systems & data
✅ Fix costs > Prevent costs
👉 Add .env to .gitignore
👉 Use env vars / secret managers
✅ Exposes API keys & secrets
✅ Risks systems & data
✅ Fix costs > Prevent costs
👉 Add .env to .gitignore
👉 Use env vars / secret managers
September 1, 2025 at 12:37 PM
Committing your .env isn’t bold, it’s dangerous. 🚨
✅ Exposes API keys & secrets
✅ Risks systems & data
✅ Fix costs > Prevent costs
👉 Add .env to .gitignore
👉 Use env vars / secret managers
✅ Exposes API keys & secrets
✅ Risks systems & data
✅ Fix costs > Prevent costs
👉 Add .env to .gitignore
👉 Use env vars / secret managers
September 1, 2025 at 7:48 AM
Googling isn’t a skill.
Turning what you find into clean, reusable solutions is. 🚀
♻️ 📌 🔔
Turning what you find into clean, reusable solutions is. 🚀
♻️ 📌 🔔
August 31, 2025 at 11:35 AM
Googling isn’t a skill.
Turning what you find into clean, reusable solutions is. 🚀
♻️ 📌 🔔
Turning what you find into clean, reusable solutions is. 🚀
♻️ 📌 🔔
August 31, 2025 at 7:53 AM
Clean CSS = happy devs ☀️
Messy styles = chaos 😵💫
✅ Keep classes consistent
✅ Reuse tokens for colors/shadows
✅ Delete dead code
Good CSS isn’t just pretty. It’s scalable & keeps your sanity intact.
♻️ 📌 🔔
📷: ᴍᴇᴍᴇ ᴄʀᴇᴅɪᴛ ᴛᴏ ᴏʀɪɢɪɴᴀʟ ᴄʀᴇᴀᴛᴏʀ
Messy styles = chaos 😵💫
✅ Keep classes consistent
✅ Reuse tokens for colors/shadows
✅ Delete dead code
Good CSS isn’t just pretty. It’s scalable & keeps your sanity intact.
♻️ 📌 🔔
📷: ᴍᴇᴍᴇ ᴄʀᴇᴅɪᴛ ᴛᴏ ᴏʀɪɢɪɴᴀʟ ᴄʀᴇᴀᴛᴏʀ
August 30, 2025 at 6:39 AM
Clean CSS = happy devs ☀️
Messy styles = chaos 😵💫
✅ Keep classes consistent
✅ Reuse tokens for colors/shadows
✅ Delete dead code
Good CSS isn’t just pretty. It’s scalable & keeps your sanity intact.
♻️ 📌 🔔
📷: ᴍᴇᴍᴇ ᴄʀᴇᴅɪᴛ ᴛᴏ ᴏʀɪɢɪɴᴀʟ ᴄʀᴇᴀᴛᴏʀ
Messy styles = chaos 😵💫
✅ Keep classes consistent
✅ Reuse tokens for colors/shadows
✅ Delete dead code
Good CSS isn’t just pretty. It’s scalable & keeps your sanity intact.
♻️ 📌 🔔
📷: ᴍᴇᴍᴇ ᴄʀᴇᴅɪᴛ ᴛᴏ ᴏʀɪɢɪɴᴀʟ ᴄʀᴇᴀᴛᴏʀ
AI can boost your speed ⚡️ but speed without structure = chaos later.
✅ Small functions
✅ Clear comments
✅ Refactor often
Fast is fun, but clean is future-proof.
♻️ 📌 🔔
📷: ᴍᴇᴍᴇ ᴄʀᴇᴅɪᴛ ᴛᴏ ᴏʀɪɢɪɴᴀʟ ᴄʀᴇᴀᴛᴏʀ
✅ Small functions
✅ Clear comments
✅ Refactor often
Fast is fun, but clean is future-proof.
♻️ 📌 🔔
📷: ᴍᴇᴍᴇ ᴄʀᴇᴅɪᴛ ᴛᴏ ᴏʀɪɢɪɴᴀʟ ᴄʀᴇᴀᴛᴏʀ
August 29, 2025 at 5:30 PM
AI can boost your speed ⚡️ but speed without structure = chaos later.
✅ Small functions
✅ Clear comments
✅ Refactor often
Fast is fun, but clean is future-proof.
♻️ 📌 🔔
📷: ᴍᴇᴍᴇ ᴄʀᴇᴅɪᴛ ᴛᴏ ᴏʀɪɢɪɴᴀʟ ᴄʀᴇᴀᴛᴏʀ
✅ Small functions
✅ Clear comments
✅ Refactor often
Fast is fun, but clean is future-proof.
♻️ 📌 🔔
📷: ᴍᴇᴍᴇ ᴄʀᴇᴅɪᴛ ᴛᴏ ᴏʀɪɢɪɴᴀʟ ᴄʀᴇᴀᴛᴏʀ
August 29, 2025 at 7:36 AM
When “vibe coding” stacks up, guess who ends up holding it all together?
Quick hacks might work today, but they create shaky towers for tomorrow.
✅ Write code that’s easy to read, not just easy to run
✅ Add tests so fixes don’t break five other things
Quick hacks might work today, but they create shaky towers for tomorrow.
✅ Write code that’s easy to read, not just easy to run
✅ Add tests so fixes don’t break five other things
August 28, 2025 at 3:52 PM
When “vibe coding” stacks up, guess who ends up holding it all together?
Quick hacks might work today, but they create shaky towers for tomorrow.
✅ Write code that’s easy to read, not just easy to run
✅ Add tests so fixes don’t break five other things
Quick hacks might work today, but they create shaky towers for tomorrow.
✅ Write code that’s easy to read, not just easy to run
✅ Add tests so fixes don’t break five other things
August 28, 2025 at 10:27 AM
“Vibe coding” isn’t about lo-fi beats and coffee.
It’s when you tell AI what you want, accept the code it generates because it vibes, and move on.
That’s fun for fast prototypes, but dangerous if you stop there.
✅ Review and test AI-generated code
✅ Make sure you understand why it works
It’s when you tell AI what you want, accept the code it generates because it vibes, and move on.
That’s fun for fast prototypes, but dangerous if you stop there.
✅ Review and test AI-generated code
✅ Make sure you understand why it works
August 27, 2025 at 1:26 PM
“Vibe coding” isn’t about lo-fi beats and coffee.
It’s when you tell AI what you want, accept the code it generates because it vibes, and move on.
That’s fun for fast prototypes, but dangerous if you stop there.
✅ Review and test AI-generated code
✅ Make sure you understand why it works
It’s when you tell AI what you want, accept the code it generates because it vibes, and move on.
That’s fun for fast prototypes, but dangerous if you stop there.
✅ Review and test AI-generated code
✅ Make sure you understand why it works
August 27, 2025 at 6:48 AM
🚪 Not every feature deserves to stay forever, sometimes the best “feature” is the one you remove.
In codebases, unnecessary complexity is like unused apps:
✅ Delete dead code that nobody calls
✅ Remove outdated dependencies
✅ Simplify over “just in case” abstractions
In codebases, unnecessary complexity is like unused apps:
✅ Delete dead code that nobody calls
✅ Remove outdated dependencies
✅ Simplify over “just in case” abstractions
August 26, 2025 at 5:19 PM
🚪 Not every feature deserves to stay forever, sometimes the best “feature” is the one you remove.
In codebases, unnecessary complexity is like unused apps:
✅ Delete dead code that nobody calls
✅ Remove outdated dependencies
✅ Simplify over “just in case” abstractions
In codebases, unnecessary complexity is like unused apps:
✅ Delete dead code that nobody calls
✅ Remove outdated dependencies
✅ Simplify over “just in case” abstractions
August 26, 2025 at 8:02 AM