I can’t say, I have always been someone that has followed patterns and framework implementations to the letter, rather using their approaches to development work. But there are some that I lean on heavily and come back to when thinking about building solutions, no matter the purpose; Leverage queues where possible – offload your work into bite-size deliveries that take the work off the middle-end. Scale out your Databases – you don’t need one and…
Plants Grow. People Grow. Teams Grow. So why would you think your code can never be improved? Never get better and never grow. It doesn’t mean your code was bad, it means it’s simply time for it to move on, grow and become something else.
I don’t think you can ever go in search of a Mentor. You might read about someone and decide that they are like you, but you won’t know until you sit down and talk with them. Because they are famous does not mean that the two of you will click immediately. I think it happens organically, over time, through successes and failures, and in some instances, you won’t even realize it until it’s over. It…
There is a path between two problems that are often ignored and generally occurs between two opposing sides. Some call it the middle ground, but it’s simply another option for getting work done. Sometimes there is no middle ground or way in between, other times, a good number of times, there are more options here than we could ever believe. The problem is being willing to look at them, that’s where we stumble.
It doesn’t need it – your code – it doesn’t need to be defended. You don’t need to cite why it is excellent, works, and shouldn’t be changed and how the problem must be elsewhere. Because if it’s running, if it’s doing the thing you built it to do, if it’s scaling, if it’s handling errors and not losing them and if it’s taking a hit but keeps on running. Then that is all the…