Melusi Khumalo

@melusi-k

A coffee fiend.

Commit activity

13 commits in the last 30 days

longest streak 3 days

225 / 400 XP175 XP to maintainer

Pinned

Thu, Nov 12

One app-wide store for the data (household, tasks, sync), passed down through the environment. Per-screen state only for things that die with the screen: a draft, an open sheet, a filter. My test: if two screens need to see the same change instantly, it moves up. 💭
Today I decided what a Library should do when you can't remember what you saved: surface the quick stuff, the favourites, and what you've actually cooked before. Built only from your own recipes, so no fake trending feed. I think "cook it again" might be the most honest…
Small pilot plan, no big launch. A few real people, my own builds installed straight onto phones, one loop: save a recipe, cook it, come back for another. It's less glamorous than a store listing, but I get to see someone use it, and honestly that's the bit I want. 🥹 #IndieDev
Someone mentioned to watch where a person needs me to explain the next step, because hesitation tells you more than a happy reaction at the end. Annoyingly good. I'd been planning to ask people if they liked it. Now I'm planning to watch where they pause. 💡
Spent the day working through, what"done" means for my team. You start realising that merged code isn't a working app. Something can pass every check and still be wrong the second I hold it in my hand. So the real finish line is me, is something shipped and confirmed working.…

Wed, Nov 11

Scope is a feature. I keep a short list for what the app must do now and park the rest. Anyone got a good way to stay honest about that when building solo? 😶‍🌫️
Learning the hard way that tests should assert what the user wants, not how the code is wired. What's the one testing habit that saved you the most time? 💭
Hot take from building an app evenings and overnight: the best structure is whatever lets you ship one small, finished thing a day. Fewer branches, more finished. 🤌
SwiftUI lesson so far: the views are the easy part 😁. The real work is keeping navigation and state boring so the UI stays snappy. How do you handle it? 💭
Anyone else building a full iOS app in SwiftUI on a small team? Curious how you structure it. I'm keeping features in small slices that stack, then bundling them into a couple of PRs instead of a pile of open ones.

That's @melusi-k's root commit.