Preparing for the WebGeek DevCup

1,199 views

Published on

presentation at the pre-event meetup

Published in: Technology
0 Comments
1 Like
Statistics
Notes
  • Be the first to comment

No Downloads
Views
Total views
1,199
On SlideShare
0
From Embeds
0
Number of Embeds
640
Actions
Shares
0
Downloads
8
Comments
0
Likes
1
Embeds 0
No embeds

No notes for slide

Preparing for the WebGeek DevCup

  1. 1. Preparing for theWebGeek DevCup Bryan Bibat pangkaraniwang developer
  2. 2. 6 Hours
  3. 3. NOTENOUGH TIME!
  4. 4. Solution:Do everything that you can do before the event
  5. 5. according to the rules:
  6. 6. No Offsite Development: All development must beperformed on-site between the aforementioned start and end times for the event.
  7. 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. 8. HOWEVER
  9. 9. Languages & Tools: Applications may be assembled using any mix of programminglanguages, application frameworks, and development tools.
  10. 10. You cannot pre-build an app,but you can pre-build a framework.
  11. 11. framework ≈app that does nothing
  12. 12. Rest of this talk:● Preparing your App/Framework ● Preparing everything else
  13. 13. For professional developers: nothing new here!
  14. 14. App Prep
  15. 15. Languages?
  16. 16. Frameworks?
  17. 17. Databases?
  18. 18. Third-party APIs?
  19. 19. doesnt matter (had app)
  20. 20. Choose what you are comfortable with
  21. 21. less time Google-ing = more time coding
  22. 22. Once youve decided...
  23. 23. Build your "framework"
  24. 24. your framework must: ● run on a web server
  25. 25. your framework must: ● run on a web server● not have errors when browsed
  26. 26. your framework must: ● run on a web server ● not have errors when browsed● connect to a database, if needed
  27. 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. 28. Feel free to add modules found in other frameworks
  29. 29. Framework ModulesFront End Design Frameworks
  30. 30. Framework Modules Page Templating
  31. 31. Framework Modules Administration
  32. 32. Framework Modules Authentication
  33. 33. Framework Modules Pagination
  34. 34. demo
  35. 35. Apart from framework setup, your biggest potential time waster would be...
  36. 36. Machine Prep
  37. 37. Install everything beforehand!
  38. 38. Dont expect the Wi-Fi to be flawless on the event
  39. 39. Make sure everyone in yourteam is able to execute and develop your app
  40. 40. Possible option:Virtual Environments
  41. 41. Once you can run the app, goinstall whatever you want in your machine
  42. 42. Have a backup internet connection
  43. 43. Make sure everyone in yourteam is able to execute and develop your app
  44. 44. Revision Control
  45. 45. "If its not in version control, it doesnt exist."
  46. 46. The Joel Test (http://www.joelonsoftware.com/articles/fog0000000043.html)1. Do you use source control?
  47. 47. Also proves you didnt cheat
  48. 48. Doesnt matter what you choose as long as you use one
  49. 49. Share your code.Dont worry about people copying it.
  50. 50. Deployment
  51. 51. Making your app available onthe internet is optional, but will help in the judging
  52. 52. The Joel Test (http://www.joelonsoftware.com/articles/fog0000000043.html)2. Can you make a build in one step?
  53. 53. Option 1:Use push-based hosting
  54. 54. Option 2:Deploy Automation Tools
  55. 55. one command: cap deploy
  56. 56. Everythings prepped except the most important part...
  57. 57. Team Prep
  58. 58. Communication is key! (yes its cliche)
  59. 59. asset creation and integration,
  60. 60. asset creation and integration, conflict resolution,
  61. 61. asset creation and integration, conflict resolution, bug finding and fixing,
  62. 62. asset creation and integration, conflict resolution, bug finding and fixing, feature creation and pruning,
  63. 63. asset creation and integration, conflict resolution, bug finding and fixing, feature creation and pruning, etc.
  64. 64. No ideal group composition - work with what you have
  65. 65. Mostly devs?Focus on the functionality. Takerisks in experimental technology.
  66. 66. Mostly designers? Limit features but polish them.Focus on making your app usable.
  67. 67. Dont forget the basics!
  68. 68. Problems are easier to fix in design than in code
  69. 69. POP QUIZ
  70. 70. Your software project is running very late, what do you do?
  71. 71. Your software project is running very late, what do you do?A. Add more people to the project
  72. 72. Your software project is running very late, what do you do?A. Add more people to the project B. Make people work harder
  73. 73. Your software project is running very late, what do you do?A. Add more people to the project B. Make people work harder C. Cut unnecessary features
  74. 74. If you answered A or B,I have bad news for you
  75. 75. Your software project is running very late, what do you do?A. Add more people to the project B. Make people work harder C. Cut unnecessary features
  76. 76. Self Prep
  77. 77. Get some sleep
  78. 78. Bring a jacket
  79. 79. Say no to drugs...
  80. 80. ...or whatever floats your boat
  81. 81. Remind yourself to take breaks
  82. 82. HAVE FUN!
  83. 83. HAVE FUN! meh
  84. 84. LEARN
  85. 85. LEARNabout others and about yourself
  86. 86. Thank you for listening! bryanbibat.net | @bry_bibat speakerdeck.com/u/bryanbibat
  87. 87. For the bored,heres me doing a dry run:http://youtu.be/ZE15NycXHJk (2 hours, 1 app)
  88. 88. Thank you for listening! bryanbibat.net | @bry_bibat speakerdeck.com/u/bryanbibat

×