Let me break your suspension of disbelief and admit that I am not writing this "today" ... well it is still today by my standards because "tomorrow" starts at 6am and it's only 5am right now ... but Wordpress is going to disagree with my definition and claim I have posted this tomorrow.
But despite this small glitch in how the calendar is arbitrarily constructed, I did manage to learn two things today.
The first and most important is that trying to book somewhere to stay for a single night on the same day you plan on showing up just doesn't work. Now I don't have enough data points to know exactly and for certain that it doesn't work, but finding such a place in San Francisco at what I'm told is the height of the tourist season ... well it doesn't work. I tried to find hostels, but all online things said nobody had any vacancies. I also tried Airbnb and didn't even get a response ... tried couch surfing and also didn't get a response.
Hell, I even tried to beg the twitters for a couch to crash on for the night and there were no takers. Nobody wants to host for a guest that's coming at 4am and staying until about 8am ... possibly drunk out of his mind ...
What was the other thing that I learned ... I know it was something useful, but I can't think of it for the life of me. So I'm going to go with having learnt that there is a Starbucks open all night in San Francisco and this means I have somewhere to "stay" until the trains start running again at 8am.
Continue reading about I learned two things today 6.8.
Semantically similar articles hand-picked by GPT-4
- I learned two things today 7.8.
- Temporarily homeless, a story in one dumb move
- It's good to be back, but I still don't know where I like it more
- I returned to Slovenia after 3 months and I am culturally shocked
- I learned two things today 14.8.
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 ❤️