On any given week, I might be working on 2-3 different projects at a time. I’ll often have to dip into an old project, start a new project, or assist another developer in their current project. When you’re dealing with so many files with so many different authors, you realize the importance of a well documented and updated README file. Every project has its own requirements, installation processes, coding styles, content management system, etc. A well documented README file can save a developer hours of time.
Recently here at Happy Cog, we’ve been using the lobotomized owl selector to handle vertical spacing between elements. Up until now, we’ve been adding a class of `.spacing` on a container to create equal spacing between all of its direct child elements.
For the last 6 months or so, I’ve had the privilege of completing an internship working as a developer for Happy Cog. Throughout my time working here, I learned about the strategy, artifacts, and processes of building a beautiful, user-focused, responsive website. I attended both internal and client project meetings, worked directly with the designers and developers, and built an understanding of design systems and the best practices for coding.