This video explains that "code katas" are simple coding problems that help programmers practice and improve their skills, similar to how martial artists practice karate forms. The speaker, who learned about code katas from Dave Thomas, a co-author of the Agile Manifesto, discusses how these exercises allow developers to focus on their work habits and build new ones, like using test-driven development. He emphasizes that practicing code katas can help programmers become better at designing new code and writing tests.

Key Takeaways

Code katas are simple coding problems designed to help programmers think about their work habits and build new ones.

The idea of code katas was inspired by Dave Thomas, one of the pragmatic programmers and a signature of the agile manifesto, who observed his son practicing karate.

The speaker found that studying solutions to code katas significantly helped him improve his skills in designing new code and tests.

Code katas can help developers adopt test-driven development (TDD) as their default style by building habits like running tests often and building functionality in small slices.

Practicing code katas is a way to develop disciplined practice away from complex production code.

0:00 Code carters are interesting problems to

0:03 solve, yet they're simple. Simple enough

0:05 that it doesn't take all of your brain

0:07 power just to get to a solution, which

0:10 means you've got some capacity left to

0:12 think at this meta level about the way

0:15 you're working and what your habits

0:17 actually are. And then of course you do

0:19 a code carter repeatedly and

0:21 deliberately to build up new habits. I

0:25 first learned about code carters from

0:27 Dave Thomas. He's one of the pragmatic

0:29 programmers. He's written lots of books

0:31 and he's one of the signatures of the

0:32 agile manifesto. So he got the idea when

0:35 he was watching his son practice karate.

0:38 They were doing these Carter exercises

0:41 where they they train moves all together

0:43 with the whole class doing the same

0:45 thing. Dave Thomas thought about how

0:48 programmers train or mostly don't. And

0:51 he realized that we could do with some

0:53 of this disciplined practice away from

0:55 production code. At the time I was

0:58 fairly junior as a developer. I was just

1:00 learning about unit testing and

1:02 test-driven development. I was very keen

1:05 to improve. So I began to work through

1:07 some of these code carters and looking

1:09 at solutions to them I found on the

1:11 internet by other people. And I realized

1:13 that studying like this actually helped

1:15 me a lot to rapidly improve my skills

1:18 for designing new code and tests. So I'm

1:21 a huge fan. I've been using these

1:23 exercises personally for more than 20

1:26 years at this point and I still get

1:28 value from practicing. Most developers

1:31 spend a lot of time building new

1:32 functionality in complex systems and the

1:35 best approach in my opinion is to use

1:37 testdriven development. If that's not

1:39 yet your default style, you'll want to

1:42 build some habits so it will become your

1:44 default style. And that means habits

1:46 like running the tests often, building

1:49 functionality in small slices, test by

1:52 test. And code carters can really help

1:54 you to learn to do

How Expert Programmers ACTUALLY Practice Coding

Name: How Expert Programmers ACTUALLY Practice Coding
Channel: Continuous Delivery

Continuous Delivery

Key Takeaways

Start a conversation

How Expert Programmers ACTUALLY Practice Coding