DEV Community: Rono

How this Game is won

Rono — Wed, 25 Mar 2026 20:49:40 +0000

A playbook from the greats

Most people think this game is about talent...it’s not, it’s about understanding how things actually move.

Let’s not dress it up.

This is a game.

Not a fair one.
Not a clean one.
But a game you can learn.

So forget the noise.

Let’s break it down.

First thing:

Nothing you see working today started from a good position.

Not the banks.
Not the deals.
Not the people you think had an advantage.

It started the same way every time:

Pressure.

Look at Mwai Kibaki.

He’s already inside the system. Smart. Respected.

Then he loses.

Twice.

That usually ends careers.

He doesn’t react the way people expect.

He doesn’t get louder.

He steps back.

Watches.

Waits.

Lesson one:
When you can’t force the outcome, control your position.

Timing beats effort when the system is bigger than you.

He understood that.

So when the window opened—he didn’t scramble.

He stepped in.

Now James Mwangi and Peter Munga.

They walk into something broken.

Not struggling—broken.

No capital. No trust. No momentum.

Everyone says: shut it down.

They ask a different question:

What’s actually missing?

Not money.

Access.

So they remove friction.

No minimum balance.
No intimidation.
Just access.

Lesson two:
Find the constraint. Remove it. Scale what opens up.

They didn’t build a better bank.

They built a bigger door.

Now Chris Kirubi.

He builds something real.

Then it collapses.

Not because he didn’t try.

Because he didn’t control the system around it.

Distribution blocked. Doors closed.

That’s when it clicks.

Lesson three:
If you don’t control movement, you don’t control outcome.

Product is not power.

Access is.

He adjusts.

Everything changes after that.

Then Gideon Muriuki.

He inherits failure.

Mess everywhere.

Most people try to grow out of problems.

He doesn’t.

He slows down.

Fixes structure.
Fixes people.
Fixes discipline.

Only then does he scale.

Lesson four:
Speed without structure kills you. Fix first. Then move fast.

Now Jimmy Wanjigi.

Different play.

He doesn’t start with assets.

He starts with insight:

The biggest opportunities sit behind government.

So he doesn’t build blindly.

He connects intentionally.

Lesson five:
In this game, access multiplies everything.

Ignore that, and you stay small.

Understand it, and things move faster.

Now zoom out.

Different people.

Different styles.

Same game.

Here’s the pattern:

1. Go where others aren’t paying attention
That’s where the opportunity hides.

2. Stay longer than feels comfortable
Most people leave right before things shift.

3. Change angle, not just effort
Pushing harder isn’t always the answer.

Positioning is.

4. Understand power, not just product
Execution matters.
But control decides scale.

5. Build structure before growth
A weak base doesn’t survive success.

6. Treat relationships as infrastructure
Not optional. Not extra.

Core.

7. Use failure as feedback
Not identity. Not a stopping point.

Just data.

That’s the playbook.

No hype.

No shortcuts.

Now the part people avoid:

This system isn’t designed to be fair.

It rewards awareness.

It rewards timing.

It rewards people who understand how things actually move—not how they should move.

So you decide.

Sit outside the system and complain.

Or step inside it and learn the rules.

And if you’re in the middle right now—

Things not working.
Plans not clicking.
Nothing moving the way you expected—

Good.

That’s where this starts.

You’re not late.

You’re early in the real process.

So don’t rush.

Don’t panic.

Just get sharper.

Where’s the real constraint?
Who controls movement?
What position are you building?
And are you staying long enough to catch the shift?

Now let’s go one level deeper.

Because this is where most people break.

The Rules You Don’t Get Taught

No one is coming to save you
Not systems.
Not luck.
Not perfect timing.

You can benefit from them.

But you can’t depend on them.

Build like it’s on you.

Think inward before outward
Blame is easy.

Control is harder.

Focus on what moves with you:

Skill.
Time.
Execution.

That’s your leverage.

Be selective with people
Some people drain you slowly.

Others sharpen you fast.

Choose carefully.

Distance is not disrespect. It’s strategy.

You will need a level of selfishness
You won’t grow if you’re constantly adjusting yourself to fit others.

There are moments you choose your path over approval.

That’s part of the cost.

Focus beats everything
Discipline gets you started.

Obsession keeps you going.

The people who win stay longer on the same problem.

They go deeper.

Results change how people treat you
Before results, you explain yourself.

After results, people explain you.

So build. Don’t argue.

If you don’t create value, your voice stays small
The world listens to output.

Not intention.

Not talk.

Become useful. Then visible.

Courage is staying when it’s uncomfortable
Fear will be there.

Doubt will be there.

That’s not the signal to leave.

It’s the signal you’re in the real part.

Use what you have
Your environment is not just a limitation.

It’s also an angle.

Find it. Use it.

Kill the scarcity mindset
If you think opportunities are rare, you hesitate.

If you hesitate, you miss them.

Train yourself to see more. Move faster.

Drop the anchors
Bad habits.
Wrong environments.
Time-wasting loops.

You don’t rise while holding everything.

Let things go.

That’s the layer most people avoid.

Not because it’s complex.

Because it demands change.

You don’t need perfect conditions.

You need clarity.

You need focus.

And you need time in the game.

That’s how this game is won.

When Ai runs your Workflow

Rono — Tue, 24 Feb 2026 18:03:41 +0000

What happens when your workspace thinks with you?
"One of the ways that I believe people express their appreciation to the rest of humanity is to make something wonderful and put it out there." — Steve Jobs
We built Daraja Workspace because we kept running into the same wall — and we suspected every team did too.
The brief is somewhere in the chat. The feedback is buried three threads down. The decision that took two hours to reach last Tuesday? Nobody can find it. Meanwhile the deadline is tomorrow, the client is waiting, and half the team is spending more time looking for context than actually doing the work. It's not a people problem. It's a workflow problem. And most tools aren't built to solve it — they're built to store things, not understand them.
That's the gap Daraja Workspace was built to close.

A workspace that keeps up with how teams actually work
Real teams don't work in neat, linear steps. A brief comes in, someone has a question, a thread goes sideways, a new idea surfaces, the scope shifts. By the time you're ready to execute, the important information is scattered across dozens of messages and nobody has a clean picture of where things stand.
Daraja Workspace is built around an AI — DarajaAI — that lives inside the workspace and pays attention to all of it. Not as a chatbot you have to prompt, but as a thinking layer running quietly underneath the work. When a new brief lands, it connects it to everything relevant that came before: the last campaign for that client, the feedback that never made it into the brief, the resource conversation from two weeks ago that everyone half-forgot. It keeps the full picture in view so your team doesn't have to.
When a deadline is approaching, it notices. When feedback in a long thread is contradicting itself, it surfaces the conflict and summarizes what was actually said. When a team member joins a project late, they don't have to scroll through weeks of chat to get up to speed — the workspace can bring them current in minutes.
None of this requires anyone to learn a new system or change how they naturally communicate. The team keeps working the way they work. The workspace gets smarter as they do.

Built for the people doing the actual work
One thing we were deliberate about: Daraja Workspace had to work for everyone on the team, not just the people who already have everything in their heads.
For a junior coming onto a project, that means getting context explained clearly — what the client expects, what's been tried before, what the team's shorthand actually means. For a senior managing multiple projects, it means being able to get a clean cross-project overview without having to dig for it. For the founder or team lead who steps away for a few hours, it means the workspace holds the thread so nothing important drops while they're gone.
The point isn't to automate the work. The creative instinct, the client relationship, the judgment call that turns a good campaign into a great one — those are human, and they should stay that way. What Daraja Workspace handles is the connective tissue: the tracking, the remembering, the surfacing of what matters right now. The mechanics that eat up time and mental energy without adding anything to the actual output.
When that friction goes away, something shifts. The team's attention goes back to the work itself. Conversations get sharper. Decisions get made faster because everyone already has the context they need. The energy that used to go into managing chaos goes into building something worth being proud of.

What we've learned building this
We've tested Daraja Workspace with real teams, on real briefs, under real deadline pressure. What surprised us wasn't how much the AI could do — it was how quickly teams stopped thinking of it as a tool and started treating it as part of the team.
Not because it's trying to be human. But because it's genuinely useful in the moments that matter: when a thread gets too long, when the context is getting lost, when someone new needs to get up to speed fast, when the team needs to move and nobody has time to call a meeting.
We've also learned that the best version of this isn't the AI doing more — it's the AI knowing when to step back. The workspace should feel like a calm, organized colleague, not an interruption. So we've been careful about what it surfaces and when, making sure it adds signal rather than noise.

Why we built this
There's a version of work that most teams glimpse occasionally — usually during the best projects, with the best teams — where everything just flows. Everyone knows what they're doing, information moves freely, decisions happen quickly, and the energy stays high from start to finish. It doesn't feel like chaos management. It feels like building something.
That version of work shouldn't be rare. It shouldn't depend on having the right people in the same room at the same time or a team lead who holds everything in their head. It should be the default.
Daraja Workspace is our attempt to make it the default. To take the things that make the best teams work well — shared context, clear communication, a sense of where everything stands — and build them into the workspace itself, so they don't disappear when the project gets complicated or the team gets busy.
We put it out there because we believe work can feel better than it usually does. And we think the right workspace is a big part of how you get there.

Daraja Workspace is built for teams that care about how they work, not just what they produce. If that's you, we'd love to show you what it looks like in practice.

Check out my app

Rono — Fri, 26 Dec 2025 07:20:41 +0000

Hey guys, this is the shortest article I'll probably ever write...

I've been juggling a crazy schedule lately—work, life, school, endless meetings—and got fed up with clunky calendars and scattered notes.

So I built Rucks an app that uses AI to smartly schedule your chaos, suggest optimal times, and make collaboration effortless.

It's simple, powerful, and actually helpful.

Check it out, try it free, and let me know what you think. Feedback welcome—I'm iterating fast!

Thanks for reading (all 100 words of it). 🚀

The unfair advantage your classmates already have

Rono — Sun, 07 Dec 2025 20:51:11 +0000

I’m not launching anything today. I just want every student in the US, South Africa ,Europe and Kenya who’s currently panicking about finals to know this exists.

Real stories from the last 48 hours (names removed because they begged me 😂):

→ Final-year BCom student at UCT dumped 400+ pages of Econ 301 + 302 slides + tutorial answers into Rucks this morning. Typed: “Generate all my macroeconomics questions and answers for revision.” 30 seconds later he had 127 exam-style questions with full model answers pulled straight from his own notes + past papers he uploaded last year. He’s revising right now instead of crying.

→ Riara University dude in Nairobi facing Microeconomics CAT tomorrow: “Bro just type ‘give me 50 multiple-choice questions on elasticity from my notes’” → Rucks scanned everything he ever saved, made the MCQs, gave the answers + page references. He sent me a voice note screaming.

→ UCLA kid grinding for Econ 101 final next week: Uploaded every lecture recording since September. Typed “create a 3-hour past-paper style exam with solutions from everything we’ve covered.” Rucks delivered a 25-question paper + marking scheme in under a minute.

This isn’t some future AI fantasy. This is live right now at rucks.cc and it costs $1.50 a week.

How it actually works for finals week:

You throw in everything — PDFs, lecture recordings, WhatsApp voice notes from group study, photos of whiteboard, past papers, whatever.

When you’re cooked and have zero time left, you just say stuff like:

“Generate 100 KCSE-level Biology questions from my Form 3 & 4 notes” “Make me a full Principles of Accounting mock exam with answers” “Give me every single definition + example we ever learned in Development Economics” “Turn my International Finance notes into Anki cards”

Rucks reads ONLY your stuff (100% private, nothing sent to OpenAI) and spits out perfect revision material instantly.

$1.50 a week. Cancel anytime. Works offline during loadshedding or when campus Wi-Fi dies.

If you’re in the USA, South Africa, Kenya, or anywhere else on Earth and you have finals coming, stop suffering.

Go to rucks.cc → sign up in 9 seconds → throw your notes in → type “generate all my [subject] questions and answers” and thank me later.

No upsells. No “launch discount.” Just the tool that’s already saving thousands of students right now.

Drop your country flag + the subject you’re currently scared of below. I’ll personally send the top 10 most panicked people a free month.

You’ve got this. Your notes have you covered. Rucks just makes them talk back.

rucks.cc

(like so someone who actually needs this sees it before their exam tomorrow ❤️)

10 Productivity Hacks to Boost Your Day with Rucks

Rono — Sun, 16 Nov 2025 07:31:05 +0000

10 Productivity Hacks to Boost Your Day with Rucks.cc

Are you tired of feeling overwhelmed and struggling to stay on top of your tasks? Do you wish there was a way to maximize your productivity and achieve a better work-life balance? Look no further than Rucks.cc, the AI-powered schedule and task manager that's here to revolutionize your daily routine.

In this article, we'll share 10 productivity hacks to boost your day with Rucks.cc. From prioritizing tasks with AI to reviewing and adjusting your schedule, these tips will help you get the most out of your day.

The Productivity Hacks

1. Prioritize with AI

Let Rucks.cc's AI-powered scheduling feature organize your tasks and schedule. By prioritizing your most important tasks, you'll ensure that you're focusing on what matters most.

Pro tip: Tag tasks with high, medium, or low — Rucks AI pushes deadlines automatically.

2. Task Bundling

Group similar tasks together to maximize your time. Whether it's checking emails or making phone calls, task bundling helps you stay focused and efficient.

Example: Bundle all admin tasks into a 30-minute "Power Hour" every morning.

3. Time Blocking

Schedule fixed, uninterrupted blocks of time for important tasks. This technique helps you stay focused and avoid distractions.

Rucks feature: Drag-and-drop blocks in desktop mode — perfect for deep work on laptops.

4. Break it Down

Divide big tasks into smaller, manageable chunks. By breaking down complex tasks, you'll make progress without feeling overwhelmed.

Rucks hack: Use the "Split Task" button — turns "Write 20-page report" into 5 micro-tasks.

5. Use the Eisenhower Matrix

Prioritize tasks based on urgency and importance. This decision-making tool helps you prioritize tasks into four quadrants:

Urgent & Important
Important but Not Urgent
Urgent but Not Important
Not Urgent or Important Rucks integration: Label tasks with quadrant tags — AI auto-sorts your day.

6. Schedule Self-Care

Make time for activities that recharge you. Whether it's exercise, meditation, or spending time with loved ones, self-care is essential for productivity.

Rucks reminder: Set "Recharge Block" — non-negotiable time that teammates can't override.

7. Avoid Multitasking

Focus on one task at a time for maximum productivity. Multitasking can decrease productivity and increase stress.

Rucks focus mode: Enable "Do Not Disturb" — hides notifications until your block ends.

8. Set Realistic Goals

Be realistic about what you can achieve in a day. Set achievable goals and prioritize your tasks accordingly.

Rucks AI: Suggests daily limits based on your past performance (e.g., "Max 6 high-energy tasks").

9. Use Reminders

Set reminders to stay on track and meet deadlines. Rucks.cc's reminder feature ensures that you never miss a deadline or important task.

Bonus: Get WhatsApp alerts at 7 AM — because email is for old people.

10. Review and Adjust

Regularly review your schedule and adjust as needed. By regularly reviewing your progress, you'll identify areas for improvement and optimize your productivity.

Rucks dashboard: Sunday 8 PM → 60-second review with "What Went Well / What to Fix".

Final Thoughts

By implementing these 10 productivity hacks with Rucks.cc, you'll be able to maximize your time and energy, prioritize tasks with ease, and achieve a better work-life balance.

Kenyan students, freelancers, and hustlers — this is your unfair advantage.

Get Started

Website: https://rucks.cc
Sign up in 3 seconds with Google
First 100 users get PRO free till Jan 2026

"Rucks turned my chaotic semester into a system. Group projects? Done in 48hrs." – Mercy, UoN

Tag a friend who needs this.

Let’s make 2026 the year of done > perfect.

productivity #ruckscc #softwaredevelopment #ai

Posted on November 16, 2025

Why the Economy Loves and Hates Lazy People

Rono — Fri, 08 Aug 2025 19:29:34 +0000

Laziness runs the world.
Not ambition, not innovation, not grit laziness. It’s the reason we invented the wheel, elevators, cars, computers, and now AI that can write your emails for you. Humans have always been looking for ways to do less while getting more.
And the modern economy? It’s built on that instinct. Everything around you from the coffee you ordered this morning to the phone in your pocket exists to make your life easier. Laziness isn’t just tolerated. It’s monetized.

But here’s the catch: while laziness makes the economy rich, it also threatens to kill it. This is why the economy loves you for being lazy… and hates you for the exact same reason.

Laziness = Profit
The economy thrives when people outsource their effort. Consumerism is basically the commercialization of “I don’t feel like it.”
Look around:

Amazon isn’t selling products; it’s selling not having to leave your house.
Netflix isn’t selling movies; it’s selling entertainment without effort.
Uber Eats isn’t selling food; it’s selling the 45 minutes you don’t spend cooking.
If you’re the type who will pay extra to save time or avoid hassle, you’re exactly who the market is designed for. You’re the dream customer quick to spend, loyal to convenience, and addicted to comfort.
This is why laziness is profitable. People who don’t want to build or make something themselves are willing to pay for it, and that money fuels entire industries.

The Hard Truth About Convenience
Here’s what we tend to forget: every convenience you enjoy is built on someone else’s hard work.
That app you open before bed? A developer spent months coding and debugging it.
That perfect cup of coffee? It came from a farmer who harvested beans, a roaster who perfected the flavor, and a delivery driver who got it to your door.
That next-day delivery from Amazon? Warehouses full of staff worked non-stop to make it happen.

The “lazy economy” sits on the shoulders of the “hard-working economy.” Without the builders, innovators, and risk-takers, there’s nothing to consume.

Why the Economy Hates Laziness Too
Here’s the flip side laziness on the supply side is poison.
If too many people stop creating, innovating, and putting in hard work, the pipeline of goods and services dries up. You can’t sell convenience if there’s nothing to make life convenient in the first place.

History proves this. Civilizations that became too comfortable, too dependent on the wealth of previous generations, eventually crumbled. When everyone’s consuming and no one’s creating, shortages hit, prices spike, and innovation stalls.

And in the long game, that kills economic growth.

The Balancing Act That Keeps the System Alive
The economy works because there’s a balance between:
Builders people putting in the grind to create new value.
Consumers people spending money to enjoy that value.
If the balance tips too far in either direction, the system breaks.
All builders, no consumers? Production outpaces demand.
All consumers, no builders? There’s nothing left to sell.
The modern economy survives by keeping just enough hard-working creators to feed just enough lazy consumers.
The New Face of Laziness
In 2025, laziness doesn’t always look like lying on the couch all day. Sometimes it’s hidden behind technology. AI, automation, and delivery services make us feel productive while we’re actually avoiding effort.
Yes, tools like ChatGPT or the Mac M4 make life faster and more efficient but they also remove the struggle that once built skills and discipline. The danger isn’t using these tools; it’s letting them do all the thinking for us.

We’re entering a stage where laziness is dressed up as efficiency. And the economy will keep selling it back to us until there aren’t enough real builders left to keep the cycle going.

Where You Stand
Here’s the uncomfortable question: are you a builder or just a consumer?
If you’re building, you’re on the side that keeps the economy alive. You’re creating value, solving problems, and giving people something to pay for.
If you’re just consuming, you’re living off the effort of builders and the economy loves you for your money but hates you for not contributing to its future.

The truth is, most of us are a mix of both. We work hard in some areas, but happily hand over our money to avoid effort in others. The problem comes when the balance in your own life tilts too far toward consumption.

Final Word
Laziness fuels spending. Hard work fuels creation. The economy needs both, but it will always respect the builders more even if it doesn’t say it out loud.
The economy doesn’t care about your feelings. It only cares whether you’re making it money or making it possible.

Why I'm Building a Custom DNS Responder for Embedded Devices

Rono — Sun, 20 Jul 2025 16:11:57 +0000

When working with MicroPython on small microcontrollers like the ESP8266 or ESP32, you quickly hit a wall if you try to do anything with DNS—especially mDNS (multicast DNS). I found out the hard way while building a Bluetooth beacon-powered app that needed to talk to a local server on the same network.

The Problem with micropython-mdns

There’s a package on PyPI called micropython-mdns, but don’t be fooled—this isn’t something that runs on your device. It’s a build utility meant for working with MicroPython code on your desktop. Trying to mip.install("mdns") doesn’t work, and even if you manage to hack something together, you'll face:

Incomplete installs
Memory constraints
Missing socket support
Vague or outdated documentation
In short, DNS support on MicroPython is a mess.

Why This Matters

Many modern apps, especially in IoT or edge scenarios, rely on some form of local device discovery. Whether you’re running a simple HTTP server on your ESP or trying to expose endpoints dynamically, DNS or mDNS is the typical go-to.

But for small micros, this just isn't an option today—not without going native (C/C++) or using an external helper.

My Approach

For now, I’ve pivoted to using dummy data just to prove my app’s concept. The ESP was only acting as a local server—I could use my laptop instead, but I want this system to be portable, low-power, and eventually headless.

That’s why I’ve decided to build my own DNS responder written in C or Rust—tailored for use in embedded projects. It will:

Be lightweight and memory-safe
Run on small MCUs
Support basic A record responses and mDNS
Help other devs avoid the same rabbit hole
Conclusion

This isn’t just a personal fix, it’s something the MicroPython community sorely needs. Reliable, plug-and-play DNS discovery for embedded devices is long overdue. If you’ve been burned trying to get DNS working on a tiny board, stay tuned.

I’ll open-source the DNS tool and write a follow-up on how it works internally once it's ready.

— Kiprono

Making the Future Cool: Lessons from BASiGo’s Bold Move

Rono — Tue, 15 Jul 2025 12:35:28 +0000

The future is not just something that happens. The future is something we must imagine, design, and build.

There’s something deeply unsettling about how we’ve come to accept the world around us. We move through broken pavements, cross potholed roads, dodge open drainage trenches, and wait for water that never runs. And somehow, we call that “normal.”

But here’s the thing: this isn’t normal. It’s just stagnation dressed up as survival.

Our infrastructure is tired. The way we build, move, and live was designed for a time long gone. Our roads weren’t meant for modern logistics. Our homes—built with materials and methods that barely evolved—aren’t optimized for durability, affordability, or sustainability. Drainage systems? Half of them don’t even qualify for the word “system.” Clean water access? Still a luxury for too many.

The solution isn’t waiting for the government to fix things. It’s to build companies that fix them.

We need a wave of innovation not in the clouds, but on the ground—focused on the very basics of daily life.

Why not rethink how walking paths are built and maintained?
Why are we still stuck with outdated road construction materials?
Why do we build houses the same way we did 50 years ago—expensively, inefficiently, and unsustainably?
Why hasn’t someone disrupted how drainage works, or how we collect, purify, and distribute clean water?
The answers aren’t in speeches. They’re in startups.

Take BasiGo. A few years ago, the idea of an electric bus on Nairobi roads sounded like science fiction. Today, BasiGo is quietly reshaping public transport—not just by making it cleaner, but by challenging the assumptions that have kept it broken for decades. This is what innovation actually looks like. Not theory. Not hope. Execution.

So the question is:

What other parts of our infrastructure are waiting for a BasiGo moment?
Our public transport, our housing, our water, our urban design, our construction materials—all of it is ripe for a second look. A smarter take. A better version. But it won’t come from maintaining the status quo. It won’t come from boardrooms or ministries.

In fact, the best thing the government can do right now is to step aside—not because we don’t need them, but because we don’t need them to build. What we need is an environment that rewards risk, protects builders, opens doors, and keeps the red tape away from those solving real problems.

Progress won’t come from policies.
It’ll come from bold builders willing to say: this isn’t good enough. Let’s fix it.

We don’t need to settle for what we have.
We need to question it, redesign it, and rebuild it—smarter, cleaner, cheaper, faster.

The future won’t get better on its own.

It will only get better if we build it.

I'm About to Ship My First EdTech-Focused App 🚀

Rono — Sun, 18 May 2025 06:14:28 +0000

Hi everyone 👋,

After months of coffee-fueled nights, hallway feedback, and testing between classes, I’m thrilled (and nervous) to say—I’m about to ship my very first EdTech-focused app: Rucks.

🎒 What Is Rucks?
Rucks is a student productivity and learning companion built for students, by a student. I created it because I was constantly overwhelmed by:

Missed deadlines

Endless WhatsApp groups

A lack of focus-friendly tools tailored to how we actually study

So I asked: What if there was a quieter, more intentional space just for students?
That’s what Rucks is—a lightweight app to track your learning, plan your days, and improve how you manage school.

✨ Key Features
Here’s what’s shipping in Version 1.0:

📅 A distraction-free calendar with daily learning goals

🧠 A smart reflection tracker to see how you’re growing

📊 Powered by MxAnalytica, a custom-built analytics engine that learns from your usage (without Google)

🌗 Dark/light mode support with smooth transitions

💬 “New Message” screen to keep feedback flowing

📸 [Insert image/gif of a user creating a task or reflecting on their day]

🛠️ Built with Flutter, Supabase, Dart Frog, and a pinch of Clean Architecture.

💭 Why I Built It
I didn’t build Rucks in a lab—I built it in class, in transit, in the in-betweens.
Like many students, I wanted a better system but didn’t want the complexity of Notion or the chaos of WhatsApp.

Also, I wanted to build something that didn't just collect data—but used it to make students better.

🚀 What's Next?
I’ll be rolling it out to a small test group of students in my class

Gathering feedback, fixing bugs, and listening closely

Long-term? I hope Rucks becomes a community of learners helping each other get better.

📸 [Insert roadmap image or feature sneak peek here]

💡 Tech Stack
Frontend: Flutter

Backend: Supabase & Dart Frog

State Management: BLoC

Database: Drift

Analytics: My custom tool—MxAnalytica

Hosting: GCP/AWS (final decision coming soon)

If you're a Flutter dev, I'd love to hear your thoughts or ideas for improving the structure.

📣 Where You Come In
If you’ve ever built something and hesitated to launch—you’re not alone.
This post is part celebration, part encouragement, and part call to action:

🙌 I’d love feedback

🐞 Spot bugs? Tell me

🧠 Got feature ideas? Let’s talk

🫶 Want to support Rucks? Share it with a student!

📍 Where I’ll Showcase Rucks
If you’re also launching or building something, here are a few places I plan to share Rucks:

📸 ProductHunt (Coming Soon) – Launch day post

💬 Reddit – r/EdTech / r/FlutterDev

🧑‍💻 GitHub Showcase

🎓 Campus noticeboards + WhatsApp groups

🐦 Twitter/X (@ronov11725 if you have one)

🙏 Final Thoughts
Shipping something is hard. Shipping something meaningful is even harder.
But if you’re reading this and working on something—don’t stop. Keep building, keep learning, keep shipping.

Thanks for reading—and thank you in advance if you check out Rucks.

Stay curious,
Kiprono Ngetich
Maker of Rucks
ronov9000@gmail.com
GitHub: Rono0365

🚀 Introducing Rucks: A Student-Built App to Help Students Stay on Track

Rono — Sat, 17 May 2025 08:38:38 +0000

Dear Dev Community,

Between classes, late-night coding, and the occasional existential crisis, I realized something: school can be overwhelming.

There’s always a deadline, always a distraction, and platforms like WhatsApp or Telegram—while useful—aren’t really designed for focused learning. So instead of just complaining about it, I decided to build something.

🎓 Meet Rucks.
A tool by a student, for students—to help us plan, learn, and grow without the noise.

🧠 The Problem
As a university student juggling projects, classes, and personal goals, I found it hard to keep everything in sync. Most apps felt too bloated or too generic. I didn’t want another productivity app that treated me like a corporate employee.

I wanted something that understood student life. So I built it.

✨ What is Rucks?
Rucks is a minimalist, distraction-free space to help students:

Plan their days and assignments

Track learning goals

Reflect and improve

Stay motivated without social media noise

It’s simple, focused, and built around real academic pain points.

It also integrates MxAnalytica, a small analytics engine I built to help improve the experience based on real usage—not assumptions.

🔧 Tech Stack
Frontend: Flutter (for a clean, cross-platform UI)

Backend: Dart Frog + Drift for lightweight local storage

Analytics: MxAnalytica (custom engine)

No Google services — I wanted to build something privacy-respecting and independent

📦 Why I Built It This Way
Rucks wasn’t made in a lab or during a hackathon. It was built:

"Between classes, coffee sips, and the occasional existential crisis."

Every design choice was guided by real needs and actual friction points I (and my peers) experience as students.

🔍 What’s Next?
Right now, Rucks is in version 1.0. I’m testing it with a small group of classmates, collecting feedback, and iterating fast.

I'm also exploring ways to monetize it without compromising the experience. If you’ve built something similar or have thoughts on that, I’d love to hear from you.

🧑‍💻 Call for Feedback & Collab
If you're a student, an indie dev, or someone who just gets what it means to feel overwhelmed in school—I’d love your feedback.

Got ideas? Want to test it out? Just curious?
Shoot me a message or comment below.
You can also reach me at: ronov9000@gmail.com

Let’s build better tools for learning—together.

—

Thanks for reading,
Kiprono Ngetich (Rono)
GitHub: @rono0365

I built my first app entirely on google's project idx

Rono — Sat, 25 May 2024 09:50:36 +0000

I built my first app entirely on Google’s Project IDX!

Here are my key takeaways:

1/ ⚡ Speedy Development: The development process is impressively fast with a good internet connection. Definitely a game changer!

2/ ⚙️ Configuration Challenges: When adding an existing project, IDX should automatically configure system settings. For example, running dart --fix or adjusting Java versions was a bit cumbersome and took me 2 hours to sort out.

3/ 📱 Android Emulator Limitations: The provided x86 Android emulators struggle with building apps for release. Plus, I faced issues downloading the APK to my computer.

Overall, Project IDX is a promising tool with a few areas for improvement. Excited to see where it goes! 🚀

here's a link to the video i posted it on twitter/X :
here's the video

lo

Rono — Sat, 11 May 2024 06:09:21 +0000

lo and behold , i have arrived