Yesterday was the fabled second day after a blog post, which meant I should've written a new blog post as I once, long ago, promised I would. Obviously since then I haven't quite lived up to my promise, but I try to post as much as humanly possible.
That is to say, I try to try as much as humanly possible because in all factuality I'm simply quite too lazy to keep posting all the time and there are always things coming up and biting me in the arse with, apparently, the sole intention of distracting me from writing the blog even when I have awesome ideas.
But that is not all, a while ago I vowed to have the site updated to a new design and made all pretty and such by the end of the month, which is tomorrow, and it doesn't quite look like I'm going to make it. Even though the coding is rather much all done because I skillfully integrated it into a project at work and opensource demands I get to use it elsewhere as well, there's this little issue of design. The designs I haven't touched since sketching up the fancy bits five days ago. The design that doesn't seem to be getting made for a while.
Although I really should, absolutely must, kick myself into high gear and draw those fucking things already and throw it all together. Must. Why? So I can work on other more lucrative projects I've recently hooked up with. Let's hope money will be enough to throw laziness to the wind and let me work.
Continue reading about The fabled, but lazy, day
Semantically similar articles hand-picked by GPT-4
- 17 hour workday Sunday
- The chronicles of a dead blog
- Oh shit
- NaNoWriMo day3, when nothing happens
- Busy busy busy
Learned something new?
Read more Software Engineering Lessons from Production
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 👇
Software Engineering Lessons from Production
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
Want to get my best emails on JavaScript, React, Serverless, Fullstack Web, or Indie Hacking? Check out swizec.com/collections
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
Want to brush up on your modern JavaScript syntax? Check out my interactive cheatsheet: es6cheatsheet.com
By the way, just in case no one has told you it yet today: I love and appreciate you for who you are ❤️