How to Write a Quick and Dirty Tool

If you are new to programming, certainly something like Python or maybe.NET is probably a good place to start. It has that nice immediacy of giving you feedback quite quick. If you get an off by one error, it's going to throw an exception. You don't have to worry about memory management. It's harder to write bad code than if you write everything in C or C++. Instead of waiting to become an expert and then going and write a tool, you actually write the tool as or you start writing tooling as a way to become an Expert. Did I get that right? Would you agree with that?

Transcript

Play full episode

The AI-powered Podcast Player

Save insights by tapping your headphones, chat with episodes, discover the best highlights - and more!

Get the app