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.
The problem with caching is it’s not always the right cache. When coding, cached data, is data stored in memory (on a file or some other structure) that makes retrieving constantly used data easier to get to. The goal is to reduce calls. Bad cache is data that’s not updated, but the user thinks it’s updated. Bad cache causes delays, wasted effort, and excessive troubleshooting. Bad Cache slows us down when it’s meant to speed…
If you’ve had 2 months to work on a project and you started it a week before and now have delays thrown at you or have to wait for others -the waits and the delays are not the problem. Waiting to start was your problem. Not planning out when to begin was your problem. Don’t blame the project on your planning.
If you’ve ever spent months, long months, serious months – to finish a project. To get through all the work, the meetings, the politics, the back and forth, the bugs. To see people not use it, or to see the work tossed out, is hard to handle. You put your everything into it for nothing to happen. Sure you learned and gained knowledge, but no one using it, that’s tough. If you haven’t had this…