Mahmoud

Builder, Tech lead, Self-hosting fan. 💻 📹

🤜🏼 Open Source

[Mahmoud @MightyMoud]

@dreamsofcode_io Very interesting and cool project you go there. Good stuff man

[Mahmoud @MightyMoud]

Nothing but magic. LLMs are magic! Probable magic

[Mahmoud @MightyMoud]

A mind forever voyaging in an endless sees of thought alone...

[Mahmoud @MightyMoud]

I recently stopped paying for premium, but I would definitely pay to get shorts gone forever...

[Riley Brown @rileybrown]

Hey @YouTube I would pay an extra $10/month on top of YouTube Premium to disable shorts.

I don't want to see another short ever again. Please let me toggle them off.

[Mahmoud @MightyMoud]

Oh my god learning a TON from just chatting with Claude in Ask mode... Love it!!

[Mahmoud @MightyMoud]

I'm sick of YouTube being full of people reading out and discussing drama and breaking down news instead of actually useful content...

[Abhishek Singh @0xlelouch_]

Go has become my default / go-to language.

1. It’s great for backend and distributed systems
Networking, concurrency, and services feel first-class. Writing servers, workers, and infra code is exactly what Go was designed for.

2. It’s boring in the best way
Few language features, clear semantics, predictable behavior. You spend time solving the problem, not fighting the language.

3. Concurrency just works
Goroutines and channels make parallelism readable and practical, not an academic exercise. You can reason about load, throughput, and failure.

4. Performance without ceremony
Fast enough for most systems, low memory overhead, no GC horror stories if you design sanely. No need to drop into C for 95% of use cases.

5. One binary, zero drama
Static binaries, easy cross-compilation, simple deployment. SCP it, run it, done.

6. Tooling is unmatched
go fmt, go test, go vet, go mod — all built in. No yak shaving, no toolchain chaos.

7. Testing is straightforward
Table-driven tests, standard library support, fast feedback loops. Writing tests feels natural, not forced.

8. Ecosystem fits real systems
Kubernetes, Docker, Terraform, Prometheus — the tools running production are written in Go. Learning Go aligns you with how infra actually works.

9. Easy to integrate everywhere
HTTP, gRPC, protobufs, CLIs, cron jobs, workers — Go fits cleanly into almost any system boundary.

10. It stays out of your way
You don’t “love” Go. You trust it. And that’s exactly what you want for systems that need to run at 3am without surprises.

[Mahmoud @MightyMoud]

@vascoabm Hopes and dreams my friend, hopes and dreams!

[Mahmoud @MightyMoud]

The terminal can be beautiful!

[Mahmoud @MightyMoud]

@__morse @msmps_ @thdxr Also just on the same topic, there is this main feature of openTUI to basically render layers and modals that I wanted. It doesn't exit in bubbletea V1. V2 is still pre-release... I tried to get V2 to work and was painful.
Claude made me the same system in 20mins!

[Mahmoud @MightyMoud]

Hey @thdxr why is the go package of the OpenTUI no maintained? https://t.co/wkPMIkhcFU

[Mahmoud @MightyMoud]

@__morse @msmps_ @thdxr Yeah I think maybe we can build on top of the Zig part to port that engine to other langs? Not sure what's the best approach here. But I think maybe starting with the node side won't be optimal

[Mahmoud @MightyMoud]

Ah man OpenTUI is much clearer than Bubbletea.... Sigh...

[Mahmoud @MightyMoud]

@msmps_ @thdxr Cool thanks for clarifying

[Mahmoud @MightyMoud]

Reading Dagger docs I’m like dude wtf are you talking about!! 😆

[Mahmoud @MightyMoud]

@orhundev Dude your work has been very inspiring for me. Thanks for all you do

[Mahmoud @MightyMoud]

@romainlanz Boringnode is shaping up well Please keep going

[Mahmoud @MightyMoud]

If you don't know how to use these tools now it's you not them... That wasn't true a year ago. It is now

[Ben Awad @benawad]

Software Engineering Expectations for 2026

- The majority of your code should be written by AI now
- Cursor/Codex/Claude Code/Gemini/etc
- You should try all the tooling and switch between them, as each one gets an edge over the others depending on the release cycle.
- You should be using AI to check the code that is written by AI
- Have AI write tests
- Have AI read logs
- Have AI navigate your browser
- I don't do this every time because sometimes it's simple enough to check it myself
- You should still skim code changes
- This can be a lighter skim on internal tools and a heavier read through on customer facing code
- Use AI to help you define specs

[Mahmoud @MightyMoud]

This tweet has me extremely excited! It's a new dawn people. Nothing will be same now....

[Lee Robinson @leerob]

I built a Rust-based image compressor, WASM binary, and SvelteKit app!

I wanted to see how far I could go using only coding agents.

I did not write any code by hand.

After 520 agents, 350M tokens, and $287 I can now say… extremely far.

https://t.co/yxFL20j0PF

[Mahmoud @MightyMoud]

OpenTUI is really good. Very inspiring. Loving the terminal more and more