Download to read offline
More Related Content
Similar to Preparing for the WebGeek DevCup
Preparing for the WebGeek DevCup
- 1. Preparing for the WebGeekDevCup Bryan Bibat pangkaraniwang developer
- 2.
- 3.
- 4. Solution: Do everything thatyou can do before the event
- 5. according to therules:
- 6. No Offsite Development: All development must be performed on-site between the aforementioned start and end times for the event.
- 7. No Offsite Development: We don’t allow teams to re- purpose an existing app, add a feature, then flog their badly disguised demo as a hack.
- 8.
- 9. Languages & Tools: Applications may be assembled using any mix of programming languages, application frameworks, and development tools.
- 10. You cannot pre-buildan app, but you can pre-build a framework.
- 11. framework ≈ app that does nothing
- 12. Rest of thistalk: ● Preparing your App/Framework ● Preparing everything else
- 13. For professional developers: nothing new here!
- 14.
- 15.
- 16.
- 17.
- 18.
- 19. doesn't matter (had app)
- 20. Choose what youare comfortable with
- 21. less time Google-ing = more time coding
- 22.
- 23.
- 24. your framework must: ● run on a web server
- 25. your framework must: ● run on a web server ● not have errors when browsed
- 26. your framework must: ● run on a web server ● not have errors when browsed ● connect to a database, if needed
- 27. your framework must: ● run on a web server ● not have errors when browsed ● connect to a database, if needed ● not do anything else (dummy programs are ok)
- 28. Feel free toadd modules found in other frameworks
- 29. Framework Modules Front EndDesign Frameworks
- 32. Framework Modules Page Templating
- 36. Framework Modules Administration
- 38. Framework Modules Authentication
- 39. Framework Modules Pagination
- 40.
- 41. Apart from frameworksetup, your biggest potential time waster would be...
- 42.
- 43. Install everything beforehand!
- 44. Don't expect theWi-Fi to be flawless on the event
- 45. Make sure everyonein your team is able to execute and develop your app
- 46.
- 50. Once you canrun the app, go install whatever you want in your machine
- 54. Have a backupinternet connection
- 55. Make sure everyonein your team is able to execute and develop your app
- 56.
- 57. "If it's notin version control, it doesn't exist."
- 58. The Joel Test (http://www.joelonsoftware.com/articles/fog0000000043.html) 1. Do you use source control?
- 59. Also proves youdidn't cheat
- 60. Doesn't matter whatyou choose as long as you use one
- 64. Share your code. Don'tworry about people copying it.
- 65.
- 66. Making your appavailable on the internet is optional, but will help in the judging
- 68. The Joel Test (http://www.joelonsoftware.com/articles/fog0000000043.html) 2. Can you make a build in one step?
- 69. Option 1: Use push-basedhosting
- 75.
- 79. one command: capdeploy
- 81. Everything's prepped exceptthe most important part...
- 82.
- 83. Communication is key! (yes it's cliche)
- 84. asset creation andintegration,
- 85. asset creation andintegration, conflict resolution,
- 86. asset creation andintegration, conflict resolution, bug finding and fixing,
- 87. asset creation andintegration, conflict resolution, bug finding and fixing, feature creation and pruning,
- 88. asset creation andintegration, conflict resolution, bug finding and fixing, feature creation and pruning, etc.
- 89. No ideal groupcomposition - work with what you have
- 90. Mostly devs? Focus onthe functionality. Take risks in experimental technology.
- 91. Mostly designers? Limitfeatures but polish them. Focus on making your app usable.
- 92. Don't forget thebasics!
- 93. Problems are easierto fix in design than in code
- 94.
- 95. Your software projectis running very late, what do you do?
- 96. Your software projectis running very late, what do you do? A. Add more people to the project
- 97. Your software projectis running very late, what do you do? A. Add more people to the project B. Make people work harder
- 98. Your software projectis running very late, what do you do? A. Add more people to the project B. Make people work harder C. Cut unnecessary features
- 99. If you answeredA or B, I have bad news for you
- 100. Your software projectis running very late, what do you do? A. Add more people to the project B. Make people work harder C. Cut unnecessary features
- 101.
- 102.
- 103.
- 104. Say no todrugs...
- 105. ...or whatever floatsyour boat
- 106. Remind yourself totake breaks
- 107.
- 108. HAVE FUN! meh
- 109.
- 110. LEARN about others andabout yourself
- 111. Thank you forlistening! bryanbibat.net | @bry_bibat speakerdeck.com/u/bryanbibat
- 112. For the bored, here'sme doing a dry run: http://youtu.be/ZE15NycXHJk (2 hours, 1 app)
- 113. Thank you forlistening! bryanbibat.net | @bry_bibat speakerdeck.com/u/bryanbibat