New teams… Offer new chances. New possibilities. New directions. New opportunities. New paths. New ideas. If you’re willing to embrace it.
We all have them, and they aren’t people – it’s the one thing that stops you in your tracks and frustrates you to no end. For me it’s TLS and certificates, it’s a pain, I’ve tried learning it over and over again. I have bashed my head against the table on this subject over and over again. I secretly hope it is replaced by something much simpler – i.e., SECURITY_ON and SECURITY_OFF Other people get…
If you’re building tools for your users to use. It would be important to ask them… How are they going to use it? What will make them wake up every day and use it? Why do they need to have this? How will it save them time and why? All these questions are about your users and what they need from it. We sometimes think we have the answers, but we often don’t. We have…
We don’t often ourselves this question, but it is a valid one. Is it a dumping ground? Is there a structure to it? Do you want to be able to deploy to a new environment with a script? Does each team need a sandbox? Do you want teams to have sandboxes? How long will it live? All these (and many more) are questions you should ask when setting up your repository that go beyond “New…
What delays your projects? If you work outside, the weather is a monster factor. If you need internet, not having a connection is the big issue. If you don’t have the right tools, you’re fighting against that the entire time. All these are yes or no answers – you either have it or you don’t – call these fixed delays. Variable delays, are the unknowns, the unquantifiable, the questions that arise from people not sure…