Fresh from the paw of the Tyger
and the thrill of the fight
the struggle, uncle
bits to bytes
and bugs in prod
got me crying
I ain’t lying
I’m still compiling.
Once upon a time I needed to connect to an Android emulator running on a Linux box from a Windows virtual machine. Yes, it was very …
You’re typing away at the console in Linux or Mac OS when you suddenly need to display a QR code. There are a lot of dubious …
They told me I needed a hobby
So here’s a few projects you may find interesting. Some of these half-baked goods may even be on GitHub .
Are your golden ducks in a row? Easy-to-use budgeting sidekick for Android and iOS. Ad-free, privacy focused.
‘OK to ship a code smell, but never OK to ship a breath smell.’ Bit tongue-in-cheek, but you can buy ’em on zazzle .
From the mind of the Tyger
and the frozen sands
of the hourglass
snapshots of thought
from an instant of time
I won’t kid you; the road to course creation is riddled with potholes, roadblocks, and sketchy checkpoints. It was hard. But the solution to each obstacle taught me new skills and valuable life lessons. I think it’s time to document those lessons.
You’re a programmer, software craftsman, full-stack developer, software engineer. But regardless of the titles dangling from your Twitter bio, if you want to greatly improve the quality of your code and indeed the quality of your life, there’s one more title you should consider tacking on there: “Runner”…
When you first started with git, you quickly got up to speed with committing, pushing, pulling, merging, and the like. But then you noticed a gaping hole in your knowledge - how do you find stuff in Git? Can you revert to a version of a file as it stood three weeks ago, or find out when a bug was introduced? Who was the last person to edit this file?
They always tell you that the great thing about Git is that you [almost] never lose any history. So how do you access and utilize that history?
Okay, so it’s a team of one ➡ The “Ty” in tygertec.