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.
Communities are big, they can have many people, and they are the accumulation of tribes. Tribes are cohorts within a community, they are carved out groups with needs, interests, and goals. Communities can have many tribes. Both are great to serve, contribute to, and work for, the key is knowing which one you are there for.
Get there. Show Up. Appear. Sign In. Call it what you want, but physically accomplish those goals. The first step is always the same, no matter what new thing you are working on. Get there.
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…
I came in this morning brimming with Creative Flow – ideas for posts were bouncing through my head and how to fix some persistent work problems. I could have started by doing my other work, but the pull was too great and I started writing them all down, getting them all out as fast as you can. I’m lucky because I have a job where I can do that for an hour a day, others…