The latest articles on DEV Community by Imran Askem (@imranaskem). https://dev.to/imranaskem https://media2.dev.to/dynamic/image/width=90,height=90,fit=cover,gravity=auto,format=auto/https:%2F%2Fdev-to-uploads.s3.amazonaws.com%2Fuploads%2Fuser%2Fprofile_image%2F26919%2F0816a06e-b5a9-4663-bcb3-04bc3d6273d7.png https://dev.to/imranaskem en Imran Askem Tue, 09 Apr 2019 08:22:26 +0000 https://dev.to/imranaskem/is-there-an-iron-triangle-of-development-1cp https://dev.to/imranaskem/is-there-an-iron-triangle-of-development-1cp <p>Before I was a developer, I was a Project Manager and one of the first things I learnt was the iron triangle. For anyone not familiar with it, it's a model of the constraints of managing a project. The idea is that you can only have two of the three points. For example, if you want a project with many features delivered quickly it will cost a lot of money/resource. I found it a helpful construct for thinking about what trade-offs to make, which got me thinking about how this could apply to development.</p> <p>As someone that likes to make conscious decisions, I often wonder what trade-offs I'm making as I write code. </p> <p>If I'm working on a task that needs to be highly performant am I sacrificing readability? If I want to make a project easy to maintain does that mean it can't be as extensible? </p> <p>I'm actually not sure what shape the "development" version should be or what the axes are. My starting list would be:</p> <ul> <li>Performance</li> <li>Readability</li> <li>Extensibility</li> <li>Maintainability </li> <li>Time (to develop)</li> </ul> <p>At the moment I have a lot of questions and few answers but I think it's an interesting idea, have you ever thought something similar? It would be great to hear from you.</p> discuss productivity softwaredevelopment