Rust on Janusworx

Make a Ruckus: 001, Done! Or Are We? Thank you, Dave!

feedback@janusworx.com (Mario Jason Braganza) — Sat, 20 Sep 2025 13:39:01 +0530

Cute wolf Mabel, who caused quite a Ruckus, courtesy David Beazley

I had started this series, to catalogue my journey learning Rust whilst doing David Beazley’s, Ruckus course.
And just like that, it’s over! 😂 The course is done, and I am already missing Dave and my fellow journey folk, Rodica, Yadu, Marko, Upul, Gabriela, and Eugene!
I never thought the end would be so bittersweet.

Worth it financially?
#

Yes! Oh, dear God, yes!
To begin with, I never thought that Dave’s courses were expensive. Yes, they cost money, but he’s given so much away for free, that I was willing to save up and put my money where my mouth was.
I also think, I’ve figured out Dave’s schtick with the idea of what he teaches.
Take something, something hard, (Write a compiler? Figure out distributed consensus in networked systems? The big ideas and paradigms in computing?); something that would take an average Joe, 4-6 months (or a college semester) to learn, and then compress it down to anything from a couple of days to a work week. Compress the time that is … not the knowledge.
Having that much knowledge dowloaded into your head in that short a time frame, is what (to use a Dave-ism) makes your brain explode.
And now having actually done it, I’m now swinging around to the price is just right or “He actually undercharges a bit” camp.
This is bloody addicting. I’m just going to save up and do them all as and when I can over time. Like Neo answering Tank’s, “How about some more?”, with a Hell yes!

Worth it for the knowledge I gained?
#

Have I already said, Oh, dear God, Yes?! Doubly so, here!
Learning it myself, I realised that Rust had paradigms, teasing me at the edge of my vision, which I couldn’t quite see, frustrating my attempts to learn the language.
Python (C/OOP) is my ur-language. Having that, made it easy to learn Go. Rust turned out to be a different beast altogether. Having the big ideas of Rust laid bare and then explained thoroughly was therefore, such an eye opening experience. And I learned it while doing something else, that is inherently hard. Dave makes it easy though, like I describe below.

I just wanted to learn Rust. I didn’t really want to write a small programming language.
But doing that, made me learn Rust without even realising it. He’s that good. The pedagogical method is that good.
Most big ideas were in there. Ownership and borrowing, check. Compare and contrast how things are done in other languages, double check. Macro magic, check and triple check.
The course was more focussed on the why of Rust, more than the more easily discoverable, how.
A fascinating mental model was looking at Rust like Earth. An inner strict core, surrounded by a more relaxed, friendlier outer shell.

Daily work was tremendously, mentally taxing. In a good way.
Dave keeps saying that minds explode due to the material. But no good Sir, that is not true!
To Dave I say, “’Tis thou, Dave, who dost cause the explosions of brains!”
He starts with an innocent problem, something seemingly innocuous, and then lays his trap.
Simple solutions are shown not to work, teensy yet ghastly exceptions show up to trip you, dreadful scenarios that you’d never imagine, lie beneath the surface. And your mind gets wound up so tight, that when Dave finally has had his fun, takes pity on us and shows us the solution, it naturally goes, Boom!

I cannot wait, to have my brains exploded once again :)

Am I done with this series?
#

No.
I jumped into the deep end of the pool, by attempting to learn Rust with a hard project at the same time.
So while I’ve learned a lot, there’s plenty of work to do.
While the others could do their programming exercises quickly, I have seriously lagged behind.
With the notes I’ve made and the resources that I have access to, I will attempt to redo this week myself over the coming months and write about it, and ponder, struggle, work through it here.

Dave as teacher and all round good egg
#

The man puts in tremendous amounts of work.
Every bit of the course, is planned and structured meticulously and then he just riffs off of the ideas.
There was a collaborative Github repo ready and waiting, there were video recordings ready as soon as the day was done.
Dave never pretends to have all the answers. 99% of the time, he does and hides it well, so we do the thinking, but the few times he didn’t, he let us know and then came back to us with answers and thoughts either in the next session or the next day.
Unfailingly polite, kind and generous to a fault, he fostered an extremely collaborative environment, in which, even when there were other folks much more learned and experienced than I; I never felt like a dunce. I never felt spoken down to.
All my kooky ideas were evaluated, and then Dave would point out why doing something like what I suggested wouldn’t quite work or why stuff would crash and burn or why what I suggested doing eeny, meeny, miny, moe was in fact, pretty good.
I learned not just what, not just how, but also why.
And I learned it all in a place that was nice, and friendly, and warm, and kind.

Dave, thank you for all you do! I’m very grateful!

Feedback on this post?
Mail me at feedback at this domain or [continue the discourse here][2].

P.S. Subscribe to my mailing list!
Forward these posts and letters to your friends and get them to subscribe!

Make a Ruckus: 000, The Motivation

feedback@janusworx.com (Mario Jason Braganza) — Thu, 11 Sep 2025 13:47:52 +0530

Wolf howl, by Lorc, CC BY 3.0, via Wikimedia Commons

I signed up for the latest cohort of David Beazley’s, Ruckus.
The basic idea, behind Ruckus is to write a small interpreter in Rust!

Why?
#

From the Ruckus page:

This course tackles Rust by stepping back and thinking about it from the standpoint of a “programming languages” project. If Rust is really so different, how would you go about finding out how? Suffice to say, building a programming language will cut right to the heart of the matter.

This is exactly how I learned Python. Only it took me an inordinately long time. And I didn’t even realise that I was doing it that way. While most of my friends were happy just using Python, I could not quite do it right, because I had no fundamentals¹, and since my background has been tech support, hardware and people management, I needed to unlearn a ton of stuff.

I’m cautiously hoping Ruckus will help me do the same with Rust, only in a turbo charged manner.

Rust fascinates me. And I quite like my journey to its doorstep.
I learned writing for myself with Python. But when it came time to sharing my tiny projects with friends and family, I was a bit stumped.
I learned Go, just so I could give them a binary and then instruct them with a “just run this.”
And while that solved my distribution problem, Go’s type system made me realise, just how well suited a typed language is for collaboration.
Which brings me to Rust. Long term, this is the language², I would love to write for performant code, because Rust’s big picture features (safe, performant, easy to distribute) are exactly what I want for all my tiny bits and bobs.

Which in turn brings me back to Ruckus.
Getting a teensy peek at how everything works underneath, while at the same time, getting a firm handle on the language seems like a fun challenge.
I also wanted to try what Cal Newport, calls a grand gesture in Deep Work:

The concept is simple: By leveraging a radical change to your normal environment, coupled perhaps with a significant investment of effort or money, all dedicated toward supporting a deep work task, you increase the perceived importance of the task. This boost in importance reduces your mind’s instinct to procrastinate and delivers an injection of motivation and energy.
[…] The dominant force is the psychology of committing so seriously to the task at hand. To put yourself in an exotic location to focus on a writing project, or to take a week off from work just to think, or to lock yourself in a hotel room until you complete an important invention: These gestures push your deep goal to a level of mental priority that helps unlock the needed mental resources. Sometimes to go deep, you must first go big.

Make no mistake, my current state is that of an enthusiastic, ignorant newbie. How hard can it be? I’m woefully unprepared for what might come. The only thing I know, is that I don’t know. I fully expect to be like the wolf above, losing my mind, howling at the moon and generally creating a ruckus.

Feedback on this post?
Mail me at feedback at this domain or continue the discourse here.

P.S. Subscribe to my mailing list!
Forward these posts and letters to your friends and get them to subscribe!

I have some now ↩︎
I thought I could be pragmatic about the giant that stewards Go, but I realise that it’s something that’ll always stick in my craw. I have no issues using it with other folks or in a collaborative project. I just don’t want to use it for myself and my projects. ↩︎

Doing Devops, Dropping Rust

feedback@janusworx.com (Mario Jason Braganza) — Fri, 07 Jun 2024 16:37:50 +0530

Been struggling to do it all over the past few months.
But no! Life says no :)

So I’m building some margin into my life.
And the only thing I can talk about work wise, is the familiarity I am trying to gain as part of the career pivot.
The Devops Stuff.
The only thing that is career adjacent to all the stuff I did as a sysadmin and then consultant. So hopefully lots of boring stuff about exciting tech as I try to build new mental models, to fit over old ones.

Problem though, is what do I write?
I don’t have a good spin on most computer devops stuff. I don’t know what to say.
So for now, they probably will be, just like I point above, boring progress logs.
Mostly consistent, to give me accountability.
And hopefully, I’ll find a voice.

On the personal front, books, reading, art, language, poetry, photography and other posts will continue. Those are what make my soul sing :)

Feedback on this post? Mail me at feedback at this domain

P.S. Subscribe to my mailing list!
Forward these posts and letters to your friends and get them to subscribe!
P.P.S. Feed my insatiable reading habit.

Rust on Janusworx

Make a Ruckus: 001, Done! Or Are We? Thank you, Dave!

Worth it financially? #

Worth it for the knowledge I gained? #

Am I done with this series? #

Dave as teacher and all round good egg #