100DaysOfCode, Day2

The second entry in a continuous series of learnings from this accountability challenge.

100DaysOfCode, Day2
Photo by Walkator / Unsplash

I decided to make longer form accountability posts for the trends I hashtagged below. Will this hurt how I’m perceived when I decide to hunt for a corporate job and let freelancing take a back seat? Not sure.

Some schools of thought say you should avoid these trends on networks like LinkedIn. To be honest, I can see why, so my intent is to enhance what I document about my efforts and process.

I want to see my own progress more than I want to prove myself to anyone else. So I’m planning to expand on my efforts in the takeaway section and give a “behind the scenes” look at what I find worth learning by providing my Anki questions/answers.

If you have any questions or input on how I’m structuring this and tracking progress, please reach out on socials or feel free to buy a sub and comment here 🙂


Day 2 of #100DaysOfCode to #buildinpublic with #100Devs

I studied:

  • HTML and CSS today with Shay Howe, beginner through advanced
  • practice with various layout exercises

I built:

  • a content strategy that I hope will be sustainable

Biggest Takeaway


I wrote a post on LinkedIn based on a discussion from a recent Twitter Space, the topic was burnout. Here it is.

Coincidentally, I couldn’t keep my focus groove at the keyboard so I deliberately allowed myself to run errands and spend time being present in the sun and with pets for the better part of the day.


It’s important to network as a way to help your prospecting efforts. Don’t rule yourself out of the running for work you may not normally do.

I landed a client for a small piece of digital media design work today.

I was nervous to commit to being able to do the work, so I was honest that it wasn’t my typical type of gig but I volunteered to research into it a little and made an educated offer based on my research. The offer was accepted! Paperwork and payment to follow…

Design {and Development}:

I’ve learned a couple of different clearfix hacks for use on legacy code that uses floats for positioning. There is one involving table-level elements listed in the Shay Howe Guide to HTML and CSS material that I thought was interesting for its historical insight into the way certain problems were solved while CSS3 and the layout of the web were developing past infancy and teens.

I appreciate that 100Devs has us learn a little bit of “how it once was” and is explicit that this is because we may get hired by companies that have a legacy code base.

My biggest takeaway on positioning with floats is that depending on how content-rich the page is, things were likely cumbersome, to say the least. The thought of margins and paddings overlapping in unexpected ways really nags at the pixel perfectionist in me.

Flexbox is a huge step up, in my opinion. I plan to take one of the layouts I was practicing with and build it from the ground up with floats, then refactor it with Flexbox (and maybe grid) in order to see what lessons there are. It will be a future feature post for sure.

Note Dump

I use this space to generate Anki card content for my spaced repetition learning. For more info, check out Ali Abdaal on YouTube. The things I called out to quiz myself on are personal to what I took away from the material I reviewed but if you’re curious to discuss any, hit me up on Twitter or just become a paid subscriber to help by donating to Resilient Coders (then you can comment here 😉)

  • I didn’t watch a lot of videos today which is usually where the note cards come in and the stuff I practiced I actually felt competent on so there weren’t many Anki additions, but here are my stats on reviews
dashboard of Anki study card performance stats
dashboard of Anki review card stats