Still struggling. Still falling over. Still ticked off. Still haven’t figured it out. Still not sure where to start. Still not sure what to do next. Still stuck. As long as you’re “Still not waiting to start” you’re much further than everyone else that is behind you.
Building some conditional logic is not Artificial Intelligence. Storing customer preferences is not Machine Learning. Copying your on-premise code to a cloud Virtual Machine is not Cloud Services. Adding more memory to your server is not Scaling it up. Your role is to make sure your customer knows what you are and what you are not building for them. Don’t hide your delivery behind buzzwords.
There are always two competing agendas occurring at a Project Kick-Off. The Customer I want it yesterday, here is everyone you need to meet, start delivering. You (the Developer) I’d like to tell you how we’re going to delivering your project. From the onset, they are in disagreement because one is driven by immediacy and the other by a pragmatic approach. The developer wants to make sure they do it right for the customer the…
No not the experience and/or qualifications you need to get a “job”. I’m talking about the experience you feel when you try something new for the first time. What’s the expectation that a customer can be up and running with your product in how you have shown it after they purchase it? One Hour? One Day? One Week? Does that line up with the reasons as to why your customer purchased your product? I run…
Yesterday’s unit test results. Last week’s build breakage. Last month’s bad update. Last year’s roll-out that went sideways and didn’t make it in until the third try. These alone aren’t bad when they occur, but when we hold onto them, reference them in meetings when someone wants to try something new, test out a new idea or approach and use them as justification for not implementing change. This is when they become our biggest failure.…