Post

Best piece of advice someone gave me that I never followed and always regretted: Every time you learn something coding at work, write a tiny, low-effort blog post about it. You can always edit or beef up later, but it's the fastest way to remember what you've learned.

7 reposts42 likes

That’s a great idea. Over the years I’ve been writing paying attention to images, etc. The problem is, that for a new post to be consistent with everything else, means spending a significant amount of time, which isn’t always an option. Might need to reconsider 🤔

Writing isn’t typically the issue for me. In fact, I love to write. It’s everything else around it like properly cropped and right images that’s taking up the time. Recently I had a look at posts from Matt Mullenweg and DHH that got me thinking about doing it differently

I'm not writing a blog post about how Capybara somehow reads your CSS when matching things in the DOM so if you're searching for "Body" (and it is "Body" in the DOM) it doesn't find it because you uppercased it with CSS. I don't have time to write about that. I'm crying about it.

This is the reason I started my blog. How I accomplish it. I open an MD file the second I run into any resistance while effecting a task. When I am done, I commit it. I have more unpublished than published, but I have documented a lot of weird things, and silly mistakes!