The Speciality Coffee Rabbit Hole

I moved to Goa sometime in late 2020, and the only habit of mine which I struggled to carry onwards from Bangalore was coffee. I was (and still am) a bit of a kitchen nerd.

Decent coffee was something I usually took for granted in Bangalore, where you had tiny mom & pop coffee roasters selling you either plantation or peaberry arabica beans, which you could either buy whole or buy ground to whatever size you wanted – with the option of pre-blending some chicory into your coffee.

You would eventually form friendships with these roasters, and have a steady supply of fresh beans to crush with a cheap ceramic conical burr grinder, and brew into a nice concentrate with the South Indian Filter. Brewing coffee at home was part of my morning routine, and buying beans locally about once every 2-3 weeks was one of the small joys of everyday existence (in a pre-pandemic world, ofcourse).

Arriving in Goa, it became apparent that I couldn’t source coffee beans of the same quality I could in Bangalore. Moreover, my trusty tiny South Indian Filter was starting to crack in a few places, and I wanted something nicer to brew with.

I decided to start experimenting with relatively fancier equipment and coffees. I bought myself a bright red plastic 02 sized Hario V60, which came along with paper filters, a ~700ml conical glass carafe, and a measuring spoon. I found a couple of companies that shipped adequate quality beans online, and zeroed in on Devan’s.

About 4 months after I moved to Goa, I met Moxxie. We became acquaintances at first, awkward friends next, and within a few months, a romance blossomed, and we grew into becoming a steady old fashioned couple. Moxxie was something of a tea nerd, and I a coffee nerd. Moxxie’s impression of coffee at that time was a harsh astringent beverage that’d help you stay up all night, and I’d make them coffees every morning to try and change their mind. I succeeded.

This lead us down a new rabbit hole – SPECIALITY coffee. I began reading more about coffees, and started consuming large amounts of video content from YouTube. I decided that my continuously failing cheap ceramic burr grinders were not going to cut it (pun intended), and I never really liked the taste of pre-ground coffee as much. I decided to acquire a Comandante C40 Mk3, an Aeropress, a Fellow Prismo, and go down THAT rabbit hole. I also bought a lot of silly coffee gear that I would only occasionally use, and this became something of a hobby of mine.

We bought light roasted coffees from Blue Tokai, and ordered sampler packs of anything and everything until our palettes settled down on something we actually liked.

Moxxie settled on a chic looking matte white Timemore C2 for a hand-grinder, and exclusively brews with their Aeropress + Prismo, and uses a matte white Sleepy Owl 350ml French Press to fluff their milk to make their large mug of fluffy coffee every morning, brewed with a caramely medium roast that is neither bitter nor acidic but has a long aftertaste.

My own flavour profile, meanwhile, seemed to go in the direction of light / light medium roasts that have good body, enough acidity, no bitterness, and none of the funky notes of warm dry wine (or sewer water) that some Indian roasters seem to enjoy. But I drink a lot more coffee than Moxxie, and as a result I can afford to experiment with gear & beans, and risk messing up atleast one of my coffees everyday.

I have a laboratory retort stand that I use to allow my pour overs to drip from a great height (to cool them down immediately to drinking temperature). I have a Hario Mugen dripper to SLOW DOWN my V60 brews while keeping the grind size coarse. I bought an Atlasware 2-cup (15g dose) MokaPot because I wanted to own more equipment that is made in India. Blue Tokai sold me a South Indian Filter to replace the one I used to own. I have a laboratory funnel that I sometimes use to brew micro pourovers (5g dose). I use a separation funnel to do a slow drip coffee.

I still have my “defaults” – 100% of my grinding is on my black Comandante C40 Mk3 (the makers claim it’ll last 20+ years, and I hope they’re right!), and I like the Aeropress best when it comes to brewing. I only use other gadgets for the sake of variety.

But this desire for variety and the continuous stimulation from experiments led to something I did not expect – I started writing lengthy messages about what I did to Moxxie, some coffee friends, and to a coffee discord server. And in a way, it cleared up my writer’s block! That’s where this blog post comes in. I’m going to post a lot about my experiments – coffee, kitchen, electronics, and all else – onto my blog on a much more regular basis going forward.

Here’s to a lot more content!

Personal Updates: Hello 2022!

Ahoy there, Rhino from the future! You’re probably the only reader of this blog. To give you company, I have decided to revive it and start writing more often! As is often tradition, I’ll start 2022 with a list of what I have been up to since my last blog post…

I moved out of Bangalore.

I now live in Goa! Urban Goa is extremely cosmopolitan, sort of like what Bangalore, Madras, or Bombay is, minus the cultural stagnation. You can jump between the various towns within Goa depending on the sort of vibes you are looking for – whether you’re in it for pretty roads (Canacona), smelly hippies (Arambol), or chic urban vibes (Panjim).

I changed my name.

My online handle has always been @wingedrhino. I’m now officially Rhino Maximus even in the offline world. It feels a bit like being reborn.

I got hooked onto embedded systems.

It’s been a decade since I last monkeyed with microcontrollers. COVID-19 related travel restrictions meant that my own home had to be my primary source of entertainment. So I converted it into a lab! My current favourite chips are the Raspberry Pi Pico, and the Raspberry Pi Zero 2 W. Don’t expect to see either of these in project blogs though! I have plenty of older hardware I am yet to use up before moving on to newer toys.

I resumed working for someone else.

It’s been a tiring few years hustling startup after startup with an obese, broken body that’s barely capable of taking care of itself. I decided to spend some time working on myself, and building my mind and body up to a level where it’d be a lot higher in performance, before I resume hustling.

I got into music once more!

I have never been anything close to a genius musically. Everything I enjoyed listening to was a bit too hard to play, and beginner level lessons taught styles I absolutely loathed. But blues, swing, and stoner rock changed everything. I am now back to playing the guitar! I’m still a beginner after ~15 years of playing, but this time I’m a lot more motivated learner.

I’m finally giving frontend development a go.

This is mostly down to how awesome has been to listen to. After years of building distributed systems and exclusively writing backends, how hard can it be to display a few boxes with colours, gradients, text, and images?

I don’t feel averse to writing anymore.

I had something of a writer’s block for several years. I’d feel stressed, unmotivated, or just extremely dark, and feel unable to express myself in words like could when I was younger. Furthermore, my vocabulary and grammar regressed quite a bit. This year though, I feel confident enough to ignore all that and just write for the sake of writing. What I lack in expressiveness can easily be made up by the usefulness of the information presented within this blog!

DCDBS: Easy docker-compose Databases

A common problem I tend to face when starting a project is setting up databases. Even when I use docker-compose to do the job, the steps are repetitive and configuration of each individual db is hard to remember. Thus, dcdbs. It’s a docker-compose.yml file with a bit of everything I’ve used via docker-compose. You can find a continuously updated version on my GitHub.

Databases include MongoDB, ElasticSearch, PostgreSQL and Redis. I threw in a web-based admin interface for each database. I’ve included Portainer to manage docker itself. Finally, I added a local version of httpbin to test sensitive APIs.

To bootstrap a new project, either just clone dcdbs and use as-is or use it after deleting anything you don’t need. You can actually get by with using a common docker-compose.yml file for small projects. That’s what I tend to do.

I’ll keep this blog post updated as I make changes to the contents but refer to the repository’s and also the docker-compose.yml file for information on how to get started.

Note that I only tested dcdbs on Docker for Linux. It should run on docker-machine since it is nothing but Linux. I cannot make promises about performance on native docker for Windows and Macintosh.

Have fun and happy hacking!

2018 Kerala Floods: Resources For Claiming Insurance

Note: This post was originally written for, a website with information to help people recover after the 2018 Kerala Floods. My mother, who works in the insurance industry helped me write this. I’m re-publishing it in my blog with the hope that it reaches a wider audience. Please visit AfterFlood for more resources on post-flood recovery.

The PSU general insurance companies have put systems in place to expediate processing of claims for the 2018 Kerala Floods. Here are some resources for claiming insurance.

PSU Insurer Contact Details

The insurers have contact details established to aid with claims processing. Here they are for your convenience (Source: The News Minute).

National Insurance Co Ltd

  • Claim hub: 9188044186
  • Email:

New India Assurance Co Ltd

  • Toll-free number 18002091415

Oriental Insurance Co Ltd

  • Toll-free number 1800-11-8485
  • Email:

United India Insurance Co Ltd

  • Vehicle claims: 8921792522
  • Other claims: 9388643066
  • Email:

Life Insurance Corporation of India (LIC)

Special teams have been set up in 14 district alongside officers to offer a special 24-hour assistance.

  • Trivandrum – 9482419551
  • Kollam – 9496301011
  • Palakad – 9447839123
  • Thrissur – 9447315770
  • Ernakulam – 8075947267
  • Kottayam – 9847167946
  • Idukki – 9895884618
  • Pathanamthitta – 9961993580
  • Alappuzha – 9746817205
  • Kozhikode – 9496710567
  • Wayanad – 9496220783
  • Kannur – 9496414055
  • Kasargod – 9447951431
  • Malappuram – 9446024966
  • Mahi – 9447468899

  • 24×7 Helpline for Kerala – 8448180966

Regardless of whether you have purchased an insurance from them, PolicyBazaar is offering a 24×7 helpline to assist with the insurance claiming process. Source: Business Standard.

Standard Claims Process

The claims process looks something like this:

  • First an intimation of claim by letter or mail will need to be given immediately based on which a surveyor will be appointed for assessing the loss.
  • The surveyor need to be provided with all documents like stock register, purchases and sales register, balance sheet, etc.
  • The surveyor He will also see if the all items are insured and for the correct value.
  • Accordingly loss assessment will be done.
  • If the amount insured is less than the actual value claim will be proportionately reduced.
  • On receipt of survey report, claim will be settled.

Things You Can Do to Expediate Claims

  • If you have multiple kinds of insurance for different items (vehicle insurance for vehicles, property insurance for household and posessions, etc) it is recommended that you categorize what item is applicable to which policy and then make a list of items that need to be claimed.
  • If your vehicle got submerged in water, take photos of it before towing it to a workshop.
  • Take as many photos of your house as you can, so that you can cover different items that have been damaged.
  • You can use photos of items inside your house before the flood as proof while accounting for what has been lost.
  • If you have made any purchases online or otherwise have receipts that haven’t been washed away, these also help expediate the claims process.

Here’s an article from News18 explaining the process to claim an insurance for motor and property categories: page on Here is another from The Indian Express.

Extra Services by Companies

  • Some corporations are offering free repairs and other services. Read this article by The News Minute to learn more.
  • Private Insurers have simplified documentation requirement for claims and have said that a municipal death certificate, or death dertificate by any competent government authority like local government of Kerala, armed forces, government hospitals or police authority will suffice.
  • Bajaj Alliance Life has said ā€œDeath and disability claims for customers from these States will be processed on priority, and the company will make best efforts to settle maximum claims within 72 hours of claim registrationā€
  • Max Bupa has said they’d ensure all claims from Kerala get immediate attention and all eligible claims are processed on a cashless basis and on a priority.
  • Source for the last 3 points: The Hindu Business Line

PS: If you’d like to contribute content to AfterFlood, please fork their GitHub repository and submit a pull request!

Find and Replace with Sed: Rename Golang Packages

I just consolidated my GitHub, Twitter and Instagram handle. They are the same as the .com domain I bought for this blog. As I renamed my GitHub handle, I also needed to fix import paths and rename golang packages hosted there.

I used Sed, everybody’s (and also their parents’ and their grandparents’) favourite stream editor. It’s from 1974 – the same year Judas Priest released their debut album, Rocka Rolla. Because Sed is available on all platforms and works directly with text files, you could re-use this recipe outside golang.

The syntax to find and replace strings recursively across files in the current directory looks like this:

sed -i 's/' **/*.go

Super simple eh? All you need to remember is the following:

  • The flag -i asks for an in-place edit (i.e, replace content in the files)
  • The operator s/ asks for a substitution.
  • The /g at the en informs Sed that the substitution is global – it is to be done for all matching occurrences.
  • The original package name and the new package name come between the s/ and the /g, separated by a forward slash /.
  • We need to use back-slashes to escape regular slashes that occur within the text we’re searching for and the text that is being replaced (I had to replace with
  • **/*.go is used to recursively hunt down all .go files from the directory we are operating out of.

I suggest doing these kind of operations only after you have checked in code into GitHub so that if the worst happens you can restore a working copy from there. Always do a git diff between the old version and the new version to see what has changed. You could also use Meld if you want to compare directories that contain multiple git repositories:

meld oldfolder newfolder

There’s a lot more to sed than simple substitutions; so head over to a more in-depth tutorial like or to learn more!