You’ve got X hours to produce something that works, is impressive and useful. • You bring nothing but a laptop and an idea, Build team and hopefully leave with working code (prototype of the future product/feature).
• It gives you an excuse to learn something new and challenge yourself. • Prove your NerdFu to the world. What can you do in 8 or 12 or 24 hours? • Meet with likeminded people, share ideas and build something useful.
problem to solve, that you think you can solve with what you know now + 2-‐3 new things. • Find a toolset to use -‐ either one you know or want to explore. • Keep your scope limited!
to tackle. • What do you need to write for that? • How many new things are you going to have to learn to make it happen? • Lets try to keep it to three new things and one or two features.
open source as you can! • Use open APIs to get you started quickly, but only ones that automa^cally provision (you don’t have ^me to wait around). • Do exactly one thing at a ^me.
X hours. I was running out of ^me and eventually had to give up gedng everything I wanted. • I moved a lot of things around and messed around trying to get the popover stuff working. • It’s not pre0y, but I solved the basic problem!
^me. • Don’t start on feature 2 un^l #1 is finished and working in a demo-‐able way! • Keep your goals limited and well-‐defined. If you have ^me, you can add more, but at least get the very basics working.
to solve. • Have a basic plan for what toolset you’re going to use. • Install pre-‐requisites (but don’t start coding, seriously) • Get your API keys!
into 3 four-‐hour chunks, with check-‐ins every hour. • Everyone has deliverables that have to be done in that ^meframe. • You can come up with this plan ahead of ^me... it will save organizing ^me later.
don’t be afraid to drop them and re-‐evaluate. Remember, the goal is to have something working to show at the end! • If you need to, jump in and help with a specific feature to get it working.
walk around. • Sleep if you have to, but if you start sleeping, you might not be able to stop. • Pace yourself -‐ don’t load up on caffeine too early! A slow steady supply will keep you up and alert. • Don’t eat too much. It’ll make you sleepy.
Chat • The Kayako REST API lets you quickly develop applica^ons to connect and integrate into your Kayako helpdesk. • Kayako Staff API for Mobile App Development • Kayako Apps and Hooks • hAp://wiki.kayako.com/display/DEV/Kayako +Developer+Resources+Home
salaria
wooootack
minorun365
sansan33
har1101
oracle4engineer
visional_engineering_and_design
kohbis
nwiizo
.PNG){kind=avatar}
aloerina
blueb
speakerdeck
irinanazarova
tammyeverts
kneath
samlambert
thoeni
jacobian
bkeepers
panda_program
aki_iinuma
samanthasiow
bryan
![Mahesh Salaria [email protected] h0p://twi0er.com/salaria Thank You](https://files.speakerdeck.com/presentations/69307f1019650132e2f872a17a4ff112/slide_19.jpg){kind=link}