I've been recently doing a lot of test-driven development at my new job, and one of the things I've noticed is that sometimes we will just run into snags, times when we hit a wall where it feels like we aren't making any real progress forward. There have been a few times now where we have gotten the code down to make the actual product work, but we spend a lot of time struggling to get the tests to pass and to really test the system in a way they we felt was good and proper. The trick is juggling the fact that we want to be a lean team that develops quickly but that we also want to write tests first that will pass when we implement these new features. Sometimes that last "making the test pass when they should" can be a lot more challenging that it ought to be, and it sometimes seems that we're put in a position where we need to choose between cutting corners or further increasing the risk that we ship late. To be honest I don't really have a right answer for all this, but in this post I'll think out loud about some ideas.
Recently I've been getting back into doing some algorithms coding challenge problems, and I really wanted to setup for myself a nice, comfortable coding environment that I could be proud of and that really followed the TDD principles of Uncle Ben, Ken Beck, and all the other gurus. Anyway, this is a guide for setting up simple, barebones TypeScript node.js projects for TDD. I'll show you how to set up a brand new node project, how to make your project a "typescript project", how to add mocha and chai in watch mode, and finally how to see your test results in a nice code coverage report. It's a lot I know, so let's dive into it!
I had developed a nice front-end website in Angular 7 for Kate From HR and was so excited that it was finally deployed live! However, I was having this strange issue where the routing was not working. The base url would work, and clicking on links would load the other pages. When I entered a url directly in the address bar though it would just bring me to a 404 page! Oh dear, it was bad times indeed. However, I figured out how to fix it so it's all happy days again!
This is just a proof of concept right now, but I basically want to create a little dashboard in ther browser that will follow live baseball games and, in real-time, show the probabilities of each outcome of each player's next at-bat. Then you can look at the numbers of your chart for who's about to be up and easily to compare it to bets available at your sportsbook, and this should then allow you to always bet at a theoretical advantage.
The posts on this site are written and maintained by Jim Lynch. About Jim...