Programming related thought

While reading through Mark Pilgrim (software developer) Mark Pilgrim is a software developer, writer, and advocate of free software. He authored a popular blog, and has written several books, including Dive into Python, a guide to the Python programming language published under the GNU Free Documentation License. Formerly an accessibility architect in the IBM Emerging Technologies Group, he started working at Google in March 2007. In 2018, he moved to Brave. 's Dive Into Python Mark Pilgrim is a software developer, writer, and advocate of free software. He authored a popular blog, and has written several books, including Dive into Python, a guide to the Python programming language published under the GNU Free Documentation License. Formerly an accessibility architect in the IBM Emerging Technologies Group, he started working at Google in March 2007. In 2018, he moved to Brave. , stumbled upon this interesting thought, wherein he says that, when you 'plan' to develop a full -fledged feature for a software which will help in certain tasks, and if you end up coding a small version, make it just work rather than a completed polished 'as-per-plan' thing, then you are not only being inefficient, but you are being rude (to your customers).

That's a very good thought. Most of times, I think of designing a software and when it reaches to level where it works, I stop there and move to next. The working thing, sometimes never goes past my computer.