Our Engineering team, apprentices, Front-End Developers, and Designers share insights on the development process
At its core, pairing is another useful strategy to work with your peers and get shit done. The best way to know what works for you is to take more opportunities to pair with others, think about what works and what doesn’t work, and continue to refine this skill set.
Working in Terminal is faster and easier when you set up your bash profile with these awesome shortcuts and tricks that you can install yourself.
You’ve tested. You’ve deployed. Your work is out in the wild. Then – WHAT IS THAT on your bug report? Oh… You have users on Internet Explorer. Jason shares how to test using Windows Virtual Machine on the MacBook.
Coding without if-statements is one method for learning other ways to structure your code. That doesn’t mean never use if-statements. Being careful with conditional logic makes better code. Here’s why.
Review your own code first before sending it for peer reviews. Here’s how to change the lens through which you’re inspecting your code.
Instead of living in fear that you’re the one asking bad questions, consider that your questions will probably lead your team to deliver better outcomes.
It may be simple to use pronouns like “this, that, these, those, and they”, but Thomas Knoll says that these are ambiguous and dangerous words. And you should murder them.
Don’t use JSON as a configuration file format, unless you have to. Here are all the reasons why – and what to use instead.
Here are 8 things Developers can do to balance the effort of communication across entire project sprints.
A great way to save hours of time is to always keep cross-browser best practices in mind throughout the process of developing a new site.