This is a Livecoding Recap – an almost-weekly post about interesting things discovered while livecoding ?. Almost always under 500 words and with pictures. You can follow my channel, here. New content almost every Sunday at 2pm Pacific. There’s live chat, come say hai ?
<This is where a video of the livecoding would go, but LiveEdu saved only the first 5 minutes. The rest went poof ?>
I guess I could upload my own copy to Youtube and embed that… ?
Nobody else thought to get it either :D
The new site isn't much to look at, and it doesn't have to be. It exists, and that's what matters because now I can make stickers! Right now, the site is a link to the book and to the next workshop.
Ok, I'll be honest: 90% of that screenshot happened many hours after livecoding was over. Writing with people watching over my shoulder still feels weird.
So what did we learn while livecoding this?
We learned that Canon didn't think their flip screen UX through. The cable between the camera and the computer covers the screen you use to see yourself. Maybe they never intended you to use your DSLR as a webcam? Who knows ...
We also learned that @daemon92 misses Kiwi butt. With the new camera, my bird no longer puts his butt in front of the camera. Such loss.
And Daemon is still doing homework. He hopes to finish soon, so he can go spring break and party. Young'uns these days… when I was in college, we partied first and studied second.
We also learned that setting up a custom domain for Github pages is still confusing. Documentation feels circular, fragmented into too many pages that say two sentences, then tell you to go somewhere else for the real answer. It's ridiculous.
At least they create the CNAME file for you these days. I think that's how Github servers know which repository a domain links to.
I mean, you're setting DNS to point at Github servers in general. They must be doing some sort of resolving internally.
It's been a while since I sysadmined ?
Oh, and fundamentally, we learned that using a custom domain when hosting your site on Github pages disables https. No green checkmark for your beautiful new page.
This makes sense of course. They'd have to issue certificates for each domain hosted on their servers, and that kind of defats the purpose.
Oh, and we learned that to get Webpack offline-plugin to work, you have to
npm run eject your app. This is unfortunate because you lose automatic
react-scripts updates, but worth it because it makes your site hella fast. Hella. ?
Until next time, happy hacking. ?
PS: I later learned that running offline-plugin on localhost is a bad idea
I write articles with real insight into the career and skills of a modern software engineer. "Raw and honest from the heart!" as one reader described them. Fueled by lessons learned over 20 years of building production code for side-projects, small businesses, and hyper growth startups. Both successful and not.
Subscribe below 👇
Join Swizec's Newsletter and get insightful emails 💌 on mindsets, tactics, and technical skills for your career. Real lessons from building production software. No bullshit.
"Man, love your simple writing! Yours is the only newsletter I open and only blog that I give a fuck to read & scroll till the end. And wow always take away lessons with me. Inspiring! And very relatable. 👌"
Have a burning question that you think I can answer? Hit me up on twitter and I'll do my best.
Who am I and who do I help? I'm Swizec Teller and I turn coders into engineers with "Raw and honest from the heart!" writing. No bullshit. Real insights into the career and skills of a modern software engineer.
Want to become a true senior engineer? Take ownership, have autonomy, and be a force multiplier on your team. The Senior Engineer Mindset ebook can help 👉 swizec.com/senior-mindset. These are the shifts in mindset that unlocked my career.
Curious about Serverless and the modern backend? Check out Serverless Handbook, for frontend engineers 👉 ServerlessHandbook.dev
Want to Stop copy pasting D3 examples and create data visualizations of your own? Learn how to build scalable dataviz React components your whole team can understand with React for Data Visualization
Did someone amazing share this letter with you? Wonderful! You can sign up for my weekly letters for software engineers on their path to greatness, here: swizec.com/blog
By the way, just in case no one has told you it yet today: I love and appreciate you for who you are ❤️