I truly intended to use Rails' extra features. First life just got in the way. And then Rails did.
Grab a bowl of buttery popcorn because the saga continues! The end of the previous chapter saw our intrepid little Rails app camping happily on Heroku. This latest chapter in the hosting chronicles brings with it a twist: not just a change in host, but a complete migration from one programming language to another.
Onward for the Why’s, How’s, and Gottchas of the switch.
Is Hugo the right match for your site, and is it worth the hype? Here's what you need to know, reader's digest style.
Static site generators aren’t new, but something about the fresh simplicity of Hugo is turning heads. We’re in the early stages of the Gartner Hype Cycle, but expect to see media outlets abuzz with tales of Hugo “making waves” and “disrupting stuff”. Even de facto strongholds like WordPress have begun losing ground to the inexorable spread of the Static Invasion.
But between all the skirmishes, turf wars, and soap-box-soliloquies, how do you know if Hugo is the right match for your site, or if it’s even worth the hype? Here’s what you need to know, reader’s digest style. (from Migrating WordPress to Hugo, Step-by-Step)
Five months and 200 hours later, I’m standing tall, arms-folded, my first-ever training course live on the video wall behind me. How’d I get here?
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've got a WordPress site you want to migrate to the Hugo static site generator. Now there's a fun course that will help you do it, safely and efficiently. What should you expect from the course?
Hugo isn’t even at version 1.0 yet, and it’s already of the one of best static site generators in the world. A switch from WordPress to Hugo can save you money, improve site performance, and harden site security. For the shiny gopher-shaped cherry on top, do I dare say it? — Hugo is fun.
With your current site stuck in WordPress, how do you get from point WP to point Hugo?
The intriguing true story of one programmer's battle with Carpal Tunnel Syndrome, and the multipronged attack strategy which led him to a victorious recovery.
Night is falling as the old cowboy coder pauses his story to stoke the
flickering campfire. You lean in slightly, eager to hear more.
A deliberate man, he takes a draw from his tin mug and then exhales contentedly,
gazing into the fire. Deliberate? — Maybe he just values a good dramatic pause,
“Trouble was,” he continues, “click-clacking the day away was hard on the old
wrists. Before long, I found myself square on the littered trail to neuropathy.
A wise old country doc told me I had…” He pauses briefly, then pronounces each
word like a hiker carefully negotiating rocky terrain, “carpal tunnel
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”…
Markdown is a great way to format text inline, without getting in your way. i.e. it’s not ugly and cumbersome like HTML tags, and your hands don’t have to leave the keyboard to access formatting toolbars like they might in a traditional text editor. Personally, markdown helps keep me “in the zone” when I’m writing. That’s why this site uses markdown for nearly all its formatting needs.
You can learn markdown in about 5 minutes. Here’s a cheatsheet to get you started!
Code flows effortlessly from your nimble fingers, like fine cloth from a loom. Your face is serene, focused, content. Suddenly, a wrinkle appears in your brow, breaking that pleasant mask of serenity. The frown deepens. “That can’t be right…” What happened? A bug! A hairy bug lurks fiendishly somewhere in that elegant tapestry of code love. How did the bug slip past you? You were so careful! A frustrated hour passes, then two. You comb through each strand of code, retrace your steps through the intricate lattice of if, when, and for…
We sink so much time into the deep pit that is debugging. Yet for all the time we spend on it, there is surprisingly little literature written on the subject. A notable exception is Debugging: The 9 Indispensable Rules for Finding Even the Most Elusive Software and Hardware Problems, by David J Agans.
"Minimum Viable Product, ship it, incrementally add value! Yes, we know we shouldn't shoot for perfection - The "perfect is the enemy of the good." That said, nobody wants junk either. How do you know when a feature is "good enough"? That's where the QUPER model comes in.
Spanish for the Inner Gringo helps intermediate to fluent Spanish speakers correct the mistakes they didn't know they were making.
I recently launched a new learning channel, Spanish for the Inner Gringo! It aims to help you polish up (squeak) your Spanish accent and grammar so that you sound more like a native, and less like a Hawaiian-shirt-wearing, camera-laden tourist.
The videos are short (only two-minutes!) and I will be releasing one video every few weeks. The AV is sub-par, so you’re bound to get some laughs too. Subscribe to the channel and sign up for updates so you won’t miss a single video.
With our attention increasingly fragmented, and our work environments increasingly shallow, Cal Newport's book Deep Work helps us fight back by relearning and recommitting to focus. Here are a few tips I picked up.
Deep work – it’s where the right stuff gets done. And it just happens to be the most enjoyable state of mind for a knowledge worker – that illusive state of flow. In his book, Deep Work, Cal Newport does a fantastic job laying out the What, Why’s and How’s of “deep work”.
“I’ll live the focused life, because it’s the best kind there is.”