Working alone on a project seems like trying to reach the bottom of the sea from time to time…
That’s why we have to pay attention when making some decisions regarding modularity, and the general organization of the code. By using the right tool at the right moment, and making sure that it’s easy enough to use, one can avoid everyday traps that I’ll call “Psychological steps”.
A psychological step is something you know how to resolve, yet avoid to do for some time (up to some months).
In a general case, you can design one generic (modular) class and get rid of several psychological steps at once.
ex: I hate coding user interfaces (though I love to design’em), in order to speed up my development process I created a small modular class to build a basic interface (and the controller with it). It uses a simple list
conclusion: By taking one afternoon to design a modular class for my UI I was able to get 5 different UI panels working with a minimum of tweaking.
BUT! and this is a big BUT (absolutely no jokes included).
I find myself in a situation where my suppa modularized UI class is actually the psychological step!
ex: I’m working on the save menu right now, but the original conformation of my UI general class doesn’t accept as many buttons as needed to operate the menu…. NoooOOOoOoOOOooooOOOooO. The psychological step here is: i don’t like coding uis, i have to design a news system and make it work with the original modular class.
you’ll tell me “well all you have is to do it right?”, right but one cannot underestimate the importance of morale while working alone. As I am in an ongoing application for a job as a tech documenter (and god knows it takes time), so my morale is fairly low (I was supposed to get a part-time job for september XD).
So has anyone tips to overcome these self-expending morale difficulties?
Should I modify my modular ui class or add an independent layer on it?
Is blue my favorite color?