With OOP, the structure was changed from Procedural to modular and many of the things we’ll be borrowing from will be from OOP.
Protopie classes code#
Previously to OOP, code was procedural that is, it would execute in a linear fashion. One of the biggest leaps forward in terms of code modularity was the invention of OOP (Object Oriented Programming). Having a shared vocabulary of how things are organised and coded is crucial to enable a team of developers to work together efficiently. Over the years the developers have created processes, methodologies and frameworks to help them work more efficiently with code and more collaboratively in teams. So let’s look at how we can apply some of these standards to ProtoPie. Patterns, processes, and principles all contribute to creating common practice and understanding. We all have different ways of doing things but because of a lack of standards many hours figuring out how something has been built can be wasted. I can’t tell you the number of hours I’ve wasted trying to figure out how a designer has prototyped something. You can then get back on track building prototypes that can be more easily changed and iterated as well as being able to be shared and collaborated with more easily. By adopting a few simple tried and tested principles that developers have been using for years and you can start to alleviate some of that pain and frustration. So far it has done a fairly good job at hiding away things like code and development constructs giving the designer the freedom to be messy and explore ideas without concerning themselves with the build quality or organisation of their prototypes.īut as prototypes become larger and more complex it becomes quickly apparent that creating in that hot messy exploration mode will eventually result in more time being spent fixing things than creating them.Ĭomments come back from stakeholders such as “can you just make it do this” or “can you just change that” and soon enough you are trying to retrofit changes your time is being eaten up by bug fixing and rebuilding (something developers call refactoring).īut it doesn’t have to be like this. To do that ProtoPie needs to work the way a designer thinks. ProtoPie’s goal has always been to give designers autonomy.
0 kommentar(er)
