I think you're mostly talking about regularization stages (i.e. tuning training data against some that is partitioned off in the
validation--not testing-- set). Again, this could all be done under the hood in a built in / off the shelf program or algorithm. If you have access to such an algorithm, and aren't pursuing this for pedagogical / learning purposes, then you should be good to use the built-in stuff. It's really a judgment call. Sometimes people recreate stuff from scratch for no good reason.
- - - -
The more I think about it, though, your question could be more general: why bother with validation at all? I suppose in this context validation is an ML concept. There is very nice treatment of this in the book
Learning from Data which is a great purchase for $30 if you're in the US (NY?). This is all discussed in chapter 4 "Overfitting", for reason. In general we worry about overfitting, and so a lot of different techniques have been developed to minimize it. Regularization parameters (e.g. Tikhonov) are one way to deal with overfitting in linear models. Having a separate validation set is another way of getting dealing with overfitting. You're basically leaving out some of the training data, and getting a 'sneak peak' of the benefits of using the test data, except you're not using the test data so it doesn't get contaminated. There are other techniques, and ways to combine techniques. But the idea is when you have a highly expressive / powerful model, you need to be deeply concerned about overfitting.
- - - -
When you have the time and interest: I really like the materials from MIT... 6.00.1x and 6.00.2x on edx are terrific intros to python and CS and free:
https://www.edx.org/course/introduction-computer-science-mitx-6-00-1x-11
https://www.edx.org/course/introduction-computational-thinking-data-mitx-6-00-2x-6
FWIW, I actually built a texas hold'em poker MC simulator from scratch, entirely in Excel a few years ago. (It was to help settle disputes with a certain person over odds of getting some more complicated hands -- the direct combinatorics approach started to get tedious and error prone.) The simulator worked but the process was brutal and I realized I didn't have the right tool for the job. This was one of the final straws that pushed me toward proper coding.