Articles for category: Delivery

July 7, 2016

Greg Thomas

Old vs New

How often do you get a project and start to build it against the patterns you already have in your brain?  Or you start to review against the patterns that you have in your head that always worked before and should work now as well? Too much? All the time? Never? I don’t know if there is a balance, but I do know, to this day, whenever I start to work on a project that I have done more than twice (why twice, well I do it once to learn it, twice to perfect and thrice to contemplate the path

July 4, 2016

Greg Thomas

Defining your Code Velocity

Some people, generally do some things faster than others and vice-versa. You can estimate all you want and task it out all you want, but at the end of the day, that’s what it comes down. Velocity, when defined, is the speed of something moving in a given direction. The faster someone goes is the easiest (and generally most obvious) way to measure velocity. But it’s not the only way… accuracy redundancy readability transition understanding reduced bug count These are all factors that can shape your velocity and show that what you are shipping is more than simply code before

June 29, 2016

Greg Thomas

Can you handle the Change?

Should I apply when my skills don’t quite line up to what is being asked? I have .NET, they want Java? I do Development but want to be a QA? I’m more Agile than Waterfall? Do you have an aptitude to change and learn without disparaging that which you don’t know? If yes, apply, if not, probably not the best idea for you because you know it is going to be different, you know there are going to be hurdles and hills to climb and you know it is going to take you out of your comfort zone. So before

June 10, 2016

Greg Thomas

What if Developers had to Sell their Code?

What if you, as a developer had to sell your code? I’m not talking about Developers building a funnel and doing trade shows.  But what if the last step in a customer purchasing your software was for the Developer to sell it to them, in essence, the developer was the Closer for the deal. What would change in not only how you wrote it but how you designed it? Would you put in all that “future proofing” and extensions that might never get used? Would you spend more time in designing the UX to make it easier to use? Would

June 2, 2016

Greg Thomas

The Prayer of the Demo Gods

On this day, when I must demonstrate my code in front of others with the hopes that they accept all that I have built, I say this prayer in hopes that my code will work flawlessly.  I’ve done many a demo, joked about the demo god prayer, but never have actually figured out what this prayer would be… until now… Let this code compile, In not an hour, but a little while. Allow this application to run with speed and zest, as this will keep users glued to my test. If my code blows up in my face, do it

© 2025 Rambli by Greg Thomas. All rights reserved.