presentation at the pre-event meetup

1. Preparing for the
WebGeek DevCup
Bryan Bibat
pangkaraniwang developer

2. 6 Hours

3. NOT
ENOUGH
TIME!

4. Solution:
Do everything that you can
do before the event

5. according to the rules:

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. HOWEVER

9. Languages & Tools:
Applications may be assembled
using any mix of programming
languages, application frameworks,
and development tools.

10. You cannot pre-build an app,
but you can pre-build a framework.

11. framework
≈
app that does nothing

12. Rest of this talk:
●
Preparing your App/Framework
●
Preparing everything else

13. For professional developers:
nothing new here!

14. App Prep

15. Languages?

16. Frameworks?

17. Databases?

18. Third-party APIs?

19. doesn't matter
(had app)

20. Choose what you are
comfortable with

21. less time Google-ing
=
more time coding

22. Once you've decided...

23. Build your "framework"

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 to add modules found
in other frameworks

29. Framework Modules
Front End Design Frameworks

32. Framework Modules
Page Templating

36. Framework Modules
Administration

38. Framework Modules
Authentication

39. Framework Modules
Pagination

40. demo

41. Apart from framework setup,
your biggest potential time
waster would be...

42. Machine Prep

43. Install everything
beforehand!

44. Don't expect the Wi-Fi to be
flawless on the event

45. Make sure everyone in your
team is able to execute and
develop your app

46. Possible option:
Virtual Environments

50. Once you can run the app, go
install whatever you want in
your machine

54. Have a backup internet
connection

55. Make sure everyone in your
team is able to execute and
develop your app

56. Revision Control

57. "If it's not in 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 you didn't cheat

60. Doesn't matter what you choose
as long as you use one

64. Share your code.
Don't worry about people
copying it.

65. Deployment

66. Making your app available 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-based hosting

75. Option 2:
Deploy Automation Tools

79. one command:
cap deploy

81. Everything's prepped except the
most important part...

82. Team Prep

83. Communication is key!
(yes it's cliche)

84. asset creation and integration,

85. asset creation and integration,
conflict resolution,

86. asset creation and integration,
conflict resolution,
bug finding and fixing,

87. asset creation and integration,
conflict resolution,
bug finding and fixing,
feature creation and pruning,

88. asset creation and integration,
conflict resolution,
bug finding and fixing,
feature creation and pruning,
etc.

89. No ideal group composition -
work with what you have

90. Mostly devs?
Focus on the functionality. Take
risks in experimental technology.

91. Mostly designers?
Limit features but polish them.
Focus on making your app usable.

92. Don't forget the basics!

93. Problems are easier to fix
in design than in code

94. POP QUIZ

95. Your software project is
running very late,
what do you do?

96. Your software project is running
very late, what do you do?
A. Add more people to the project

97. Your software project is running
very late, what do you do?
A. Add more people to the project
B. Make people work harder

98. 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

99. If you answered A or B,
I have bad news for you

100. 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

101. Self Prep

102. Get some sleep

103. Bring a jacket

104. Say no to drugs...

105. ...or whatever floats your boat

106. Remind yourself
to take breaks

107. HAVE FUN!

108. HAVE FUN!
meh

109. LEARN

110. LEARN
about others and about yourself

111. Thank you for listening!
bryanbibat.net | @bry_bibat
speakerdeck.com/u/bryanbibat

112. For the bored,
here's me doing a dry run:
http://youtu.be/ZE15NycXHJk
(2 hours, 1 app)

113. Thank you for listening!
bryanbibat.net | @bry_bibat
speakerdeck.com/u/bryanbibat