Decoding parenthood... The Software Engineer's way
Well, parenting is tough. It is. It really is. The advertisements that you generally see of happy babies with their nappies on or happily eating their Cerelac is just a moment captured on camera after hours of shooting with them. One has to re-wire their entire schedule and hardware (brain) around one soul to be successful. I have decided to pen my own experience and tie it to the fundamentals of what I do at work everyday and make sense to the all the melodrama surrounding this incredibly easy process.
1. You start from ground up!
In contrast to most of the IT projects we tend to be a part of, we start from ground up in this case. This becomes easy as we have a finished "product" in our hands with all the features built in. The product (would now be referred to as "baby") has all features in beta version wherein we can influence some aspects of the baby throughout. The features are usually standard with some variations but this guide would apply to all.
2. Inheritance
This is one of the fundamentals when we come to the object oriented programming, a programming paradigm that enables us to understand the way the objects usually interact with each other, now this stands true that the programming fundamentals were derived from the real life but once we get entwined in all the software lingo it is important to tie the word back to the original roots. The baby usually inherits from the base class (parents) or super classes (grandparents) and is usually implementing the same methods as defined within them. So if you do an analysis on the attitude/behavior of the baby it would most probably (hopefully) mimic the lineage. So better start behaving!
3. Garbage collection
Unlike the normal behavior we see in terms of garbage collection usually implemented in compilers collecting our unused variables/objects etc from a heap. In the babies case its everything in and garbage out. "Output" can be various shades of poop to pee in varying intervals. Outputs can also be generated from other end as well with most of the milk/formula milk/purity coming out in terms of reflux that you have to sometimes dodge as well.
4. Unpredictable production behavior
We develop systems, we deploy systems, with minimal changes one might expect no untoward incidents or "mood" of the systems in place. However, as most of the IT fraternity know, this is farthest from the truth. The harsh truth of times of "production down/slow" are way too much. There is sadly no pattern and you cannot really evaluate what's the next mood change.
Similar can be said for babies as well, at one time we would find the baby crying, the next second we would do that magic trickv(play a song, snuggle etc) the baby would laugh again, then become irritated cuz the baby has not been fed. Point is we have to be on our toes. One slight misjudgment (usually from the dad) and we see the baby back into the recursive mode of crying at higher decibel tone till the mother arrives.
I would keep updating the post with other anecdotes as and when they keep coming by and I would try to tie them closely with the boring IT work that we keep on doing.. till then adios. YES! he is crying again!
1. You start from ground up!
2. Inheritance
This is one of the fundamentals when we come to the object oriented programming, a programming paradigm that enables us to understand the way the objects usually interact with each other, now this stands true that the programming fundamentals were derived from the real life but once we get entwined in all the software lingo it is important to tie the word back to the original roots. The baby usually inherits from the base class (parents) or super classes (grandparents) and is usually implementing the same methods as defined within them. So if you do an analysis on the attitude/behavior of the baby it would most probably (hopefully) mimic the lineage. So better start behaving!
3. Garbage collection
Unlike the normal behavior we see in terms of garbage collection usually implemented in compilers collecting our unused variables/objects etc from a heap. In the babies case its everything in and garbage out. "Output" can be various shades of poop to pee in varying intervals. Outputs can also be generated from other end as well with most of the milk/formula milk/purity coming out in terms of reflux that you have to sometimes dodge as well.
4. Unpredictable production behavior
We develop systems, we deploy systems, with minimal changes one might expect no untoward incidents or "mood" of the systems in place. However, as most of the IT fraternity know, this is farthest from the truth. The harsh truth of times of "production down/slow" are way too much. There is sadly no pattern and you cannot really evaluate what's the next mood change.
Similar can be said for babies as well, at one time we would find the baby crying, the next second we would do that magic trickv(play a song, snuggle etc) the baby would laugh again, then become irritated cuz the baby has not been fed. Point is we have to be on our toes. One slight misjudgment (usually from the dad) and we see the baby back into the recursive mode of crying at higher decibel tone till the mother arrives.
I would keep updating the post with other anecdotes as and when they keep coming by and I would try to tie them closely with the boring IT work that we keep on doing.. till then adios. YES! he is crying again!
Comments