The rabbit hole of abstraction

So, I've really been digging abstraction and interfaces lately. I'm like, "Hmm, I'll probably want more than one way to do this in the future, so I'll abstract that bit out so I can inject the dependency or whatever." Because I've been so focused on writing tests lately, I wasted a few hours today. I got to this point where I was confused as to which Interface/class I was injecting into another class, and I realized I'd abstracted the same thing about three levels deep. I kept being like, "I'll handle it with this next abstraction," but I never actually was like, "The buck stops here."

Anyway, just a bit of frustration, mostly because I felt so productive yesterday and most of my coding today seemed for naught. Though, I think I learned a valuable lesson about making sure I don't lose sight of the bigger picture.

I think I'll start using EclEmma pretty soon to help keep track of what I'm doing with my tests.

More TDD

I'm curious if anyone reading this has any experience with writing tests in Eclipse. I've been using Junit, and like it mostly. I find it helpful that I can create a new testing class and specify which already-existing class is to be tested; (and that it automatically populates the test class with all the public methods.) I try to make sure I have all my public methods under test, but I know that sometimes I create a public method and then forget to add it to the testing class. Is there a way to, say, update a testing class so that it will re-populate, adding any uncovered public methods? I suppose I could look into some sort of test coverage plugin.

My current focus is re-getting the display portion of my game up and running. I think I'm pretty close, though when it's there, I won't really have anything to show for it, other than a testing suite with all green checks. (Though, I should be able to create a window and display some dummy information)

Some things that are on my short list to implement: dynamic resizing of the window, zooming in and out using the scroll wheel, etc.

Gainful employment, graduation, and TDD

A lot has happened since the last time I posted:

1) I graduated from Eastern Michigan University cum laude

2) My grandpa died during exam week, and I was able to thank him for his generous contributions towards my college expenses, assure him I'd graduate, and that I had some job interviews lined up.

3) I amazingly got a job after only a few phone interviews and 2 in-person interviews. The people I work with are pretty amazing and I've been employed since January 11th. I'm only just now starting to feel like I'm getting the hang of it; though I'm still learning so much every day.

4) I grew frustrated with being so exhausted in the evenings. I stopped working out, I subscribed to too many shows on Hulu. I brewed a few batches of beer

5) I became interested in test-driven development, while at the same time realizing that my x-com codebase had again grown very unmanageable.

6) I created an account at git-hub and set up gitgui with my eclipse install

7) I started rehashing my game using TDD. The going is slow, but I think it's very worthwhile.

8) I somehow borked my git-hub security hash. (I still need to fix this)

9) I started working and running again.

This is it for now. I'm still around, I still read rec.roguelike.dev, I'm still working on my game. It's just taking me a while to adjust to having a career job.