Logs are the lifeblood of any application you create. If your logs are garbage and make no sense, debugging issues when they arise (because they will arise), will be near impossible. Generic Error Codes, readable information, and elevated error states allow you to filter out what you need and diagnose information quickly. If you’re spending hours and hours to find out what went wrong, you missed something in your initial build.
In every problem you are working on, there are always a number of What Ifs to figure out – after all, it’s a problem – that you don’t know how to solve. But if you give into each and every what if that comes up, you’ll never get to solve the problem and will be left drowning in an innumerable setup of What Ifs for life. Isolate the problem, focus on the immediate, save the…
When doing Performance work, the first place you always need to start with is knowing your baseline. If you don’t know your baseline, you will not know what tools to build, what tests to run, and where to move forward to. How do you hit your baseline? You send it traffic, then you up, measure it, if it’s still working, up it some more. You keep upping it until it falls over and then you…
When someone leaves your team, there is a window from the point when they announce when they are leaving to when they actually leave. That window is the amount of time you have to get all of the training this person has learned in their time with you and download it to another person. These are the interactions you don’t want to push off and you want to kick off as soon as possible to…
It’s akin to the meeting for the meeting. Or the email to send an email. If you’re having a meeting to discuss the plan, then come up with your plan but don’t have a meeting to plan the plan that you are going to create. You’ll always get more traction by showing up with something and whether it gets torn apart, upgraded, or left as is – it will be a much better starting point.