small_Fcsqb5pWQAAzPIK.jpeg

thumbnail_Fcsqb5pWQAAzPIK.jpeg

Adobe acquires Figma, cue the memes 🤪

large_Crossover Series NFTs.png

medium_Crossover Series NFTs.png

small_Crossover Series NFTs.png

thumbnail_Crossover Series NFTs.png

From Photography to NFT Art: Twisted Digital Landscapes with Nate Hill

From Design System to ‘NFT Design System’: Creating TinyFaces

Neurodiversity and Inclusion: Choosing Kinder Design

<p><a href="http://ift.tt/2mYx6Dp">medium bookmark / Raindrop.io</a> |  </p>
<p>I read <a href="http://amzn.to/2iaLaVV">Prototyping</a> by Todd Zaki Warfel back in 2011. So while some of the software tools discussed in the book are a bit out-of-date, the concepts around ideation and prototyping are still useful today.</p>
<p>Prototyping is what I do for about 40% of my job. It is foundational to making sure you are on the right track before ever spending time writing a ton of code. It also is great for getting a concept out early and for playing with multiple concepts at once — especially if you are considering multiple methods of tackling the same problem and you want to figure out what is the critical workflow. Prototypes are cheap and are useful tools for ideation. In fact, when I used to help teach Information Architecture we used to make people generate four sketch prototypes before we would pick one for the teams to develop.</p>
<p>This book helps cover all of these basic concepts and provides a good argument for why prototyping should be part of the software development process. It also covers the different types of prototyping and how to do them (with dated pointers to software). But, the most useful part of this book is essentially chapter 4 where Zaki Warfel covers the guiding principles of prototyping.</p>
<ol>
<li>Understand your audience and intent</li>
<li>Plan a little — prototype the rest</li>
<li>Set expectations</li>
<li>You can sketch</li>
<li>Its a prototype — not the Mona Lisa</li>
<li>If you can’t make it, fake it</li>
<li>Prototype on what you need</li>
<li>Reduce risk — prototype early and often</li>
</ol>
<p>It doesn’t matter what software you use (or not use) to make your prototype. All that matters is that you do prototype. Following those guidelines are going to do nothing but lead you in the right direction for creating usable and useful software.</p>
<p>The last thing to say about this book is that it is a pretty typical Rosenfeld book. There are beautiful pictures, easy to digest chapters with recaps at the end, and the writing is easy to digest for beginners. While a bit rudimentary, I think that even with the dated materials that this book would be a great resource for anyone in software engineering.</p>
<h4>Book Club Questions</h4>
<ol>
<li>Can you think of an example of finding a bad workflow because you prototyped it?</li>
<li>How long do you spend prototyping before you move to building software?</li>
<li>What is your favorite software to use for prototyping? Mine is OmniGraffle, but I’m starting to get pretty proficient in Illustrator and the Adobe Suite.</li>
</ol>
<div><a href="http://ift.tt/2mYx6Dp">http://ift.tt/2mYx6Dp</a></div>


So you have an idea… A review of Prototyping

So you have an idea… A review of Prototyping

Top Stories