1. Download the Loop app from the Google Play Store.
2. Create/register your Loop account.
3. Enter/use my invite code: MARTIN4774
4. Complete your profile/KYC requirements.
5. Only after your profile is fully completed is the registration considered successful and eligible for the KSh 150 reward.

1. Choose your country from the list.
2. Submit your request.
3. I process the request.
4. You receive further instructions and details.

1. Download Uber Eats from the official app store.
2. Create your Uber Eats account using your genuine details.
3. Complete any verification Uber Eats requests.
4. Wait for the relevant promotion to appear in your notifications/promotions area.
5. Return to Sharp and tap "I've Done Uber Eats" to send your confirmation to Pantane.

1. Download the Absa app from Google Play.
2. Sign up.
3. Enter referral code: OFC0PEZBQF
4. Complete the required KYC verification.
5. Open Complete Profile and finish the required information.
6. Check the account for the applicable reward.
7. Referral participants can qualify for the stated referral reward according to the promotion terms.

Moved journal posts out of journal.ts into a plain journal.json, keeping all the existing frontend logic untouched.

Reduced the site's font size site-wide for a tighter, more readable feel.

Added GitHub Sponsors support — a heart icon in the nav next to GitHub, LinkedIn, and Twitter, plus a native Sponsor button on the repo itself via .github/FUNDING.yml.

Fixed a bug on the Projects page where repos would intermittently fail to load. Moved the GitHub API call from the browser to the backend with a 10-minute cache, which avoids rate limits and stops a token from ever being exposed client-side.

The goal is simple: once a payment clears, the whole handoff — unlocking the contact, notifying both sides, and logging the transaction — should happen without anyone needing to check a dashboard.

Most of the day went into mapping the event flow and deciding where automation should live versus where a human check still makes sense. Small, unglamorous work, but it's the kind that makes a product feel reliable.

This stage of a project is less exciting than the first build but just as important — hardening the auth flow, tightening database constraints, and making sure the app behaves predictably when real people are using it daily rather than just during testing.

It's a good reminder that 'done' and 'production-ready' are two different milestones.

AttendBT relies on nearby-device detection to mark attendance automatically, which sounds straightforward until you hit the real-world inconsistencies between how different devices advertise and scan for BLE signals.

Today's win: a clearer mental model of how to keep detection reliable without draining battery life. Writing it down now so future-me doesn't have to relearn it.

It's rarely about needing every advanced feature on day one. It's about not having to migrate later when a project that started as 'just an MVP' turns into something a client depends on.

Relational integrity, solid JSON support when I need flexibility, and the ecosystem around tools like Supabase make it an easy default rather than a decision I have to keep re-making per project.

If you're building for the Kenyan market and need STK push, payment confirmation handling, or a paywall-style unlock flow done properly — webhook verification, retries, and all — this is a service I offer directly.

No invented pricing here — every engagement starts with understanding what you're building and scoping it from there.

The platform started as a handful of quick converters and has grown into something I reach for regularly in my own workflow — which is the best sign that it's worth continuing to build on.

Going forward, this is where you'll find real updates on projects I'm shipping, things I'm learning, services I offer, and the occasional longer write-up — without it disappearing into a feed after 24 hours.

Thanks for following along.

It usually starts with mapping the data model, deciding on auth and access boundaries early, and setting up a deployment pipeline before the UI exists — it saves a lot of rework later.

It's not the most visible part of the work, but it's the part that determines how smoothly everything after it goes.

That includes thinking about local payment methods, slower network conditions, and mobile-first usage from the start rather than as an afterthought.

If you have an idea for a site or web app and want it built properly, this is one of the core services I offer.

The frontend is a React/Vite/TypeScript app talking to an Express backend — kept intentionally simple so the focus stays on getting the assistant experience right before adding more surface area.

Still early days, but it's a good example of the kind of AI-and-automation work I enjoy building.