The weeks leading up to a big event are stressful. Everyone’s trying to get organized, the lists are never-ending, new items are getting added daily, it can feel like you’ll never be ready. And maybe you won’t, and here is the day, and all you can do now is… Enjoy it, support it, work through it, roll with it, learn from it, and grow.
“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…
The same development problems, happen irrespective of the languages and platform you use; Delivery schedules Ticket Management Code Re-use Technical Debt API versioning Branching strategies Templates and Re-Use Data Access When we get past those problems, then the game will change.
Communities are everywhere you look. Software, sports, hobbies, gaming, building, bird-watching, coding, thinking, etc, etc. But are they communities? Do they all share the same characteristics and agree to the same norms? Or are they all thrown together with the hope that they someday might become a community, that one day they could come together? I’ve always looked at a community as not something you sign up for, but something that comes together, when you’re…
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.