Why is tests so boring and how can i get over it?

Since no one is jumping in to give an answer I will take a stab at your questions.

TDD: Yes, it is a pain. I think it was on the Ruby Rogues podcast where they were talking about how hard it is to do TDD when first starting out (sorry, no clue as to the episode). As a new dev, you are often in the dark as to if you are really covering the use case you are testing for, you may not even have a good grasp on how to write the code the code that would produce a good test. That said, TDD is also pretty cool...

While writing code twice sucks, there is this really cool thing that happens. Once you can get a good test down and go through red, green, refactor, you have that test forever. Every time you type rspec in the terminal afterwards, you verify that you didn't make some small change off in left field that somehow tied back to that little bit of code and subsequently flubbed up that part of the app that you just knew you had working like a charm. In fact, if you are doing the Odot series and running your full test suite, not just the individual files like Jason does, you will catch several issues long before Jason finds them in the videos.

Again, I can't really recall where I picked up this advice and, as such, can't vouch for whether or not it's good practice but here's my game plan: Start with integration tests. Try to cover the action the user would take as best as you can. Write code to get to green. Don't worry about writing code first and then going back to make your tests. Heck, don't worry about making a whole branch and writing tons of code without tests but do try to go back at some point and add the tests in. Taking on TDD in small, steady steps will give you the freedom you want when starting out while still easing you into writing good tests. It will also serve to drive home its benefits and allow you to realize TDD as the tool it is, not just the extra pain in the ass step of writing code.

Hope that helps to lighten the load a little! Cheers!