SPDCA: Code design.

So... there are a lot of ways to program. Arguably infinite, if we want to get math-y. But most of the time there are ways, and there are better ways. Programmers call the "bad" ways anti-patterns, meaning that they are patterns or trends in software development that have less-than-desirable eventualities when it comes to the software engineering process.

That said, idkfa has a few anti-patterns, that is, bad choices I made when building idkfa. And that isn't to say that something I've put together is broken or dysfunctional, it's more than if I want to move forward with certain features, choices I've made in the past make it unreasonably difficult to proceed.

Case in point: the "mobile" version of idkfa I tried putting together a while ago. It got so far, only to realize that the amount of work I would be putting into getting a mobile version of the site would be ridiculous. This is because I designed idkfa in the same way that I did back in v2, that is, I had the same code segments that did the underlying logic ("How many posts are in this section? Are you logged in?") also do the code display ("Put this section title next to the post count..."). This meant that for doing something like a mobile display, I would have to create two versions of the same function, and the new version would duplicate both the logic *and* the display, rather than making use of the same logic, and just changing the display slightly.

It's going to take a while, but I think in order to proceed with some of my plans, I have to rewrite a good portion of the "rendering" parts of idkfa. It will mean I will have better code design in the end, and make it easy to eventually write things like mobile versions of the site, or have more powerful choices in display mechanisms (as well as switching between them).

I'll let you know how it goes. More just writing this to collect my thoughts before I start going nuts on the problem.