One of the reasons I've been so drawn to DEV.to over other platforms is the super encouraging and helpful community that gathers here. Initially I felt like it was going to be more a place where I sat back and watched, rather than write and contribute, but I've been so pleased to find not only helpful articles and tutorials that I understand, but also that input from new coders and devs is well-received.
I thought it would be nice to compile some of the best posts every week for those of us who still identify as #codenewbies!
Growing up, I was very into art and photography... but I often feel like that hasn't transferred over into very good digital design skills as an adult. When designing my first portfolio during bootcamp, I struggled with a lot of the extra margin/padding issues addressed in this tutorial, and the typeface and font resources she has included are awesome.
I used this really great tutorial to learn about CSS variables recently, and now I'm super obsessed and will never dream of styling any other way.
Laurie teaches us about "cookie licking," which rings very familiar as I spend some part of most work days with a 4-year-old on my lap watching Cookie Monster shorts on YouTube. Most days, my imposter syndrome is triggered by not understanding the terms that my co-workers use, and this was a reassuring reminder that not everyone starts off knowing every technology and verbage.
One of those words I didn't understand? "Framework!" For the last year I've been sitting in on framework meetings and didn't even realize until recently that I don't really know what a framework is or what it means to be building a new one. Huge thanks to Molly for this uber-timely post!
Repeat after me: PSEUDO-CODE IS GOOD. I write my pseudo-code a lot of ways, including a recent scenario where I couldn't find an issue when looking through my editor... so I printed out the whole stylesheet until I could hunt it down.
I love helping, but I love even more when someone has done even the barest minimum of research on their own before asking for questions. There are times, though, where no matter how much documentation you read or research you do, the "a-ha!" moment never comes. (I'm right about there with a project of my own...) There are a lot of great tips in here on how to prepare to ask for some guidance.
That's it from me for this week, and don't forget to check out the 7 most popular DEV posts from the past week!