Yesterday was the busiest Sunday I've had in a long while since usually I devote my Sundays to leisurely activities with my girlfriend. This weekend however the girlfriend went on a trip to Tirol with family and I seized the day (and night actually) to remake my blog - something I've been planning to do for several months, but never quite got around to.
So on Saturday I started working on the software part of everything, some modules needed an upgrade or two, a touch up here and there and certain things I had to develop from scratch. Ten hours later, at around three in the morning, that bit was done, time for shuteye. And then came The Sunday. Got up and almost immediately started working. Set up my scanner, scanned in my notebook, torn pieces of paper, torn up sketches and other stuff that I needed.
And so, at six in the morning, a full seventeen hours later, the blog was complete, uploaded and quite functional. This was the first time I ever achieved anything like this on such a short timescale, then again, usually the designs I have to implement are quite more complex and tedious to make work. However most of my time was spent creating the images needed. For example photoshopping scanned in pages of writing onto torn paper (you can see the result bottom left) was especially difficult since I had to figure out how to do it in the first place. It turned out quite well if I do say so myself.
Anyhow, over the next few days I'll be making touch ups to the design here and there, perhaps ironing out a bug or two and essentially making the whole thing even better. Bear with me please.
Continue reading about 17 hour workday Sunday
Semantically similar articles hand-picked by GPT-4
- The fabled, but lazy, day
- I kicked myself in the balls
- Remember to feed your sysadmins
- Oh shit
- Of penguins and OSes
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 ❤️