“I need access to the system to get access to all data.” No. What you need is an endpoint you can call whenever you want to get only the data you need. Customers come to us with needs, in the middle there are always wants and stretching towards what they want (ask for the ocean and get the lake you need). The goal is to separate what they want from what they need but also…
When someone asks “How do we solve this?” And the solution is a vintage, time-tested, battle-hardened approach that works. You know it’s going to be a good day. I haven’t written multi-threaded code in a long time, but man when the opportunity popped up I jumped to it. I never met a thread I didn’t like.
Every now and again, we get overwhelmed with all we are doing and we need to find our reminder for why we are doing something. Is it our love for the work? Is it a particular aspect? What is it that makes you want to do this “thing” that right now is stressing you out? You might not be able to avoid everything, but sometimes we need a reminder as to why we’re there.
There is no better feeling than doing an alright job and having people see it as amazing. “But that’s not my best work? I have so much more I can do.” “This is great, you don’t need to go further… why would you do more?” People can’t tell the difference between your best and okay work -possibly because whatever you deliver comes through better than they could have imagined – so anything is great. But…
There is a reason why deployments go wrong. Because we don’t know the order of things to be done and by whom. Deployments are commonly used for release planning and code. But they apply to everything. Knowing the steps of when something starts, when something takes over, when you start doing a new initiative – is a deployment. Know the steps to nail your next successful Deployment, leave little room for confusion.