Most of what I'm doing right now is playing catch-up to the way my life interferes with my work and causes sporadic bouts of effort followed by catastrophic loss of data.
As far as what needs to be done once I'm caught up, I'm at a loss; the complexity of the project requires a certain level of planning, mapping, and foresight that impedes the ability to truly innovate the system.
It's entirely a discipline thing, where I just look at the monolith of work to be done and get discouraged form working at all instead of rewarding myself for tackling the little micro-problems that get solved EZ-PZ that I don't even bother to document.
I have a constant problem of needing to visualize the logical structure by diagramming my code using flowcharts, and writing out doscstrings and wiki pages and coming up with a FSH to accommodate this documentation that I don't actually DO the work I'm talking about and end up having to look at my own documentation to get re-acquainted with the work to get back into it.
It's exhausting, but I'm trying to do better about backing up small work as I do it instead of sitting on a game-changing stack of commits then getting discouraged if I lose my un-committed work due to my volatile lifestyle.
The Gist
I acknowledge that I really don't know enough about the topics that I'm trying to grasp through my code. I also have a bad habit of forgetting things I've learned during a stroke of inspiration.
I intend to overcome these habits by documenting my successes and work so that I have something to point at when someone asks me what have you done,. One way I can achieve this is by simply not forgetting what I learn by at the very least following through with a bibliography of pages and posts that I reference when learning things beyond my grasp. It also lends to research credibility by quoting the original author of the work I'm ripping off.
Another improvement I'm trying to continue making is actually diagramming the logical though process using flowcharts as an infographical piece to make my documentation less tedious. This is being achieved through Yed, for which I intend to make a write-up on here soon.
One more thing I can do to make this project better is hardening-off what I actually have accomplished by making everything I have more newbie-accessible through top level consolidation of every major asset. Like, the Historic Data Client is pretty much proven but isn't ran as often as it should be; while the Graphical Credential Management system really needs some testing but isn't receiving it because there's no good way to access either of these sub-systems from the command line.
A Confession;
Most of what I'm doing right now is playing catch-up to the way my life interferes with my work and causes sporadic bouts of effort followed by catastrophic loss of data.
As far as what needs to be done once I'm caught up, I'm at a loss; the complexity of the project requires a certain level of planning, mapping, and foresight that impedes the ability to truly innovate the system.
It's entirely a discipline thing, where I just look at the monolith of work to be done and get discouraged form working at all instead of rewarding myself for tackling the little micro-problems that get solved EZ-PZ that I don't even bother to document.
I have a constant problem of needing to visualize the logical structure by diagramming my code using flowcharts, and writing out doscstrings and wiki pages and coming up with a FSH to accommodate this documentation that I don't actually DO the work I'm talking about and end up having to look at my own documentation to get re-acquainted with the work to get back into it.
It's exhausting, but I'm trying to do better about backing up small work as I do it instead of sitting on a game-changing stack of commits then getting discouraged if I lose my un-committed work due to my volatile lifestyle.
The GistI acknowledge that I really don't know enough about the topics that I'm trying to grasp through my code. I also have a bad habit of forgetting things I've learned during a stroke of inspiration.
I intend to overcome these habits by documenting my successes and work so that I have something to point at when someone asks me
what have you done,. One way I can achieve this is by simplynot forgettingwhat I learn by at the very least following through with a bibliography of pages and posts that I reference when learning things beyond my grasp. It also lends to research credibility by quoting the original author of the work I'm ripping off.Another improvement I'm trying to continue making is actually diagramming the logical though process using flowcharts as an infographical piece to make my documentation less tedious. This is being achieved through
Yed, for which I intend to make a write-up on here soon.One more thing I can do to make this project better is hardening-off what I actually have accomplished by making everything I have more newbie-accessible through top level consolidation of every major asset. Like, the
Historic Data Clientis pretty much proven but isn't ran as often as it should be; while theGraphical Credential Managementsystem really needs some testing but isn't receiving it because there's no good way to access either of these sub-systems from the command line.