We have super standards. Our systems are more complicated. We’re not like everyone else. We have the most intense channel. If we go down, we are in trouble. You can come up with as many lines as you want but at the end of the day it still boils down to this – “Leading teams and delivering Code” – and if you aren’t doing those things, yes you are different, but the bigger question is…
So you probably shouldn’t be commenting on all that is wrong with it. You weren’t there for the late nights. For the stress-filled mornings. For the lack of documentation. For the tight-timelines. For the never listening customer. For the demos that had to be delivered. For the hotfixes and all the patches. But you’re here now. So take a second to check in on what you weren’t there for, before passing judgment.
The Happy Scenario gets a bad rap because it’s easy, it does the bare minimum and the customer doesn’t really want it. Who would want to buy it? No one… and that’s the point. The Happy Scenario isn’t for the customer, it’s for the developer who’s trying to get that new library up and running, it’s for the QA tester who’s trying to validate their first automation test case or maybe it’s for the Product…
I’ve gone through three versions of Rambli over the past 3 – 4 years. Who knows maybe this will be the one. After having completed a marketing course (whole other post, but I highly recommend it) – I decided to give things a facelift that boiled it down to all the things Rambli is; It’s about Delivery, Drive, Initiative, Leadership, and Growth. It’s about doing it without all the extra fluff. There is no magic…
So here it is, the culmination of that sweet spot of what you HAVE to do, what you NEED to do and what you WANT to do all being perfectly aligned in that perfect sweet spot where you have all your external factors under control, what you NEED to do is driving what you WANT to accomplish. It’s here that all our goals are being accomplished, what we deliver attuned to what we WANT to…