The beauty of working on performance problems is that they are the simplest to measure – code still does what it was supposed to do before AND goes faster. WIN! The problem is, we always do this after the fact, after the customer reported it, after we deployed it to QA and it blew up. After everything went wrong. We don’t do it before. And that’s where we need to start bundling the work into…
I think we are all feeling like this these days – taxed, weighted down – trying to do our best, not sure what to start on next because who knows what we are going to have to be working through next. If you’ve never had an Out of Memory exception, it occurs when your code has taken up all the memory on a server and there is nothing left to give back. I haven’t had…
Think back to the last time you had a great meeting, one that truly blew your mind and left you feeling satisfied. Chances are it wasn’t in the last few months. Greater chances are that it was even longer than that. If you knew your meetings for the next week and the week after we’re going to be exactly the same, leave you feeling exactly the same way – would you still attend them? Or…
Because now you have all this other stuff to deal with that two days ago you didn’t have to do. Now things need putting together, patching and updating. Now your time is being pulled in different directions as everyone wants their piece delivered first but you are only one person. And of course, you have your own list of goods you want to work on. So the question is – where do you start? You…
Not big on broadcasting what I’m focusing on but sometimes good to write it down to remind myself why I’m doing it. Areas where I want to focus on in the coming months; Typescript and its application to projects I’m working on AWS/GCP – always good to see how the other side of the world lives (or in this case the majority of it) Meetings – why do they continue to be broken after the…