Articles for category: Delivery

The Importance of Design

Design without code is not a great design; it’s airy, never been proven, just there, who knows what it could mean. Design is important, whether you do it with AI or on your own; there is value in that work, and it is largely unhidden. If it fails, everyone knows it was a bad design. If it works, no one ever mentions it again. Some of the best code I ever wrote was a simple design to send out invoices every day to customers to get our money.  It ran for years without ever needing someone to coddle it or

Knowing your Code Context

There has never been a more important time to know what your code does and how it works. It’s no longer about knowing more than the other person who sits beside you.  That competition is over; there are systems out there that will run circles around you. It’s about knowing the context of what your code does, what it talks to, what it interfaces with, and why it retrieves data in a certain way. Everyone is going to AI for answers, and the best piece of information that you can add that AI cannot is the context to your code.

Your Daily Learn

What is your daily Learn? Don’t leave it to the weekends, it won’t happen. Don’t leave it to some great big 8-hour marathon, it won’t happen. Don’t leave it till the night before, you won’t retain anything. Learning is still a process that we iteratively go through and need to not forget how to do. YouTube, Blogs, Udemy – there is so much out there – taken in increments, you’ll be much farther with what you do each day in your growth if you start with a plan today.

Yes, But What does it do?

If you can’t tell me what it does, then it doesn’t matter what the fix is, we have a much bigger problem. And that is, we don’t know what it does. Whether it’s you, AI, or Fred at the coffee shop, you need to know what it does. Base metric.

How your Team is using AI

As a leader, if you are not asking yourself this question, you are not leading your team into the next era. Are they coding with it? Are they writing manuals? Are they letting it work for them? Is the team sharing skills? Are we all using different back-ends? You don’t have to have all the answers, but you need to be asking all the questions; someone else will, and they’ll be the ones people will be looking to lead the team.