Yesterday, I wrote about finally beginning to work on not
just an app, but an entire app ecosystem. As with anything, everything starts
with giving it a name. A name is everything isn’t it. In my earlier post, I
spoke about the relevance of meaningful names making code. If I am the kind of
guy who spends so much time simply naming a basic variable in a simple piece of
code, I should give a proper name to this app ecosystem as well.
While naming, there are two types of name. There is the
placeholder name, and there is the actual name that you use for marketing. As
an independent businessman, I must appreciate and more importantly respect the
value that marketing brings into day to day business activities. So, for now, I
don’t have an actual marketing name for my ecosystem. However, a placeholder
name, I will go with would be ‘Project TD’.
What TD stands for, should remain in my own head for now. I
am weird that way ;)
Moving on, any app ecosystem, especially a technology
system, should and must follow the Software Development Life Cycle. Sure, a guy
like who hate using established systems such as SDLC. It’s boring, and it
sounds dull because some folks designed such things, and they were probably not
cool. I almost always take the road less taken, the uncharted island attracts
me more than an established. However, I admire and respect what others have
done, cool or not cool. Respect must be given, where it is due, no matter how
much I might not like on a personal level.
So yes, TD will also follow the SDLC cycle, but I will make
changes as necessary. A development model that does not adapt to changing
scenarios is a dead one. I don’t want my development model to die, obviously. Here
is the standard life cycle that I will be using.
- Prep work – includes risk analysis
- Design – loads and loads of drawings and
diagrams. Also includes presentation, mostly to non-tech people.
- Development – Loads and loads of typing.
Referencing external sources, books, mentors. 4 monitors, with simultaneous
coding on at least 2 computers.
- Testing – Engaging with lots of different types
of users, everybody from tech savvy users to folks who are turning on computer for
the first time. A true architect and developer never forgets his users because
that is where the money comes from.
- Deployment – Including a lot of security stuff,
discussing encryption systems and networking realities.
- Repeat and Rinse.
While all this cycle stuff is happening (or will happen),
perhaps the most important question is why do all this? More importantly, why
do this at all?
The answer, it boils down, to the simple life concept of ‘show,
don’t tell’. Even when I was a kid, I preferred to show stuff, rather than
explaining stuff. Interacting with the five senses is perhaps the best way to
get some work done. This blog (and all the other things I have done and shown
for the past five years) has helped some score some serious amount of deals,
and that means colour green. While I am already designing end to end solutions
for clients, I am yet to train people on end to end solutions.
Posts such as this one, and many more that will follow, will
help me keep track of progress. As always, I also hope that some of the things
that I write on blog will help others who need information. Hopefully, at least
one of these goals will be achieved.