“Do you want a mess, or a masterpiece?", the master seamstress fondly reminded her young protégé…
A hopeful software craftsperson, I can imagine writing code so elegant that the source is featured in an NYC art gallery in the year 2442. But that’s just a fantasy, because here I am pushing my big grimy ball of software mud up the hill with everyone else, trapped and raging against the impossible triangle of quality, price, and speed.
But it’s not all stern foreheads and storm clouds — We’ve got fun code-wrangling blogs like tygertec to get us through the day. And coffee! We’ll always have coffee. And Paris. I’ve heard good things about Paris.
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?
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.
I saw a tweet the other day that said, “the scariest thing about COVID-19 is that it looks like a JIRA ticket.” That is …
Can your product’s “killer feature” — that amazing bit of utility that sets it apart from the competition …
Wouldn’t you like to know when MailGun fails to deliver an email? Or worse still, when someone complains about an email you sent? …
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.
Okay, so it’s a team of one ➡ The “Ty” in tygertec.