Today I woke up into a somewhat warm room, but my bed was warmer. So I hit snooze, I can afford five more minutes. Then I hit snooze again. And again. And again. Ok so it's now been 30 minutes of snoozing in a warm bed. Fuck it, let's turn off the alarm, I can be warm for another 15 minutes right? Yes, of course, but it turned into 45 minutes instead. Oops. A quick shower and clothing later and I'm already on my way to work.
Getting to work is a five minute walk for me. It was a cold morning, but a refreshing walk. I rather enjoyed it to be honest. But when I got to work something felt funny on my head, it was somewhat itchy and annoying. I go in to scratch it and ... lo and behold, my hair had frozen solid. What the fuck?
But anyway, I've been reading Neil Gaiman's Journal lately and I like it so much that I want to become one of those Neil Gaiman readers, so I've decided to write him this question:
Dear Neil Gaiman,
I'm not a crazy fan and have until recently not even known you existed. That was, until I saw Amanda Palmer's webcam stream from a dinner with friends she did a while ago (I AM a crazy fan of hers, I admit). You seemed like a cool guy so I decided to check out your blog. This was the epiphany when I realised she doesn't say the Google You song was written by an "unknown gamer", but by "Neil Gaiman". Why those two sound so similar I don't know, probably because I'm not english.
Anyhow, I really like your blog and find it a delightful read. But seeming as how you write a lot more than just the blog and I'm becoming increasingly interested in reading your stuff, I was just wondering if you could make a recommendation on where to start? What would you say is your best work to reel in a new reader who has never had any contact with anything you've done?
So yep, I'm just gonna go ahead and submit that through his "ask Neil Gaiman" thingy and hope for the best. Or can either of you readers suggest something?
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. 👌"
Senior Mindset Book
Get promoted, earn a bigger salary, work for top companiesLearn more
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 ❤️