Everyone has a niche, an area, they want to focus on and be great at. Most don’t know what it is, but it’s there, in the back of our minds, lurking, trying to find a way out, trying to figure its way out. Problem is, it takes forever, and even when we think we know where it is, it’s the wrong niche, so we become frustrated and stop searching. That’s the hard part about niches,…
You can stress out about what broke, try to point fingers, analyze logs, try to figure out who changed what and what went wrong or you can work right now to fix it. Figuring out what happened will take much longer than fixing it right now. If you’re focused on playing the blame game as to what went wrong and who did what, then you’re going to miss out on what needs to be done.…
If you aren’t using your own software you are missing out on everything great that you can learn from it. How do those features truly work? What happens when you use a function in a different way? How many clicks does it take to accomplish a task? What happens when something goes wrong? How do we handle errors on the client side? How long does it take to load? What do I think of when…
Where _____________ is the app currently being used by your team to accomplish a task that they deem important to their overall success. But you don’t use it, maybe you never had the opportunity or need. So the question now becomes, are you going to learn something new or make the entire team change their practice to fit to your needs? No hints needed.
There comes a time in every developer’s life when they realize they need to write better tests. Whether it’s a console, web, or unit test, they need to write better tests. If you’re at this point, here are some elements that are important to writing great tests; They should be objective – the result is the result is the result – there is no complex interpretation. They should be measurable – whether they do it…