Leading a team. Testing Code. Writing Code. Building Requirements. Yes it gets tough and is never easy and there are good days and bad days, but this is what you signed up for because outside of the bad days there are always going to be good days, great days, and yes gooderer days (seriously that’s a word Grammarly). This is what you signed up for, push through the bad so you can get to the…
Here’s how you run performance, scalability, and load tests. Write down what you are going to test. Write down how you are going to test it. Write down how you are going to measure the test. Run the test. Report on the test. Rinse, Tweak, and Repeat Don’t worry if, in the first round, you get it wrong, that’s why you rinse, tweak and repeat to keep getting better and better at it. Most times…
No one wants to do the heavy lifting, especially if you’ve done it before, you know just how heavy it can really be and that what is being said at that next meeting or on paper is just a glimpse into what is required. But at the end of the day, it needs to get done and you can either ignore it or start lifting. What you might not realize is that if you’re seeing…
I have my favourite tools to do building projects with. I don’t even know if I always need them, but when starting a new project, I always bring them. And eventually, I need them. They are the old stalwarts that never fail. Similarly, the tools I write and code with don’t change much anymore. I’ve tried a variety of tools but they generally all come back to the same ones. I drift back because they…
The only answer to the statement – “It’s not the way that I would do it.” – is “then how would you do it?” If the answer is not forthcoming immediately, or in the similar amount of time that it took for you to come up with the approach, then the statement is invalid. If you make that statement, you should have a clear picture of how you would do it. The answer to -…