What are some key differences between a Software Prototyper and a Software Engineer
Before I started building prototypes in Business Design, I worked as a software engineer for a small agency. We have built web-based applications for corporate clients. When I got into prototyping I thought it's not a big change. I mean, we are building software, right? But I quickly learned that there are some key differences in the whole approach, the thinking, communication, skills and tools. Here are some key differences between the two roles:
A Software Prototyper... | A Software Engineer... |
...thinks in experiments, hypotheses to test & business models (with it's DNA) | ...thinks in scalable software in terms of architecture, performance etc. |
...is used to work with very unclear requirements | ...works very close along specifications and requirements |
...is proactive and fills the gaps (there are a lot in these early stages) | ...is reactive and waits for a jira-ticket |
...is more of a generalist (design AND frontend, AND backend AND infrastructure) | ...is more of a specialist (design OR frontend OR backend OR infrastructure) |
...takes every shortcut to be fast | ...spends a lot of time in choosing the right approach |
...can work and communicate well with non-technical stake-holders | ...can work and communicate well with technical stake-holders |
...has more of a prototyping-mindset and approach (make it work -> make it right -> make it fast) | ...has more of an engineering-mindset and approach (make it right & make it fast & make it work) |
...is interested & understands what prototypes can do with humans (socially, emotionally...) | ...is interested & understands the technical side of prototypes |
It's very important to understand these differences when you are looking for prototyping support in your business design team. It can slow you down significantly if you are not working with somebody who knows what to build, how to build it and what's important along the way.