That Code Smells!

I'm building an app that is reliant on a calendar. I'm using the excellent JTAppleCalendar control as my jumping off point. I can't say better things about the control. It's relatively new, infinitely extensible, easy-to-grok, and actively maintained. Jay has been super responsive answering my questions.

Anyhow, I've been strapping on quite a bit to the calendar in order for it to work with the data layer and the core functionality, which I'll only go into once I have something to release.¹ I've found myself adding parameter upon parameter to methods that configure and set up the calendar’s main view and calendar cells. It got pretty ugly. This sounds really obvious now, but passing in a single struct could make the code much easier to read. I’m beginning to recognize code smells and am motivating to find solutions to alleviate them.

This is very embarrassing to write, but in the past, I wouldn’t have cared about code quality, as long as my application worked. In addition to not knowing what the hell I was doing, I had serious depression with my past situation. My strong dislike towards the Microsoft stack didn’t help.

Nowadays, I’m in a better mental space and I’m using my favorite technologies on my favorite gear. Writing good code has become a goal that brings me joy. This is the first time I’ve really locked an ecosystem I love, am devouring all available resources. The future is bright, and I’m excited to share my first app with the community.