An Effort to Reorganize My Workspace, Showcase and Everything in between
It's actually an old mission, a long pending mission to tidy up all my digital workspace, showcases, and everything in between. the long-time-dead blog, cluttered GitHub repositories, messed up cloud storage, tons of duplicate files, digital garbage and evidence of things I've done that should never exist.
From the background above I just use words cluttered, messed up etc. It does show the situation but doesn't tell the urgency. In these sub-parts, I try to express how they contribute to the unright things of me.
I'm a programmer but don't have any public repository/published code, a mature code that others can get inspired with, let alone a complete app/lib that others can use.
I claim myself as a person who is experienced enough and likes to read but I don't have any published writings in the form of anything that expresses my thought or express my opinion about something relevant to my knowledge/experience.
When I think I have an idea, I usually do Self-PoC, and it's often done partially in code and another part only in the mind. With the model, I can confirm to myself it is legit proof while knowing that in the future I can guarantee that I will forget those parts in my mind.
When I need to show my off-office work, I don't have anything real to put in my showcase, it's all over the place, local disks, minds and even scratch paper. And this repeats.
and so on.
Risk & Impact
Here I'm trying to identify the risk and impact of those unright things above, to model how it will affect me and probably my life.
There's a possibility that some audience will see what I claim about myself as a false premise.
There's a possibility that some audience will see that I'm exaggerating the claim.
There's a possibility that some audience will see that I'm the kind of person who likes to keep everything to myself.
There's a possibility that some audience will see that I'm the kind of person who doesn't have good responsibility with the work artifacts, let alone doing documentation on them.
Companies won't get a meaningful conclusion from a false premise. Thus, they won't buy pig in the poke, i.e. not gonna hire me.
Companies, even they like to hire me. They will be in doubt. Thus, I won't get my salary expectation
Companies will value me as a nonteam player, or at least not a good one. Whether or not they hire me, my value just got dropped.
Companies will think that non-responsibility with the work artifact is very bad for the team or even the whole company, and should be avoided. And of course, company won't take the risk.
Breaking Down the Problem
From the above description, we have a broad problem space and cross domains and of course, it has never been a good idea to try to solve it as a whole. We definitely need to do dividee et impera against it. The obvious option would be by activity, which gives us three problem sub-space:
Coding activity: What do I need to do/have, to be a productive, consistent, and being better and better time-to-time programmer?
Writing Activity: What do I need to do/have, to be a productive, consistent, and being better and better time-to-time writer?
Self-PoC activity: What do I need to do/have, to be a proofer for concepts?
We have broken down the problem into specific domains which hopefully are easier to solve. To keep them separate, I think it'd be better to try to solve the above problems in separate articles.
If you happen to read this and have a thought on how I should solve my problems please tell me what you think.