TD Cafe #020 - AI & Development Teams

Wow.

It sounds like we're all in different stages of the process with me maybe at the earliest stage here.

[laughs] Wow.

What questions does everyone have? [laughs]

I think that's completely normal too.

Just we do for clients, we do like AI visibility.

So the first thing is, is your brand discoverable in AI? And then you move to a few more stages down the road.

Are you trusted in AI? And then the final stage is, are you recommended in AI? I think with adoption of tooling in development, it's the same thing.

Like, we go from that experimentation to a standard workflow, and I think that's completely normal.

Mike, I'd like to hear about your- ...

the standards you've put in place or the guidelines you've put in place for implementation.

One, one of the things that struck me as I started to use it for my own work [tsks] is [laughs] humility a bit, in that I was humbled.

Not that I f- think of myself as some awesome programmer, but coding for so many years, you have ways you do things.

It's the way I do it, it's the way it's always worked, it's sort of an industry accepted practice.

And then when I start to see code get generated a different way than I do it, I think you have to be humble in a way to say, to be open and look at this and say, "Is this actually a better approach than the way I would've done this?" And I found myself more and more saying, "Yeah, that probably is a good idea." And yet have to put some things aside and say to myself, "You know what? Yeah, maybe this is a little bit better approach to this problem than I would have typically done." And that kinda leads to like how do you put standards in place? The standards I would've put in place a year ago of how code should be structured or patterns that should be used, I think are very different today that I would write based on code that I've seen Claude generate for me.

And how do you get your arms around that?

It's funny 'cause I was just talking to someone about this.

Years ago, early in my development career, I was totally against using like IntelliSense and auto-complete in my I- IDEs, 'cause I felt the same way.

I was like, "I'm a developer.

I need to know how to write every piece of the code.

I can't have a tool finish a function for me or suggest the way to do something." And like I literally wrote my code in like Notepad 'cause I didn't want any of those IDE plugins that would help you as a developer.

Eventually I learned, hey, this is helpful.

I don't have to know how to write every single thing.

I can have it, the program help me.

And I think AI is a lot like that.

Wow.

It sounds like we're all in different stages of the process with me maybe at the earliest stage here.

[laughs] Wow.

What questions does everyone have? [laughs]

I think that's completely normal too.

Just we do for clients, we do like AI visibility.

So the first thing is, is your brand discoverable in AI? And then you move to a few more stages down the road.

Are you trusted in AI? And then the final stage is, are you recommended in AI? I think with adoption of tooling in development, it's the same thing.

Like, we go from that experimentation to a standard workflow, and I think that's completely normal.

Mike, I'd like to hear about your- ...

the standards you've put in place or the guidelines you've put in place for implementation.

One, one of the things that struck me as I started to use it for my own work [tsks] is [laughs] humility a bit, in that I was humbled.

Not that I f- think of myself as some awesome programmer, but coding for so many years, you have ways you do things.

It's the way I do it, it's the way it's always worked, it's sort of an industry accepted practice.

And then when I start to see code get generated a different way than I do it, I think you have to be humble in a way to say, to be open and look at this and say, "Is this actually a better approach than the way I would've done this?" And I found myself more and more saying, "Yeah, that probably is a good idea." And yet have to put some things aside and say to myself, "You know what? Yeah, maybe this is a little bit better approach to this problem than I would have typically done." And that kinda leads to like how do you put standards in place? The standards I would've put in place a year ago of how code should be structured or patterns that should be used, I think are very different today that I would write based on code that I've seen Claude generate for me.

And how do you get your arms around that?

It's funny 'cause I was just talking to someone about this.

Years ago, early in my development career, I was totally against using like IntelliSense and auto-complete in my I- IDEs, 'cause I felt the same way.

I was like, "I'm a developer.

I need to know how to write every piece of the code.

I can't have a tool finish a function for me or suggest the way to do something." And like I literally wrote my code in like Notepad 'cause I didn't want any of those IDE plugins that would help you as a developer.

Eventually I learned, hey, this is helpful.

I don't have to know how to write every single thing.

I can have it, the program help me.

And I think AI is a lot like that.