The Day by day Developer.

King Cyrus the great once said “ our differences make us stronger “ , it surely makes us stronger as we are like mirrors of one another , we see what the other is lacking , so it’s good for us but not necessarily for the individuals , a spaghetti code may achieve a level of singularity but it’s components become ragged/entropic and the programmer cannot use them well.  Holistic empowerment is a project management concept I had thought about for sometime . It’s basically empowering everyone but not in the same thing ,paradoxically this empowers the whole team symmetrically . Kind of like a complicated highway system  Fig 1 Fig 2 Although not cognitively appealing , these road systems empower everybody to reach their destination asymmetrically lessening the possibility of cars from arriving on the account of one another. This describes a team that has been managed but still haven't integrated smoothly , because it looks more like a spaghetti than locks of silky hair. These ones a

So its been sometime since I posted anything ,as I usually do it after compiling lots of related concepts . And yeah ,this blog is for sharing my new experiences and its updates. I've written a previous post with regards to the pair programming method were there is definitely an advantage for the overall work flow. But now that I tried it in a different setting,I think I've came up with a more detailed explanation of how this can be managed in a professional work environment. See, not all developers are friends ,even if they work on the same problem ,there can definitely be an incompatability in the way of thinking , when one developer comes up with a new idea ,if the mindset of the other is cooperative and his interest lies in resolving the problem then it would be supportive but if its a confrontational or self interested attitude of who finds the better solution,then it can be a disempowering and toxic relationship . It is understandable, not everyone is conditioned