I'm a coder who has worn a lot of hats, from individual contributor to lead engineer to "CTO" (yes, in quotes, make of that what you will!). I've plenty to learn and hopefully some to share as well.
Obligatory mention of the 80-20 rule. Often you can build something 80% functional in a weekend. It's the last 20% that takes a while :) I see this pattern play out sometimes after our internal hackathons. Someone throws something demo-able together in a day, but making it production ready takes a lot longer (if we even decide to do that).
I'm a Computer Science enthusiast with a keen interest in Maths. I like to tinker with things around me & practise Sahaja Yoga meditation. Do follow me on GitHub https://github.com/Aatmaj-Zephyr
I tend to flip it around and do the 20% first and then do the 80% (implementation) as that is the best way to go about it. Some people create the path and build while I prefer to open the path and determine what is needed beforehand so that the road is clear for development.
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
Obligatory mention of the 80-20 rule. Often you can build something 80% functional in a weekend. It's the last 20% that takes a while :) I see this pattern play out sometimes after our internal hackathons. Someone throws something demo-able together in a day, but making it production ready takes a lot longer (if we even decide to do that).
80-20 is the perfect way to describe this feeling!
Yep
God lies in the details. And the details take a lot longer than the other parts.
I tend to flip it around and do the 20% first and then do the 80% (implementation) as that is the best way to go about it. Some people create the path and build while I prefer to open the path and determine what is needed beforehand so that the road is clear for development.