🎙 Open Mic Session: Featuring Yohannes Haile

We’re excited to welcome Yohannes Haile — a well-known iOS developer in Addis with over 4 years of experience building and shipping consumer-facing iPhone applications both locally and internationally — to our next Open Mic Session.

Yohannes is recognized for his strong expertise in native iOS development, including building and distributing frameworks using Swift Package Manager and CocoaPods. His deep understanding of iOS APIs and the Apple ecosystem sets him apart in technically demanding projects.

✨ In this session, expect:
🔹 Real-world iOS development insights
🔹 Building production-ready mobile applications
🔹 Deep dives into native iOS tools and workflows
🔹 Career growth in mobile engineering
🔹 Open Q&A

📅 Date: Friday, February 27, 2026
⏰ Time: 8:00 PM / 2:00 LT
📍 Live on the GDG AAU Channel

Follow us for updates:
| Telegram  | LinkedIn  | Instagram | TikTok | Face Book | X

#GDGAAU #Openmicsession

Better hub 🔥

@sifendev

Working with WebSockets is finally starting to get fun.

@sifendev

Today was just a good dev day.

I’ve been using TypeScript in my Socket.IO project, and I finally took the time to properly type my server and client events. And wow… it changes everything. When you actually define the event types on both sides, TypeScript basically forces you to build things the right way. You can’t send random payloads anymore. You can’t misspell event names. You can’t “figure it out later.” It makes the whole system feel solid instead of fragile.

At first, I had the same event types copied in both the client and the server. Just duplicating them. Then I remembered wait… this is a monorepo. Why am I copying anything? So I created a shared package for common types and imported it in both apps. When I saw it working, with both sides using the exact same types from one place, I was genuinely so happy. Setting up the monorepo from scratch and seeing that structure come together felt so satisfying.

The other thing I was stuck on was error handling. With REST, you have status codes. With WebSockets, it’s just one open connection. No 200, no 500. I kept asking myself, how do I cleanly handle success and failure on the client? I tried a bunch of things, but what finally clicked was using acknowledgments. Passing a callback to emit(), and then having the server call it with a structured response. Once I created a proper Ack<T> type for success and error cases, everything started to make sense. The client can check ok and update state safely. Simple idea, but getting the types right was honestly tricky. I got some help from gpt.

@sifendev

I know most people probably don’t care about this stuff. It probably sounds like nonsense. But figuring it out, especially after being stuck for a bit, just felt really good. I was excited and wanted to share it.

@sifendev

Had some free time today and built a simple barebones Socket.IO chat app. Nothing fancy, just raw events. If you’re a beginner, you might learn a thing or two from it.

This isn’t the final boss tho. The real one is called GhostChat 👀. Starting it tomorrow. I’ll share more then.

Good night.

@sifendev

successfully convinced 4 devs to switch to Omarchy 😁

@sifendev

Happy women's day

@sifendev