Menu
Sign In Search Podcasts Charts People & Topics Add Podcast API Blog Pricing

Jamie Taylor

๐Ÿ‘ค Speaker
341 total appearances

Appearances Over Time

Podcast Appearances

Coder Radio
640: The Modern .Net Shows' Jamie Taylor

Rather than going, hey, AI, build me the thing.

Coder Radio
640: The Modern .Net Shows' Jamie Taylor

It's like, here's all of the information you need and maybe some research stuff.

Coder Radio
640: The Modern .Net Shows' Jamie Taylor

Now go build it, right?

Coder Radio
640: The Modern .Net Shows' Jamie Taylor

Which sounds like a really big lofty task, but actually spec kit helps you to do that by

Coder Radio
640: The Modern .Net Shows' Jamie Taylor

If there are gaps in what you're telling the LLM, it says, hey, go to Google or your search engine of choice or look in the code and fill in the gaps of knowledge and tell the user what you've found, right?

Coder Radio
640: The Modern .Net Shows' Jamie Taylor

So it's kind of a bit of both.

Coder Radio
640: The Modern .Net Shows' Jamie Taylor

The idea is that we live in a world where the code is king and the specification is kind of this woolly thing that somebody else writes, maybe a business person, maybe a BA of some kind, maybe a project manager of some kind, someone who probably doesn't know much about the technology you're going to implement.

Coder Radio
640: The Modern .Net Shows' Jamie Taylor

And that's a good thing and a bad thing, right?

Coder Radio
640: The Modern .Net Shows' Jamie Taylor

We always want to try and

Coder Radio
640: The Modern .Net Shows' Jamie Taylor

delay the technology decisions until the last minute because then that gives us more options to play with.

Coder Radio
640: The Modern .Net Shows' Jamie Taylor

So in that respect, having someone who isn't technical, who isn't an engineer of some kind, having them write the spec makes that easier because they don't know what an ORM is or what programming language you're going to use, right?

Coder Radio
640: The Modern .Net Shows' Jamie Taylor

So you get to make that decision.

Coder Radio
640: The Modern .Net Shows' Jamie Taylor

And we've done that for a very long time where we'll write a spec and then we'll build the feature.

Coder Radio
640: The Modern .Net Shows' Jamie Taylor

Well, this is actually flipping it on its head, where what you want to do is you want to keep the specification in source code, because then you can see where you've come from.

Coder Radio
640: The Modern .Net Shows' Jamie Taylor

So rather than having your Jira tickets or your Trello tickets or whatever separate, you keep it all in-house in the code base.

Coder Radio
640: The Modern .Net Shows' Jamie Taylor

And then you can see how we got to where we are.

Coder Radio
640: The Modern .Net Shows' Jamie Taylor

So every time you build a feature, there's a bunch of files that you create with SpecKit that outline how that feature is meant to be built.

Coder Radio
640: The Modern .Net Shows' Jamie Taylor

And then you finish that feature, merge back to main and carry on with your life, make another feature, merge back to main.

Coder Radio
640: The Modern .Net Shows' Jamie Taylor

And then there's this like a record of who built what and when and what was the decisions.

Coder Radio
640: The Modern .Net Shows' Jamie Taylor

Almost like having an ADR, like an architecture design record.