DEV Community

Discussion on: What Should be in a Coder's Toolbox?

Collapse
 
craser profile image
Chris Raser • Edited

Great post. Solid advice. I'd add: a test framework and a mocking framework. (ex. jUnit/Mockito/Powermock.) Getting proficient with these tools and using them will help you get things done faster, and radically improve the quality of your output. And it helps your team watch each other's back. If there are tests for your code, nobody's going to accidentally break it, and vice versa.

Collapse
 
samjarman profile image
Sam Jarman 👨🏼‍💻

Totally agree Chris, and I think my revised post will include a testing framework! (I've played with a few... I use RSpec daily, and have used many others, such as jUnit, Kiwi, KIF, XCTest and more!)

Thanks for bringing it up! Tests are SO important and I'm embarrassed I forgot them, if I'm honest haha.

Collapse
 
craser profile image
Chris Raser • Edited

Don't be embarrassed, Sam! This is a solid article. It seems to be aimed at Jr/mid-level web devs, but I've been doing this for 15 years, and I got plenty out of it. Cheers!

Collapse
 
codemouse92 profile image
Jason C. McDonald

Please pardon the little promotion here, but I actually wrote a testing framework, Goldilocks (part of PawLIB), for C++ that might work in scenarios where others might not. I wrote about it in the third part of this article.