Month: October 2019

October 10, 2019

Greg Thomas

Incomplete Experiences

Have finished feature are okay. Work that gets pushed off to the next sprint, it happens. Features that get canned, it’s not going to stop. All of these “events” happen that shift the development of what we are doing in the delivery of software. However, what is not okay, is to leave what half of the work has been done in the code that renders a feature partially unusable and/or changes the experience the user has when interacting with your product. When this happens, we deliver an Incomplete Experience to the end-user and that is the worst experience. We force

October 9, 2019

Greg Thomas

(Code)Blocked

You might not know it, but for a while, I was (Writer)Blocked. Couldn’t think of anything new to write. Was tired with what was out there that I was reading. Thought everything that had been said had already been said. Couldn’t get started. It made me think of how many times I sat down to start a new project and stared at the screen as it asked me what I wanted to name my class for the umpteenth time. Did I know what to call it? Did it sound any better than what it was before? Would it really matter

October 8, 2019

Greg Thomas

Stop the Memory Questions

No one knows everything about anything and if you work hard enough, you can figure out what they don’t know. For this reason, programming tests in Interviews are a lost cause because what they focus on is the application of memory and not methodical approach to solving something you don’t know. When someone doesn’t know the answer, I want to know what they are going to do to look it up; Google it. Podcast it. StackOverflow it. MSDN it. Slack it. Reach out a peer. Call a friend. All of these pieces are methods to solving problems that are constantly

October 7, 2019

Greg Thomas

Half of Nothing

The beginning of a Sprint and/or Release are exciting times, everyone wants to jump on every feature and story and get them done. Mid-way through either though, we start to realize that we are not going to be able to deliver it all and now we are left with a bunch of half-completed work items. It’s not a great feeling and it’s one Agile/Scrum is supposed to eliminate but still, there’s that pesky feeling we all have that “we can do it”. I know it, I get it all the time. I was having this conversation with a project manager

October 4, 2019

Greg Thomas

All the Things a Great Developer Can Do

If you’re looking to be a Great Developer, here’s what you need to get started. Need Project Management Skills Need Requirement Skills Need People Management Skills Need QA Skills Need to know what to automate and when to start automating Need to have an eye on the future Need to be able to sell your solution to your team and customers Need to be prepared Need to stay up late Need to wake up early in the morning Need to manage your time Need to budget your expenses Need to plan for vacation (we don’t need any more burnouts) Need

© 2025 Rambli by Greg Thomas. All rights reserved.