UX in ZOOM
2 likes613 views
The document outlines Vaclav Slovacek's role at Zoom, focusing on his work as a UX designer and product manager. It discusses his experiences with user research, specification writing, and iterative design processes, emphasizing the importance of usability and developer collaboration. Additionally, it highlights his excitement about future projects and the need for effective communication within teams.
UX in ZOOM
- 1. UX in ZOOM Vaclav Slovacek vaclav.slovacek@zoomint.com
- 2. ZOOM • call recording, agent evaluation, speech analysis • Google Web Toolkit • about 500 customers in 50 countries • about 10 developers • your voice is heard • flexible and evolving
- 4. UX Designer • at ZOOM for 8 months • in product management • writing specifications • long term design decisions • planning and prioritization • day-to-day consulting
- 5. My Story no!ing more
- 6. Preparation seeing ZOOM's product studying stuff about user research user research cost calculator playing with prototyping tools
- 7. First Days designing Excel report template checking implementation designing a new player discussing what went wrong
- 8. 10 differences game It is totally different from the prototype.
- 9. 10 differences game What is the difference? explain why features are important
- 10. Unusable Specification usability of specifications matters
- 11. Quick Fixes developers coming to ask fixing a customer's issue redesigning toolbars
- 12. Request Origins
- 13. Easier Development /browse/SC-2150! and we had a lot an had s olved http://jira:81 EC” specification. Ju problems with foll owing “As in CallR of logical ! t it`s not necessar y to implement But now Va clav found out, tha ff and made this is sue much simpler. all the stu ask why a feature is requested
- 14. Triangle simple easy to develop flexible
- 15. Triangle simple easy to develop flexible
- 16. Projects Boom tuning specifications 2011 vision presentation talk with users vision for developers UX Guidelines and checklist long term projects specifications
- 17. Specification media are stronger than text
- 18. Project
- 19. Project 1 Project 2
- 20. temporary features Project 1 Project 2
- 21. critical stuff fixed now vision of the future Project 1 Project 2
- 22. Inspiration Man, I feel excited about every new feature we design now. I feel totally inspired. do not design alone
- 23. one week planning of 4 sprints next sprint Agile daily meetings review retrospective
- 24. Agile one week planning of 4 sprints 15 enhancements having 200 tasks more accurate estimates daily meetings review retrospective next sprint
- 25. Agile one week planning of 4 sprints daily meetings know what is happening enforce relationship with developers review retrospective next sprint
- 26. Agile one week planning of 4 sprints daily meetings different kind of feedback review notes for next sprint retrospective next sprint
- 27. Agile one week planning of 4 sprints daily meetings review improving communication retrospective know what you do wrong next sprint
- 28. UX Checklist use during testing Future User Research 2011 keep stuff in sync 3v er t ical 4u s ser gro 20 half a y ca up 3 re ll c s en te sear ear r s che rs
- 29. UX is fund
- 30. UX is fundamental for your company
- 31. recommendations
- 32. explore
- 33. explore
- 34. seek inspiration
- 35. we are looking for developers
- 37. Thank you for your attention
Editor's Notes
- #2: - I do not share knowledge, do not have blog\n\n
- #3: - Adobe, IMF, Porsche, Shangri-La, 144 Notruf, DHL, Raiffeisen Bank, ČSOB\n- localizations, russian, arabic, time zones, number date formating\n- open to UX, talk with Karel about progress\n
- #4: - Adobe, IMF, Porsche, Shangri-La, 144 Notruf, DHL, Raiffeisen Bank, ČSOB\n- localizations, russian, arabic, time zones, number date formating\n- open to UX, talk with Karel about progress\n
- #5: - Adobe, IMF, Porsche, Shangri-La, 144 Notruf, DHL, Raiffeisen Bank, ČSOB\n- localizations, russian, arabic, time zones, number date formating\n- open to UX, talk with Karel about progress\n
- #6: - Adobe, IMF, Porsche, Shangri-La, 144 Notruf, DHL, Raiffeisen Bank, ČSOB\n- localizations, russian, arabic, time zones, number date formating\n- open to UX, talk with Karel about progress\n
- #7: - Adobe, IMF, Porsche, Shangri-La, 144 Notruf, DHL, Raiffeisen Bank, ČSOB\n- localizations, russian, arabic, time zones, number date formating\n- open to UX, talk with Karel about progress\n
- #8: - Adobe, IMF, Porsche, Shangri-La, 144 Notruf, DHL, Raiffeisen Bank, ČSOB\n- localizations, russian, arabic, time zones, number date formating\n- open to UX, talk with Karel about progress\n
- #9: - Adobe, IMF, Porsche, Shangri-La, 144 Notruf, DHL, Raiffeisen Bank, ČSOB\n- localizations, russian, arabic, time zones, number date formating\n- open to UX, talk with Karel about progress\n
- #10: \n
- #11: - you can decide to listen or not to listen\n- past experience at CTU, EU projects\n\n
- #12: - you can decide to listen or not to listen\n- past experience at CTU, EU projects\n\n
- #13: - you can decide to listen or not to listen\n- past experience at CTU, EU projects\n\n
- #14: - you can decide to listen or not to listen\n- past experience at CTU, EU projects\n\n
- #15: - you can decide to listen or not to listen\n- past experience at CTU, EU projects\n\n
- #16: - you can decide to listen or not to listen\n- past experience at CTU, EU projects\n\n
- #17: - you can decide to listen or not to listen\n- past experience at CTU, EU projects\n\n
- #18: - might sound boring, but it is not\n- one flagship product, another merging into it and new emerging product\n
- #19: - we will skip childhood, school, university\n
- #20: - we will skip childhood, school, university\n
- #21: - we will skip childhood, school, university\n
- #22: - we will skip childhood, school, university\n
- #23: - product always looks better\n- Axure, Flash Catalyst, Illustrator, Fireworks, Balsamiq, FlairBuilder\n\n
- #24: - product always looks better\n- Axure, Flash Catalyst, Illustrator, Fireworks, Balsamiq, FlairBuilder\n\n
- #25: - product always looks better\n- Axure, Flash Catalyst, Illustrator, Fireworks, Balsamiq, FlairBuilder\n\n
- #26: - product always looks better\n- Axure, Flash Catalyst, Illustrator, Fireworks, Balsamiq, FlairBuilder\n\n
- #27: - product always looks better\n- Axure, Flash Catalyst, Illustrator, Fireworks, Balsamiq, FlairBuilder\n\n
- #28: - product always looks better\n- Axure, Flash Catalyst, Illustrator, Fireworks, Balsamiq, FlairBuilder\n\n
- #29: - product always looks better\n- Axure, Flash Catalyst, Illustrator, Fireworks, Balsamiq, FlairBuilder\n\n
- #30: - product always looks better\n- Axure, Flash Catalyst, Illustrator, Fireworks, Balsamiq, FlairBuilder\n\n
- #31: - product always looks better\n- Axure, Flash Catalyst, Illustrator, Fireworks, Balsamiq, FlairBuilder\n\n
- #32: - product always looks better\n- Axure, Flash Catalyst, Illustrator, Fireworks, Balsamiq, FlairBuilder\n\n
- #33: - product always looks better\n- Axure, Flash Catalyst, Illustrator, Fireworks, Balsamiq, FlairBuilder\n\n
- #34: - product always looks better\n- Axure, Flash Catalyst, Illustrator, Fireworks, Balsamiq, FlairBuilder\n\n
- #35: - product always looks better\n- Axure, Flash Catalyst, Illustrator, Fireworks, Balsamiq, FlairBuilder\n\n
- #36: \n
- #37: \n
- #38: \n
- #39: \n
- #40: \n
- #41: \n
- #42: \n
- #43: \n
- #44: \n
- #45: \n
- #46: - I actually found just 9 differences\n
- #47: - I actually found just 9 differences\n
- #48: - I actually found just 9 differences\n
- #49: - I actually found just 9 differences\n
- #50: - I actually found just 9 differences\n
- #51: - I actually found just 9 differences\n
- #52: - I actually found just 9 differences\n
- #53: - I actually found just 9 differences\n
- #54: - I actually found just 9 differences\n
- #55: - I actually found just 9 differences\n
- #56: - lorem ipsum story\n
- #57: - lorem ipsum story\n
- #58: - lorem ipsum story\n
- #59: - lorem ipsum story\n
- #60: - not only developers\n
- #61: - not only developers\n
- #62: - not only developers\n
- #63: - not only developers\n
- #64: - not only developers\n
- #65: - not only developers\n
- #66: - not only developers\n
- #67: - not only developers\n
- #68: - not only developers\n
- #69: - not only developers\n
- #70: - not only developers\n
- #71: - not only developers\n
- #72: - not only developers\n
- #73: \n
- #74: \n
- #75: \n
- #76: \n
- #77: - somebody tells you do it, don't do it\n- request in JIRA to add button\n- developers now ask, how things are used\n
- #78: - somebody tells you do it, don't do it\n- request in JIRA to add button\n- developers now ask, how things are used\n
- #79: \n
- #80: \n
- #81: \n
- #82: \n
- #83: - do you know what is triangle?\n- you are moving ScoreCARD back to 2007\n- hundreds of conditions\n
- #84: - do you know what is triangle?\n- you are moving ScoreCARD back to 2007\n- hundreds of conditions\n
- #85: - do you know what is triangle?\n- you are moving ScoreCARD back to 2007\n- hundreds of conditions\n
- #86: - do you know what is triangle?\n- you are moving ScoreCARD back to 2007\n- hundreds of conditions\n
- #87: - do you know what is triangle?\n- you are moving ScoreCARD back to 2007\n- hundreds of conditions\n
- #88: - do you know what is triangle?\n- you are moving ScoreCARD back to 2007\n- hundreds of conditions\n
- #89: - do you know what is triangle?\n- you are moving ScoreCARD back to 2007\n- hundreds of conditions\n
- #90: - do you know what is triangle?\n- you are moving ScoreCARD back to 2007\n- hundreds of conditions\n
- #91: - do you know what is triangle?\n- you are moving ScoreCARD back to 2007\n- hundreds of conditions\n
- #92: - do you know what is triangle?\n- you are moving ScoreCARD back to 2007\n- hundreds of conditions\n
- #93: - do you know what is triangle?\n- you are moving ScoreCARD back to 2007\n- hundreds of conditions\n
- #94: - do you know what is triangle?\n- you are moving ScoreCARD back to 2007\n- hundreds of conditions\n
- #95: - do you know what is triangle?\n- you are moving ScoreCARD back to 2007\n- hundreds of conditions\n
- #96: - do you know what is triangle?\n- you are moving ScoreCARD back to 2007\n- hundreds of conditions\n
- #97: - do you know what is triangle?\n- you are moving ScoreCARD back to 2007\n- hundreds of conditions\n
- #98: - do you know what is triangle?\n- you are moving ScoreCARD back to 2007\n- hundreds of conditions\n
- #99: - do you know what is triangle?\n- you are moving ScoreCARD back to 2007\n- hundreds of conditions\n
- #100: - 50 projects (epic - 2 or more sprints)\n
- #101: - 50 projects (epic - 2 or more sprints)\n
- #102: - 50 projects (epic - 2 or more sprints)\n
- #103: - 50 projects (epic - 2 or more sprints)\n
- #104: - 50 projects (epic - 2 or more sprints)\n
- #105: - 50 projects (epic - 2 or more sprints)\n
- #106: - 50 projects (epic - 2 or more sprints)\n
- #107: - 50 projects (epic - 2 or more sprints)\n
- #108: - 50 projects (epic - 2 or more sprints)\n
- #109: - 50 projects (epic - 2 or more sprints)\n
- #110: - 50 projects (epic - 2 or more sprints)\n
- #111: - 50 projects (epic - 2 or more sprints)\n
- #112: - 50 projects (epic - 2 or more sprints)\n
- #113: - 50 projects (epic - 2 or more sprints)\n
- #114: - 50 projects (epic - 2 or more sprints)\n
- #115: - evolution about 100 iterations per screen, 20 per dialog, trying to get rid of dialogs\n- at least 2 concepts, mostly 3\n- moses talked about why the features are important\n- presentation to developers, tranfering the knowledge, everybody knows what is going to happen\n
- #116: - evolution about 100 iterations per screen, 20 per dialog, trying to get rid of dialogs\n- at least 2 concepts, mostly 3\n- moses talked about why the features are important\n- presentation to developers, tranfering the knowledge, everybody knows what is going to happen\n
- #117: - evolution about 100 iterations per screen, 20 per dialog, trying to get rid of dialogs\n- at least 2 concepts, mostly 3\n- moses talked about why the features are important\n- presentation to developers, tranfering the knowledge, everybody knows what is going to happen\n
- #118: - evolution about 100 iterations per screen, 20 per dialog, trying to get rid of dialogs\n- at least 2 concepts, mostly 3\n- moses talked about why the features are important\n- presentation to developers, tranfering the knowledge, everybody knows what is going to happen\n
- #119: - evolution about 100 iterations per screen, 20 per dialog, trying to get rid of dialogs\n- at least 2 concepts, mostly 3\n- moses talked about why the features are important\n- presentation to developers, tranfering the knowledge, everybody knows what is going to happen\n
- #120: - evolution about 100 iterations per screen, 20 per dialog, trying to get rid of dialogs\n- at least 2 concepts, mostly 3\n- moses talked about why the features are important\n- presentation to developers, tranfering the knowledge, everybody knows what is going to happen\n
- #121: - evolution about 100 iterations per screen, 20 per dialog, trying to get rid of dialogs\n- at least 2 concepts, mostly 3\n- moses talked about why the features are important\n- presentation to developers, tranfering the knowledge, everybody knows what is going to happen\n
- #122: - evolution about 100 iterations per screen, 20 per dialog, trying to get rid of dialogs\n- at least 2 concepts, mostly 3\n- moses talked about why the features are important\n- presentation to developers, tranfering the knowledge, everybody knows what is going to happen\n
- #123: - evolution about 100 iterations per screen, 20 per dialog, trying to get rid of dialogs\n- at least 2 concepts, mostly 3\n- moses talked about why the features are important\n- presentation to developers, tranfering the knowledge, everybody knows what is going to happen\n
- #124: - evolution about 100 iterations per screen, 20 per dialog, trying to get rid of dialogs\n- at least 2 concepts, mostly 3\n- moses talked about why the features are important\n- presentation to developers, tranfering the knowledge, everybody knows what is going to happen\n
- #125: - evolution about 100 iterations per screen, 20 per dialog, trying to get rid of dialogs\n- at least 2 concepts, mostly 3\n- moses talked about why the features are important\n- presentation to developers, tranfering the knowledge, everybody knows what is going to happen\n
- #126: - evolution about 100 iterations per screen, 20 per dialog, trying to get rid of dialogs\n- at least 2 concepts, mostly 3\n- moses talked about why the features are important\n- presentation to developers, tranfering the knowledge, everybody knows what is going to happen\n
- #127: - evolution about 100 iterations per screen, 20 per dialog, trying to get rid of dialogs\n- at least 2 concepts, mostly 3\n- moses talked about why the features are important\n- presentation to developers, tranfering the knowledge, everybody knows what is going to happen\n
- #128: - evolution about 100 iterations per screen, 20 per dialog, trying to get rid of dialogs\n- at least 2 concepts, mostly 3\n- moses talked about why the features are important\n- presentation to developers, tranfering the knowledge, everybody knows what is going to happen\n
- #129: - evolution about 100 iterations per screen, 20 per dialog, trying to get rid of dialogs\n- at least 2 concepts, mostly 3\n- moses talked about why the features are important\n- presentation to developers, tranfering the knowledge, everybody knows what is going to happen\n
- #130: - evolution about 100 iterations per screen, 20 per dialog, trying to get rid of dialogs\n- at least 2 concepts, mostly 3\n- moses talked about why the features are important\n- presentation to developers, tranfering the knowledge, everybody knows what is going to happen\n
- #131: - evolution about 100 iterations per screen, 20 per dialog, trying to get rid of dialogs\n- at least 2 concepts, mostly 3\n- moses talked about why the features are important\n- presentation to developers, tranfering the knowledge, everybody knows what is going to happen\n
- #132: - evolution about 100 iterations per screen, 20 per dialog, trying to get rid of dialogs\n- at least 2 concepts, mostly 3\n- moses talked about why the features are important\n- presentation to developers, tranfering the knowledge, everybody knows what is going to happen\n
- #133: - evolution about 100 iterations per screen, 20 per dialog, trying to get rid of dialogs\n- at least 2 concepts, mostly 3\n- moses talked about why the features are important\n- presentation to developers, tranfering the knowledge, everybody knows what is going to happen\n
- #134: - evolution about 100 iterations per screen, 20 per dialog, trying to get rid of dialogs\n- at least 2 concepts, mostly 3\n- moses talked about why the features are important\n- presentation to developers, tranfering the knowledge, everybody knows what is going to happen\n
- #135: - evolution about 100 iterations per screen, 20 per dialog, trying to get rid of dialogs\n- at least 2 concepts, mostly 3\n- moses talked about why the features are important\n- presentation to developers, tranfering the knowledge, everybody knows what is going to happen\n
- #136: - evolution about 100 iterations per screen, 20 per dialog, trying to get rid of dialogs\n- at least 2 concepts, mostly 3\n- moses talked about why the features are important\n- presentation to developers, tranfering the knowledge, everybody knows what is going to happen\n
- #137: - evolution about 100 iterations per screen, 20 per dialog, trying to get rid of dialogs\n- at least 2 concepts, mostly 3\n- moses talked about why the features are important\n- presentation to developers, tranfering the knowledge, everybody knows what is going to happen\n
- #138: - evolution about 100 iterations per screen, 20 per dialog, trying to get rid of dialogs\n- at least 2 concepts, mostly 3\n- moses talked about why the features are important\n- presentation to developers, tranfering the knowledge, everybody knows what is going to happen\n
- #139: - less issues to manage\n- arrange the projects in the right order\n- verify, include\n
- #140: - less issues to manage\n- arrange the projects in the right order\n- verify, include\n
- #141: - less issues to manage\n- arrange the projects in the right order\n- verify, include\n
- #142: - less issues to manage\n- arrange the projects in the right order\n- verify, include\n
- #143: - less issues to manage\n- arrange the projects in the right order\n- verify, include\n
- #144: - less issues to manage\n- arrange the projects in the right order\n- verify, include\n
- #145: - less issues to manage\n- arrange the projects in the right order\n- verify, include\n
- #146: - less issues to manage\n- arrange the projects in the right order\n- verify, include\n
- #147: - less issues to manage\n- arrange the projects in the right order\n- verify, include\n
- #148: - less issues to manage\n- arrange the projects in the right order\n- verify, include\n
- #149: - less issues to manage\n- arrange the projects in the right order\n- verify, include\n
- #150: - less issues to manage\n- arrange the projects in the right order\n- verify, include\n
- #151: - less issues to manage\n- arrange the projects in the right order\n- verify, include\n
- #152: - less issues to manage\n- arrange the projects in the right order\n- verify, include\n
- #153: - less issues to manage\n- arrange the projects in the right order\n- verify, include\n
- #154: - less issues to manage\n- arrange the projects in the right order\n- verify, include\n
- #155: - less issues to manage\n- arrange the projects in the right order\n- verify, include\n
- #156: - less issues to manage\n- arrange the projects in the right order\n- verify, include\n
- #157: - less issues to manage\n- arrange the projects in the right order\n- verify, include\n
- #158: - less issues to manage\n- arrange the projects in the right order\n- verify, include\n
- #159: - less issues to manage\n- arrange the projects in the right order\n- verify, include\n
- #160: - less issues to manage\n- arrange the projects in the right order\n- verify, include\n
- #161: - less issues to manage\n- arrange the projects in the right order\n- verify, include\n
- #162: - less issues to manage\n- arrange the projects in the right order\n- verify, include\n
- #163: - less issues to manage\n- arrange the projects in the right order\n- verify, include\n
- #164: - less issues to manage\n- arrange the projects in the right order\n- verify, include\n
- #165: - less issues to manage\n- arrange the projects in the right order\n- verify, include\n
- #166: - it helps you\n- it spreads a spirit, people are playing all the time\n- Jirka Valasek's quote\n- water of life\n
- #167: - it helps you\n- it spreads a spirit, people are playing all the time\n- Jirka Valasek's quote\n- water of life\n
- #168: \n
- #169: \n
- #170: \n
- #171: \n
- #172: \n
- #173: \n
- #174: \n
- #175: \n
- #176: \n
- #177: \n
- #178: \n
- #179: \n
- #180: \n
- #181: \n
- #182: \n
- #183: \n
- #184: \n
- #185: \n
- #186: \n
- #187: \n
- #188: \n
- #189: \n
- #190: \n
- #191: \n
- #192: \n
- #193: \n
- #194: \n
- #195: \n
- #196: \n
- #197: \n
- #198: \n
- #199: \n
- #200: \n
- #201: \n
- #202: \n
- #203: \n
- #204: \n
- #205: \n
- #206: \n
- #207: \n
- #208: \n
- #209: \n
- #210: \n
- #211: \n
- #212: \n
- #213: \n
- #214: \n
- #215: \n
- #216: \n
- #217: \n
- #218: \n
- #219: \n
- #220: \n
- #221: \n
- #222: \n
- #223: - chief developer - my design, the real one, not yours\n- that is what we do - we create software for people\n
- #224: - chief developer - my design, the real one, not yours\n- that is what we do - we create software for people\n
- #225: - chief developer - my design, the real one, not yours\n- that is what we do - we create software for people\n
- #226: - explore and sacrifice\n- make people understand that most of your work is exploring poor solutions\n
- #227: - explore and sacrifice\n- make people understand that most of your work is exploring poor solutions\n
- #228: - explore and sacrifice\n- make people understand that most of your work is exploring poor solutions\n
- #229: - explore and sacrifice\n- make people understand that most of your work is exploring poor solutions\n
- #230: - explore and sacrifice\n- make people understand that most of your work is exploring poor solutions\n
- #231: - explore and sacrifice\n- make people understand that most of your work is exploring poor solutions\n
- #232: \n
- #233: \n
- #234: \n
- #235: \n
- #236: \n
- #237: \n
- #238: \n
- #239: \n
- #240: \n
- #241: \n
- #242: \n
- #243: \n
- #244: \n
- #245: \n
- #246: \n
- #247: DECISIONS: I hate compromises, do not stay in the middle because of your time constraints, the icon for licking ankles, if you don't make them then you do not see some issues\nSACRIFICE: confusing prototypes with development, work is not visible, Confluence, 100 hundred\n
- #248: DECISIONS: I hate compromises, do not stay in the middle because of your time constraints, the icon for licking ankles, if you don't make them then you do not see some issues\nSACRIFICE: confusing prototypes with development, work is not visible, Confluence, 100 hundred\n
- #249: DECISIONS: I hate compromises, do not stay in the middle because of your time constraints, the icon for licking ankles, if you don't make them then you do not see some issues\nSACRIFICE: confusing prototypes with development, work is not visible, Confluence, 100 hundred\n
- #250: DECISIONS: I hate compromises, do not stay in the middle because of your time constraints, the icon for licking ankles, if you don't make them then you do not see some issues\nSACRIFICE: confusing prototypes with development, work is not visible, Confluence, 100 hundred\n
- #251: DECISIONS: I hate compromises, do not stay in the middle because of your time constraints, the icon for licking ankles, if you don't make them then you do not see some issues\nSACRIFICE: confusing prototypes with development, work is not visible, Confluence, 100 hundred\n
- #252: DECISIONS: I hate compromises, do not stay in the middle because of your time constraints, the icon for licking ankles, if you don't make them then you do not see some issues\nSACRIFICE: confusing prototypes with development, work is not visible, Confluence, 100 hundred\n
- #253: DECISIONS: I hate compromises, do not stay in the middle because of your time constraints, the icon for licking ankles, if you don't make them then you do not see some issues\nSACRIFICE: confusing prototypes with development, work is not visible, Confluence, 100 hundred\n
- #254: DECISIONS: I hate compromises, do not stay in the middle because of your time constraints, the icon for licking ankles, if you don't make them then you do not see some issues\nSACRIFICE: confusing prototypes with development, work is not visible, Confluence, 100 hundred\n
- #255: DECISIONS: I hate compromises, do not stay in the middle because of your time constraints, the icon for licking ankles, if you don't make them then you do not see some issues\nSACRIFICE: confusing prototypes with development, work is not visible, Confluence, 100 hundred\n
- #256: DECISIONS: I hate compromises, do not stay in the middle because of your time constraints, the icon for licking ankles, if you don't make them then you do not see some issues\nSACRIFICE: confusing prototypes with development, work is not visible, Confluence, 100 hundred\n
- #257: DECISIONS: I hate compromises, do not stay in the middle because of your time constraints, the icon for licking ankles, if you don't make them then you do not see some issues\nSACRIFICE: confusing prototypes with development, work is not visible, Confluence, 100 hundred\n
- #258: DECISIONS: I hate compromises, do not stay in the middle because of your time constraints, the icon for licking ankles, if you don't make them then you do not see some issues\nSACRIFICE: confusing prototypes with development, work is not visible, Confluence, 100 hundred\n
- #259: DECISIONS: I hate compromises, do not stay in the middle because of your time constraints, the icon for licking ankles, if you don't make them then you do not see some issues\nSACRIFICE: confusing prototypes with development, work is not visible, Confluence, 100 hundred\n
- #260: DECISIONS: I hate compromises, do not stay in the middle because of your time constraints, the icon for licking ankles, if you don't make them then you do not see some issues\nSACRIFICE: confusing prototypes with development, work is not visible, Confluence, 100 hundred\n
- #261: DECISIONS: I hate compromises, do not stay in the middle because of your time constraints, the icon for licking ankles, if you don't make them then you do not see some issues\nSACRIFICE: confusing prototypes with development, work is not visible, Confluence, 100 hundred\n
- #262: DECISIONS: I hate compromises, do not stay in the middle because of your time constraints, the icon for licking ankles, if you don't make them then you do not see some issues\nSACRIFICE: confusing prototypes with development, work is not visible, Confluence, 100 hundred\n
- #263: - chief developer - my design, the real one, not yours\n- that is what we do - we create software for people\n
- #264: - chief developer - my design, the real one, not yours\n- that is what we do - we create software for people\n
- #265: - chief developer - my design, the real one, not yours\n- that is what we do - we create software for people\n
- #266: - chief developer - my design, the real one, not yours\n- that is what we do - we create software for people\n
- #267: - chief developer - my design, the real one, not yours\n- that is what we do - we create software for people\n
- #268: - developers are also fundamental\n- http://www.zoomint.com/en/jobs/129-senior-software-engineer\n- 5 years experience, persistence frameworks, english, GWT\n
- #269: \n
- #270: \n