Should you use multiple <h1> heading elements on your page in 2022?
Maybe you are a bit old-fashioned and, like me, still clutching the principle of Only One H1 Per Page pretty tightly in your internal style dictionary.…
How to measure web performance with Navigation Timing API
We will explore the Navigation Timing Web API (Nav-Time API) in this post, you will learn a powerful tool to programmatically gather and measure your web application's key performance metrics.…
Afraid your code discussion is hurting team morale? Use 'Disagree and Commit' and get through technical disagreements unscathed.
The beauty of 'disagree and commit' is that it separates the developer from the opinion.…
Is it Bad for Junior Devs to ask for help too often? 4 Signs for when Junior Developers should Ask for Help.
By the end of the post, you'll have a 4 step checklist to help you determine whether now is the right time to get help, follow these signs and the senior devs on your team will be more than happy to help you every time you ask for help.…
Your software engineering career in 5 degrees of DRYness.
Personally, I wish someone gave me a 'Software Development and You' handbook when I first started containing a roadmap of how I can improve as a programmer. Not just improvements in the next 1 or 2 years, but a decade into the future.…
Code Reviews crippling your Delivery Process? How MR comment hierarchy can speed things up.
Are your pull requests stuck in the code review stage, going through multiple iterations while your initial estimates date are long in the rearview window? In general, code review comments fall into a hierarchy of the following categories, from least to most severe:…
4 Ways to Make Your Front-End Documentation Actually Useful
Here are the 4 tips that emerged during my research for better Front End documentation. They could be especially helpful for those who are not working closely with UX/UI designers.…
Getting Pushback From Your Code Review Comments? How to Prevent your Comments from Being Mischaracterized.
Have you ever worked with a developer that gets defensive whenever their merge requests get code reviewed? Reframe the code review process away from an 'instructor correcting student' dynamic and into a 'colleagues working together' mindset.…