Embrace Limitations to Complete Projects
Many years ago my grandfather told me "there is no art without limitation". Every inspiration has to fit within reality. That's not a bad thing.
Join the DZone community and get the full member experience.Join For Free
as makers and creatives, we hate it when bosses and clients put limits on what we can do when we build new software. we believe that we should be free to try anything we want with the code and the features, and that we would automatically build innovative software that could rival apple’s if only we had a bit more freedom.
yet, somehow, it’s the project with deadlines and strict requirements at your day job that end up shipping , while your own unfinished side projects languish on a github repository. the code of your side project is elegant, with a 100% complete test suite and all the latest technologies. unfortunately, nobody uses it, while old legacy code you’re ashamed of keeps going!
it’s counterintuitive, but limitations are important and will teach you how to build software that works. a large project where everything is wide open and has no clear deadline will often end up with you in the weeds, polishing a useless detail to perfection or upgrading just one last library.
my best learning experiences were at work with projects that had to ship: the stakes were higher and i had to get moving. i would learn the basics and then get started working immediately on the most important parts of the project. i could learn what was required just in time, without focusing for hours on theory or parts of the framework that were not very useful in the end.
somehow, this is really hard to put into practice when we’re working on our own projects for the sake of learning. there’s always a better way to do things, or one last missing feature, and with nobody to stop us this can go on for a while.
if you’re working on a project by yourself and don’t see any progress, creating your own limitations can help you complete it. you don’t want to take on a project that never ends, so choose the technologies you’ll use and what features you’ll implement before getting started, keeping it small and simple. after this, put your head down and work on your first version, making sure you don’t let yourself be distracted by new shiny technologies that don’t add to your project.
upgrades and new features can wait until you’re done, and you should welcome any occasions to reduce the scope of your application. since you’re working on this alone, limitations are your friends and will help you reach your goals.
Published at DZone with permission of Cindy Potvin, DZone MVB. See the original article here.
Opinions expressed by DZone contributors are their own.