Hammad | Building u-Sage

DevOps Engineer, building a book reader for language learners.
Sharing Kubernetes, system design, and the messy path from idea to users.

[Hammad | Building u-Sage @mhammadsaani]

I’m building uSage, an offline-friendly EPUB reader for language learners. Tap any word or select a passage to define, translate, or explain it using your own prompt. Save new vocabulary and remember it with spaced repetition. I’m looking for beta readers. Demo of v1

[Hammad | Building u-Sage @mhammadsaani]

@faizannriaz Shifa 😂

[Hammad | Building u-Sage @mhammadsaani]

@awsdevelopers No servers

[Hammad | Building u-Sage @mhammadsaani]

@attacomsian Will check it out, as I am about to launch my first product

[Hammad | Building u-Sage @mhammadsaani]

Drop your startup URL ,

Let’s see what you’re building :-)

[Hammad | Building u-Sage @mhammadsaani]

@shirshakchavan Saying, "X" is weird

[Hammad | Building u-Sage @mhammadsaani]

@mohit_nagaraj Yep, unified memory is an interesting piece of engineering

[Hammad | Building u-Sage @mhammadsaani]

M1 Max Architecture: It used a concept of unified memory, memory used by CPU and GPU both. Usually, GPU has its separate memory unit called vRAM.

[Hammad | Building u-Sage @mhammadsaani]

@mikeydsoftware Yep, Macs are too fast. Sometimes, I think what if we put Ubuntu in Mac 😂

[Ashok Swain @ashoswai]

Gaza - If this is not genocide, what is it then?

[Hammad | Building u-Sage @mhammadsaani]

Last 7 Days, https://t.co/LQVm4uJ8SM, stats :-). Mostly, from twitter

[Hammad | Building u-Sage @mhammadsaani]

I say this to my beta testers,
- Download
- Test
- Troll

[Hammad | Building u-Sage @mhammadsaani]

@heyitsgeorg @GregoryMcKeown Sure, let's connect

[Hammad | Building u-Sage @mhammadsaani]

@heyitsgeorg @GregoryMcKeown Interesting approach, will try this out.

[Hammad | Building u-Sage @mhammadsaani]

@gracecamille_ What's the one idea you have liked in this book, you wanna share?

[K Srinivas Rao @sriniously]

Having tried the both extremes of the sides, "read all your code" vs "go full yolo", a PRACTICAL middle ground which has worked well for me so far.

1. Write your prose. That includes README files, code comments, PR titles and descriptions and commit messages. ADRs tend to be long and can get benefitted from MD syntax, so you can take help from models here. But everything else is non negotiable.

2. LOOK at the code.

3. Read the docs of all the languages and libraries you use. Not strictly before using them, but soon, ideally within a few weeks.

4. On any day, you should be able to explain any system or subsystem or sub sub system of your codebase to anyone.

Do that and you'll do just fine.

[Hammad | Building u-Sage @mhammadsaani]

@sriniously Welcome back...

[Hammad | Building u-Sage @mhammadsaani]

@Ranktokenlol ;-)

[Hammad | Building u-Sage @mhammadsaani]

@Its_lakshya_ai Linux, make it a server...

[Hammad | Building u-Sage @mhammadsaani]

@chanduuu_cs Uninstall every Sunday,
Install on Friday Night/Saturday Morning

[Hammad | Building u-Sage @mhammadsaani]

@chanduuu_cs Claude