Having different favicons for your development and production environments can be extremely useful: you can see in a split second if you are working on the right tab in your browser. If you already refreshed, refreshed and refreshed again a page for 5 minutes… wondering why your changes don’t show up, and realizing that you were refreshing the live website instead of the local one, raise your hand ✋. This won’t happen anymore with this quick JavaScript hack to display a different favicon depending on your environment. 1. Create two different favicon images 👉 Note: a favicon image should be … Continue reading Different Favicon for Dev and Prod
Guidelines #2 for QA
Following the previous “Guidelines for developers”, here are some basic rules/advice for Quality Assurance (aka QA) based on my experience. You will notice that sometimes it is seen from the developer’s perspective, the rest consist of things I’ve seen. Once again, it is not exhaustive, so feel free to add your own! All the rules may not apply to your projects, but I’m sure you can find equivalents. 1. Prepare your tests Have scenarios ready, know what you need to do, list all the variations of things you can come across, etc. 2. A feature cannot be tested by its … Continue reading Guidelines #2 for QA
Guidelines #1 for Developers
Here are some rules or guidelines I try to live by as a developer. They are for all of you, from the beginners to the seasoned developers. It is not an exhaustive list, so feel free to add yours in the comments below! 1. “Temporary” doesn’t exist in development Be honest with yourself, you’re never going to change it. Ever. 2. Use meaningful variable names Because abc, test or tmp are not really understandable by other developers, or by you in 6 months. 3. Be consistent with style, use guidelines Some are immune to it, but unfortunately (or not), it … Continue reading Guidelines #1 for Developers