Download to read offline
Uploaded byFITC
Just Make Stuff!
Catt Small discusses the importance of focusing on the 'who, what, when, where, and why' in design rather than strictly adhering to processes. She emphasizes that while processes can provide guidance and efficiency, they can also become unhelpful and hinder creativity. The talk encourages designers to adapt their processes based on their specific context and to celebrate their successes while accepting imperfections.
More Related Content
![Automating ISP Networks Using Ansible and IPAM as a Source of Truth [SoT]](https://cdn.slidesharecdn.com/ss_thumbnails/automatingispnetworksusingansibleandipamasasourceoftruthsot-v25-1-251124105117-d7d4ca24-thumbnail.jpg?width=640&height=640&fit=bounds)
Just Make Stuff!
- 1. @cattsmall@cattsmall Just Make Stuff! FITC2016 – Catt Small
- 2. @cattsmall@cattsmall ● Product Designer,SoundCloud ● Co-founder, Brooklyn Gamery ● Co-founder, Code Liberation ● Maker of various things! A little about me:
- 3. @cattsmall@cattsmall To help youworry less about the how and more about the who, what, when, where, and why. The goal of today’s talk:
- 4. @cattsmall@cattsmall ● Why thissubject matters ● What process is good for ● Why process can be unhelpful ● How to focus less on process ● When process is okay Topics:
- 5.
- 6. @cattsmall@cattsmall A long timeago in a galaxy far, far away...
- 7. @cattsmall@cattsmall Baby designer Catt! Iwanna be the very best!
- 8.
- 9.
- 10.
- 11.
- 12.
- 13.
- 14.
- 15. @cattsmall@cattsmall Why processes & toolscan be good
- 16.
- 17.
- 18. @cattsmall@cattsmall <form action="#" method="post"> <div> <labelfor="name">Text Input:</label> <input type="text" name="name" id="name" value="" tabindex="1" /> </div> <div> <h4>Radio Button Choice</h4> <label for="radio-choice-1">Choice 1</label> <input type="radio" name="radio-choice-1" id="radio-choice-1" tabindex="2" value="choice-1" /> <label for="radio-choice-2">Choice 2</label> <input type="radio" name="radio-choice-2" id="radio-choice-2" tabindex="3" value="choice-2" /> </div> Efficient It just works!
- 19.
- 20. @cattsmall@cattsmall Why they canbe unhelpful
- 21. @cattsmall@cattsmall When it doesn’twork, it doesn’t work
- 22. @cattsmall@cattsmall Lots of hierarchy PHPJavaSQL C++ASP.NET Objective C C#Ruby JS Python JS Knockout MeteorBackbone Angular ReactEmber
- 23. @cattsmall@cattsmall Real vs. fake I’ma real programmer! export class Just<A> extends Maybe<A> { constructor(public value: A) { super(); }; export class Nothing<A> extends Maybe<A> { constructor() { super(); }; fold<R>(match) { return match.nothing; } export function of<A>(value: A): Maybe<A> { return new Just(value); export function zero<A>(): Nothing<A> { return new Nothing(); export function map<A, B>(fn: (a: A) => B): (m: Maybe<A>) => Maybe<B> { return function morphism(ma) { return ma.fold({ just: (a) => { return new Just(fn(a)) }, export function bind<A, B>(fn: (a: A) => Maybe<B>): (m: Maybe<A>) => Maybe<B> return function morphism(ma) { return ma.fold({ </> </>
- 24.
- 25. @cattsmall@cattsmall No room forvariables But that doesn’ t work for our team... We should try this new method!
- 26. @cattsmall@cattsmall But none of usknow how it works... Power shifts & vacuums This is the best framework!
- 27. @cattsmall@cattsmall No time tocelebrate Work Think about what to improve
- 28.
- 29.
- 30.
- 31. @cattsmall@cattsmall Stop unhelpful discussions Ithink we should use– Slow down.
- 32. @cattsmall@cattsmall Consider your context Companysize Team composition
- 33. @cattsmall@cattsmall The how willarise from the what.
- 34. @cattsmall@cattsmall Ask yourself questions ●Are you feeling frustrated? ● Does it benefit you enough to continue? ● Where can you deviate?
- 35. @cattsmall@cattsmall Make your ownprocess Ideate Iterate Learn Design BuildCelebrate Launch Test
- 36. @cattsmall@cattsmall Pat yourself onthe back NOICE!
- 37.
- 38. @cattsmall@cattsmall If things gettoo loose, rein it in!
- 39. @cattsmall@cattsmall Confused What the heckare we making?
- 40. @cattsmall@cattsmall Frustrated I can’t takeit anymore!
- 41. @cattsmall@cattsmall Unsure I don’t knowwhat to do next...
- 42.
- 43.
- 44. @cattsmall@cattsmall Don’t let itget out of hand.
- 45. @cattsmall@cattsmall Define objectives upfront Ithink we should use– What is our goal?
- 46. @cattsmall@cattsmall W’s first Define who, what,when, where, why Define how
- 47. @cattsmall@cattsmall Be flexible That’s notwhat the book says, but it works for us!
- 48. @cattsmall@cattsmall Ignore trendy hotness Reactworked well for them, but Ember does the job for us!
- 49. @cattsmall@cattsmall //random integer method. Lorem.prototype.randomInt= function (min, max) { return Math.floor(Math.random() * (max - min + 1)) + min; }; //text creator method with parameters: how many, what Lorem.prototype.createText = function(count, type) { switch (type) { //paragraphs are loads of sentences. case Lorem.TYPE.PARAGRAPH: var paragraphs = new Array; for (var i = 0; i < count; i++) { var paragraphLength = Share knowledge Let’s break down how this function works.
- 50.
- 51.
- 52. @cattsmall@cattsmall ● Process isa double-edged sword. ● A person’s right is another’s wrong. ● Power shifts/vacuums can happen when one person advocates for a new process or tool. In summary:
- 53. @cattsmall@cattsmall ● Think aboutyour context first. ● Always define project goals. ● Accept imperfection. ● Don’t worry about the new hotness. ● Celebrate what you make. Advice:
- 54. @cattsmall@cattsmall Go out there& make cool stuff!
- 55. @cattsmall@cattsmall Thank you. Questions? Tweet @cattsmall Emailcatt@cattsmall.com