If you want to be a developer, you have to read
This is something that I've thought about a lot during the (roughly) 30 years of my career. If you want to be a developer, if you want to write software you have to read! Whether that's a project's official documentation, the code, the docblock or inline comments, or related places such as forums like Reddit and Stack Overflow - you have to read.
Sure, AI can summarise content for you, and can help with projects that have poor or no documentation. But, whether you use AI or not, there's no getting around reading. There are no shortcuts.
In this episode, I go into depth about having to read as a developer, explain how it's unavoidable, and also why reading is a good thing.
Sure, AI can summarise content for you, and can help with projects that have poor or no documentation. But, whether you use AI or not, there's no getting around reading. There are no shortcuts.
In this episode, I go into depth about having to read as a developer, explain how it's unavoidable, and also why reading is a good thing.
Want to grow your knowledge further?
Check out the books below, where you can grow your web development skills in a very focused, very hands-on way.
Check out the books below, where you can grow your web development skills in a very focused, very hands-on way.
Hosted and produced in Bundaberg by: Matthew Setter.
Website: https://matthewsetter.com.
Follow me on: LinkedIn.
If you like the podcast, and want to support it, how about buying me a coffee?
★ Support this podcast on Patreon ★
Follow me on: LinkedIn.
If you like the podcast, and want to support it, how about buying me a coffee?
