The idea of lone wolf hacking away in the darkness of the dungeon slowly falls apart in a few weeks at the most. Writing your hobby code is no where glamorous.
Even if you are not as bad as myself,a self declared blue-moon start-and-stop brogrammer, it will definitely happen that you will shelve what ever you are doing and come back later to it again.
This is where a version control system really comes in handy. But the issue is that most of the times you will leave when even your ideas have not completely blossomed into code.
So more than version control, a project tracker which can track status of action items and hold action items under a group representing a single idea is very important.
For example, the project which brought me back from the dead is nearly two years old. I did have a skeleton proof of concept ready in last December and showed it to a few folks. I again started on it in April for nearly two weeks.
In this scenario only way to keep track of what is happening is to religiously document your ideas. The generic idea is that you should be able to pick up the threads within a day or two and get started with whatever you were doing.
This means just like any big organization, you should also treat your self as a cog in a machine. You should always leave things at a place where it can be hydrated with minimum efforts and restarted again.
I have been trying options like Asana, and Trello and I will definitely recommend giving these a whirl. both are pretty good and I remember that their being mobile based can also be deciding point for a few who happen to read this.
But for me, tying things to code and iterations was the most essential part I was looking at. And it leads me (again) to Visual Studio Online. You can really manage your work withing sprints and have a meaningful product backlog. May be it is me but I have always enjoyed the scrum meetings of one where I report progress to myself and then raise questions and answer them myself.
In this particular case, I just started with the pending and planned items in the product backlog and slowly things started making sense. I was almost able to hit the ground running. I am not at a place where I can add more items to the overall product backlog and hopefully when I get back to this the next time, I would start from a newer baseline :D
Let's talk about the dev and deployment environments in next few days !!! I was not doing much for balancing their mutability but that is the next piece of puzzle that needs to fall in place if you really need to follow the doctrine of cold-start.
Even if you are not as bad as myself,a self declared blue-moon start-and-stop brogrammer, it will definitely happen that you will shelve what ever you are doing and come back later to it again.
This is where a version control system really comes in handy. But the issue is that most of the times you will leave when even your ideas have not completely blossomed into code.
So more than version control, a project tracker which can track status of action items and hold action items under a group representing a single idea is very important.
For example, the project which brought me back from the dead is nearly two years old. I did have a skeleton proof of concept ready in last December and showed it to a few folks. I again started on it in April for nearly two weeks.
In this scenario only way to keep track of what is happening is to religiously document your ideas. The generic idea is that you should be able to pick up the threads within a day or two and get started with whatever you were doing.
This means just like any big organization, you should also treat your self as a cog in a machine. You should always leave things at a place where it can be hydrated with minimum efforts and restarted again.
I have been trying options like Asana, and Trello and I will definitely recommend giving these a whirl. both are pretty good and I remember that their being mobile based can also be deciding point for a few who happen to read this.
But for me, tying things to code and iterations was the most essential part I was looking at. And it leads me (again) to Visual Studio Online. You can really manage your work withing sprints and have a meaningful product backlog. May be it is me but I have always enjoyed the scrum meetings of one where I report progress to myself and then raise questions and answer them myself.
In this particular case, I just started with the pending and planned items in the product backlog and slowly things started making sense. I was almost able to hit the ground running. I am not at a place where I can add more items to the overall product backlog and hopefully when I get back to this the next time, I would start from a newer baseline :D
Let's talk about the dev and deployment environments in next few days !!! I was not doing much for balancing their mutability but that is the next piece of puzzle that needs to fall in place if you really need to follow the doctrine of cold-start.
No comments:
Post a Comment