This document summarizes a Hack Day event hosted by Yahoo!. It provided an overview of the event structure and goals, highlighted example hack projects from previous events, offered tips for hacking strategies and demo presentations, and promoted Yahoo!'s open source projects and APIs that could help support hack projects. The Hack Day encouraged participants to build prototypes of ideas over a 24-hour period by noticing problems, building things they would find useful, automating manual tasks, and paying attention to technology trends. Successful hacks were simple, unique, and leveraged free/open source technologies.
10 Things Every Private School Should Do On YouTubeTravis Allison
Every great private school should have a presence on YouTube.
In this presentation (originally presented at the Private School Principal's Course at York University in Toronto) Travis Allison describes how to get noticed on YouTube.
There are several practical YouTube Tips for private/independent schools in the presentation.
Contact Travis (travis@socialcatalyst.ca, 519.532.7366) if you would like him to bring a customized version of this presentation to your company or organization.
Check out http://socialcatalyst.ca/ofis for more great private school marketing ideas.
This ppt is a light-hearted and abridged summary of my achievements, at least for 2009.
It shows a deep interest towards all forms of communication and I hope that it effectively communicates the fierce resolution to create remarkable whenever the opportunity arises...
10 Things Every Private School Should Do On YouTubeTravis Allison
Every great private school should have a presence on YouTube.
In this presentation (originally presented at the Private School Principal's Course at York University in Toronto) Travis Allison describes how to get noticed on YouTube.
There are several practical YouTube Tips for private/independent schools in the presentation.
Contact Travis (travis@socialcatalyst.ca, 519.532.7366) if you would like him to bring a customized version of this presentation to your company or organization.
Check out http://socialcatalyst.ca/ofis for more great private school marketing ideas.
This ppt is a light-hearted and abridged summary of my achievements, at least for 2009.
It shows a deep interest towards all forms of communication and I hope that it effectively communicates the fierce resolution to create remarkable whenever the opportunity arises...
If good design requires failure, how can designers f*ck up when failure isn’t considered an option?
Edison famously said, "I failed my way to success." In the interactive world, we've all heard the buzz phrases about failing fast, and how failure--particularly in the form of prototyping--can be a powerful design tool. But what about real failure? We've all experienced projects that never got off the ground, or crashed and burned stunningly. We don't put them in our portfolios. We only talk about them when we've had one drink too many. What can we learn from our embarrassments? And are there really things we can learn by failing, especially in the agency and consulting worlds, where we are hired for our expertise, and infallibility?
Questions to think about:
Can there be actual power, and knowledge in failure? What is your biggest failure, and what did you learn from it?
What are the different ways you can fail? Have you ever had a "successful" project that was a personal failure? Why? What can you learn from it?
Why are we so afraid of failing? What are the negative consequences of failure? And how can we encourage a positive viewpoint on failure?
How can we pull victory from the flames of defeat? How do you not panic when you sense yourself failing? How can you use your failure to inform future successes?
How can we build an acceptance of failure into a design or consulting practice? How can we get away from always having to be right, and move towards creative adaptability?
One version of a talk I give now and then about my life plus some ideas & observations on entrepreneurship, career, and how to live a unique and fulfilling life.
My introduction talk to the Open Hack Day in Bangalore, India, 2010 explaining what a hack is, how to build hacks quickly and how to present your hack once you are done.
This powerpoint was part of a webinar and USTREAM show with the purpose of providing brief context and history of online video tools and exploring their uses for teacher professional development and education.
The related webinar can be found in the Archived section of the RETA Webinars site at http://webinars.nmsu.edu
5 ROOKIE MISTAKES you should ABSOLUTELY not makeFloown
We’re all human. And unfortunately that means that every now and then you forget to turn on your brain. Especially when you run a startup there’s the occasional gaffe that in retrospect seems absolutely embarrassing. HOW COULD WE BE SO STUPID?
For this one we had to dig quite deep into our memory. Since we’re running such a tight ship we could only muster up 5 rookie mistakes…
Nah, not even Team Floown is perfect. But as Barack Obama said: “You try to figure out how to be in the moment, make the best decision you can, know that you’re going to get a bunch of them right, but a bunch of times you’re also not going to get it exactly the way you want it.”
Meaning, don’t fret too long over all the small mistakes. You can have a bad morning, a bad afternoon, but when you keep focused and positive you might write the most genius code, design the most beautiful logo, or make the best decision in the evening. Just because you kept at it, and let loose the negativity of what was before.
Our rookie mistakes hopefully make you laugh. Put a smile on your face. And when you run an into a similar situation, hopefully you won’t make that same mistake. But more importantly, always remember to keep on moving. After five mistakes, the sixth thing you do might be the best thing you’ll ever do.
www.floown.com
Presenter:
Krystal O’Connor (@kocotech)
Session Description:
If you’ve ever considered having a video podcast or holding a Google Hangout on Air (HOA), this session will cover the benefits to having a live video counterpart to your audio or video show, and how you can leverage video even for a primarily audio podcast to connect with your community. This session will cover how to conduct effective Google Hangouts On Air as well as working with on-demand video, best encoding practices, and giving your viewers every possible way to watch your show.
Category:
Video/Podcasting
Takeaways:
Learn how video can help grow your community through face to face live sessions, and reach into one of the largest video networks around, YouTube.
Step by step, learn how to create a Google Hangout On Air from scheduling to inviting, having guests, utilize apps inside of Hangouts, and conduct the event.
Also covered will be how to obtain an offline copy of the video for editing, as well as publishing (answering questions such as should I host audio and video on the same podcast feed?) and distribution of the event for on-demand.
JavaScript App Security: Auth and Identity on the ClientJonathan LeBlanc
The story is always the same; if you want to create a JavaScript centric app with API and identity security, you’re told that you need to have a server-side component for handling your identity and application security. That’s simply not the case in modern development.
In this session we'll look at client-side identity, API, and token security, exploring token downscoping methodologies, key management tools, and security on the client.
Improving Developer Onboarding Through Intelligent Data InsightsJonathan LeBlanc
A developer platform lives and dies by it's developer community. When huge problems need to be solved, it's easy to make valuable improvements, but what do you do when those are solved and you still see high bounce rates on your site, low developer application completion, and generally poor adoption of your product? This is where your data can save you.
In this talk we'll run through:
- How to track valuable developer path insights, from moments of anxiety to time to first valuable call.
- Overlaying support and ticketing information on top of developer path data to decrease developer friction.
- How to create automated analytics systems to measure success.
- When these systems should be built, before it's too late.
If good design requires failure, how can designers f*ck up when failure isn’t considered an option?
Edison famously said, "I failed my way to success." In the interactive world, we've all heard the buzz phrases about failing fast, and how failure--particularly in the form of prototyping--can be a powerful design tool. But what about real failure? We've all experienced projects that never got off the ground, or crashed and burned stunningly. We don't put them in our portfolios. We only talk about them when we've had one drink too many. What can we learn from our embarrassments? And are there really things we can learn by failing, especially in the agency and consulting worlds, where we are hired for our expertise, and infallibility?
Questions to think about:
Can there be actual power, and knowledge in failure? What is your biggest failure, and what did you learn from it?
What are the different ways you can fail? Have you ever had a "successful" project that was a personal failure? Why? What can you learn from it?
Why are we so afraid of failing? What are the negative consequences of failure? And how can we encourage a positive viewpoint on failure?
How can we pull victory from the flames of defeat? How do you not panic when you sense yourself failing? How can you use your failure to inform future successes?
How can we build an acceptance of failure into a design or consulting practice? How can we get away from always having to be right, and move towards creative adaptability?
One version of a talk I give now and then about my life plus some ideas & observations on entrepreneurship, career, and how to live a unique and fulfilling life.
My introduction talk to the Open Hack Day in Bangalore, India, 2010 explaining what a hack is, how to build hacks quickly and how to present your hack once you are done.
This powerpoint was part of a webinar and USTREAM show with the purpose of providing brief context and history of online video tools and exploring their uses for teacher professional development and education.
The related webinar can be found in the Archived section of the RETA Webinars site at http://webinars.nmsu.edu
5 ROOKIE MISTAKES you should ABSOLUTELY not makeFloown
We’re all human. And unfortunately that means that every now and then you forget to turn on your brain. Especially when you run a startup there’s the occasional gaffe that in retrospect seems absolutely embarrassing. HOW COULD WE BE SO STUPID?
For this one we had to dig quite deep into our memory. Since we’re running such a tight ship we could only muster up 5 rookie mistakes…
Nah, not even Team Floown is perfect. But as Barack Obama said: “You try to figure out how to be in the moment, make the best decision you can, know that you’re going to get a bunch of them right, but a bunch of times you’re also not going to get it exactly the way you want it.”
Meaning, don’t fret too long over all the small mistakes. You can have a bad morning, a bad afternoon, but when you keep focused and positive you might write the most genius code, design the most beautiful logo, or make the best decision in the evening. Just because you kept at it, and let loose the negativity of what was before.
Our rookie mistakes hopefully make you laugh. Put a smile on your face. And when you run an into a similar situation, hopefully you won’t make that same mistake. But more importantly, always remember to keep on moving. After five mistakes, the sixth thing you do might be the best thing you’ll ever do.
www.floown.com
Presenter:
Krystal O’Connor (@kocotech)
Session Description:
If you’ve ever considered having a video podcast or holding a Google Hangout on Air (HOA), this session will cover the benefits to having a live video counterpart to your audio or video show, and how you can leverage video even for a primarily audio podcast to connect with your community. This session will cover how to conduct effective Google Hangouts On Air as well as working with on-demand video, best encoding practices, and giving your viewers every possible way to watch your show.
Category:
Video/Podcasting
Takeaways:
Learn how video can help grow your community through face to face live sessions, and reach into one of the largest video networks around, YouTube.
Step by step, learn how to create a Google Hangout On Air from scheduling to inviting, having guests, utilize apps inside of Hangouts, and conduct the event.
Also covered will be how to obtain an offline copy of the video for editing, as well as publishing (answering questions such as should I host audio and video on the same podcast feed?) and distribution of the event for on-demand.
JavaScript App Security: Auth and Identity on the ClientJonathan LeBlanc
The story is always the same; if you want to create a JavaScript centric app with API and identity security, you’re told that you need to have a server-side component for handling your identity and application security. That’s simply not the case in modern development.
In this session we'll look at client-side identity, API, and token security, exploring token downscoping methodologies, key management tools, and security on the client.
Improving Developer Onboarding Through Intelligent Data InsightsJonathan LeBlanc
A developer platform lives and dies by it's developer community. When huge problems need to be solved, it's easy to make valuable improvements, but what do you do when those are solved and you still see high bounce rates on your site, low developer application completion, and generally poor adoption of your product? This is where your data can save you.
In this talk we'll run through:
- How to track valuable developer path insights, from moments of anxiety to time to first valuable call.
- Overlaying support and ticketing information on top of developer path data to decrease developer friction.
- How to create automated analytics systems to measure success.
- When these systems should be built, before it's too late.
Better Data with Machine Learning and ServerlessJonathan LeBlanc
Creating valuable insights out of raw data files, such as audio or video, has traditionally been a very manual and tedious process, and has produced mixed results due to an influential human element in the mix.
Thanks to enhancements in machine learning systems, coupled with the rapidly deployable nature of serverless technology as a middleware layer, we are able to create highly sophisticated data insight platforms to replace the huge time requirements that have typically been required in the past.
With this in mind, we’ll look at:
- How to build end-to-end data insight and predictor systems, built on the back of serverless and machine learning systems.
- Best practices for working with serverless technology for ferrying information between raw data files and machine learning systems through an eventing system.
- Considerations and practical examples of working with the security implications of dealing with sensitive information.
Best Practices for Application Development with BoxJonathan LeBlanc
Covering the best practices for building new applications on top of Box platform, including token management, error condition and program flow, architecture, and other such topics.
This topic will go through current standards and future trends for building a scalable security model for distributed cloud based data. We’ll look into practices and considerations behind handing highly privileged data globally, diving into topics such as:
- How global compliance and regulations affect security practices.
- Handling data permissions, identity, and security with application access to data.
- Considerations, trends, and standards for global data availability.
Building a modern API architecture is a constant struggle between ease of development and security. JSON Web Tokens (JWTs) introduce a means of building authentication into JSON objects being transmitted through APIs.
In this session we’ll explore how JWTs work to build verifiable and trusted objects, allowing them to be combined with standards such as OAuth 2 for capturing access tokens, leading to a secure means of JavaScript SDK dev.
Creating an In-Aisle Purchasing System from ScratchJonathan LeBlanc
The future of retail is in removing the divide between the offline shopping state and the enhanced online buying experience. To create this type of enhanced retail experience, we can remove complexities in the process, such as simplifying checkout.
In this session we’ll learn how to use internet-connected microelectronics to attach to a buyer’s mobile device to provide the functionality to buy products right from the aisle.
As web enabled systems become an integral part of everything we interact with, how do we secure data in potential unsecure environments?
In this session you'll learn how to apply fundamental security precepts in potentially insecure environments. Topics include:
Securing identity and payment data through voice commands or text
Tokenization and encryption security
Triggering secure transactions from communications media
We are in an age where more people have phones than toilets, and there are more active cell phones than people on the planet. How do we protect all of these devices roaming around unsecured locations, especially when they want to pay for something. Learn the secrets behind building a secure mobile backbone, as we explore how to harden security, build systems based on identity confidence, and work towards a future proofed mobile framework.
The arena of proper auth & data security standards is often some of the most misunderstood, confusing, and tricky aspects of building Node apps. Using open source auth techniques and proper data encryption standards, we’ll learn how to make intelligent decisions on creating a solid infrastructure to protect our users and data. We’ll dive into auth systems, data attack vectors, how to protect your systems, and common security pitfalls in Node.
The screencast of this presentation can be found at https://youtu.be/o3uy7dgG_n4
There is an assumption in the industry, amongst companies large and small alike, that if they store sensitive user data (and sometimes do some mild encryption) in their database, it's locked in and secured from potential attacks. People rely too heavily on their false assumptions of security, and it usually ends up costing them extensively when that is proven wrong.
In this session, Jonathan will build a foundation for identity and data security that everyone dealing with sensitive data should understand. We'll break down concepts of identity security, common attack vectors and how to protect yourself, and how to harden your web application.
Web enabled systems are now an integral part of everything we interact with, from microelectronics to voice enabled hardware, from text messages and phone calls to email, and really we’re just limited by our imaginations as to what we can connect. As we explore vast new realms of communication over mixed digital media, we have to ask ourselves how we protect our critical data within potential unsecure environments. Going beyond that, how do we protect some of our more critical data, payment information, in this same realm.
As we look at a multitude of different environments, we’ll be exploring how to secure user identity and payment information through the communication channels, covering topics like:
* Securing identity and payment data through voice commands or text.
* Tokenization and encryption security.
* Techniques for triggering secure transactions from communications media.
At the end of the session, we’ll have a stronger understanding of proper techniques for working with new communication media sources, and see how we can apply fundamental security precepts in potentially insecure environments.
Audio from the session at OSCON (Portland, OR) on July 22nd, 2015 is available at https://archive.org/details/protecting_future_mobile_payments
We are now in an age where more people have phones than toilets, and there are more active cell phones than people on the planet. How do we protect all of these devices as they’re roaming around unsecured locations, especially when we want to pay for something.
In this talk we’re going to rip apart the illusion of mobile security and explore some of the most difficult to secure experiences: payments. We’ll cover the concepts of building a rich feature set to protect the user, how to encrypt all interactions, building scalable trust zones, and extending identification with wearables and biometrics.
In a world where technology is transforming with mobile devices and wearables, its key to have a solid security backbone. From having a strong password to using biometrics, companies are finding ways to help consumers protect themselves without impacting the experience. We'll take a look at the current landscape of passwords, the importance of proper systems and how we can use wearables and mobile devices to build trust systems.
21. And good ideas come from...
‣ No[cing something broken and
thinking of a fix.
‣ Building something you’d use yourself.
‣ Automa[ng something you are
too lazy to do manually.
‣ Finding a place where the world sucks
and figuring out how to make it beaer.
22. And good ideas come from...
‣ No[cing something broken and
thinking of a fix.
‣ Building something you’d use yourself.
‣ Automa[ng something you are
too lazy to do manually.
‣ Finding a place where the world sucks
and figuring out how to make it beaer.
‣ Paying aaen[on to trends: mobile, video,
social, local, geo, games, etc.
33. Hacking Strategies
‣ Brainstorm, but converge quickly, and
keep best details of rejected ideas handy.
‣ Scope the work so the end is in sight: set
an easy goal, and an ambi[ous one.
‣ Divide work by team member strengths.
‣ Ask for help!
34. Hacking Strategies
‣ Brainstorm, but converge quickly, and
keep best details of rejected ideas handy.
‣ Scope the work so the end is in sight: set
an easy goal, and an ambi[ous one.
‣ Divide work by team member strengths.
‣ Ask for help!
‣ Minimize the amount of work by using
free and open source tech.
35. Hacking Strategies
‣ Brainstorm, but converge quickly, and
keep best details of rejected ideas handy.
‣ Scope the work so the end is in sight: set
an easy goal, and an ambi[ous one.
‣ Divide work by team member strengths.
‣ Ask for help!
‣ Minimize the amount of work by using
free and open source tech.
‣ Don’t forget to Ctrl+S!
39. DEMO FTW
‣ “I swear it was just working...” ‐ have a
Plan B (screenshots, video, etc.)
‣ No sta[c slides ‐ leave PowerPoint for
marke[ng.
‣ Prac[ce your pitch a few [mes; make it
easy on the ears, concise and funny.
40. DEMO FTW
‣ “I swear it was just working...” ‐ have a
Plan B (screenshots, video, etc.)
‣ No sta[c slides ‐ leave PowerPoint for
marke[ng.
‣ Prac[ce your pitch a few [mes; make it
easy on the ears, concise and funny.
‣ Make a bang: demo what’s most exci[ng
and cool about your project.
41. DEMO FTW
‣ “I swear it was just working...” ‐ have a
Plan B (screenshots, video, etc.)
‣ No sta[c slides ‐ leave PowerPoint for
marke[ng.
‣ Prac[ce your pitch a few [mes; make it
easy on the ears, concise and funny.
‣ Make a bang: demo what’s most exci[ng
and cool about your project.
‣ Tell us how you’d like the project to grow.
Modify the names to include the name / logo of the school and names of the presenters.
Talk about origins of Hack Day: The original “clap-o-meter” for judging Hacks, a very grassroots effort among engineers to get away from daily routine and do something quick and cool.
A free t-shirt is the best prize for an engineer -- and winners got specially produced ones.
After clap-o-meter was deemed a bit unreliable, Hack Days got some esteemed judges.
The Hack Day spread to other Yahoo offices, with huge success
In fact, it was so successful internally that we decided we want to make it public. The first Open Hack Day took place on Yahoo campus.
Campus became campground: people put up tents on Yahoo! lawn and hacked from there, as well as from inside the buildings.
Yahoo! provided quality entertainment
And some more quality entertainment the next Open Hack Day
But just making the Hack Day public wasn’t enough -- there are many promising hackers at every university in the US who don’t have the means to travel -- so we are coming to you!
The Hack Agenda: modify according to where you are presenting.
Talk about the idea of hacker as someone who can dream up a great idea and then implement it. Dreamer + coder.
It’s not enough for a hack to be a good idea or concept -- the point is that you have the ability to bring it to life.
It’s not enough for a hack to be a good idea or concept -- the point is that you have the ability to bring it to life.
Where do good ideas come from?
Where do good ideas come from?
Where do good ideas come from?
Where do good ideas come from?
Where do good ideas come from?
A case study of a hack: InsiderTrades provides alerts whenever a particular stock you choose to follow is traded by insiders. The alerts are based on information publicly available from SEC. Other sources for this info? Delayed and expensive. So what’s good about this idea?
A case study of a hack: InsiderTrades provides alerts whenever a particular stock you choose to follow is traded by insiders. The alerts are based on information publicly available from SEC. Other sources for this info? Delayed and expensive. So what’s good about this idea?
A case study of a hack: InsiderTrades provides alerts whenever a particular stock you choose to follow is traded by insiders. The alerts are based on information publicly available from SEC. Other sources for this info? Delayed and expensive. So what’s good about this idea?
A case study of a hack: InsiderTrades provides alerts whenever a particular stock you choose to follow is traded by insiders. The alerts are based on information publicly available from SEC. Other sources for this info? Delayed and expensive. So what’s good about this idea?
A case study of a hack: InsiderTrades provides alerts whenever a particular stock you choose to follow is traded by insiders. The alerts are based on information publicly available from SEC. Other sources for this info? Delayed and expensive. So what’s good about this idea?
So, how do we build a winning hack? Here are some strategies.
So, how do we build a winning hack? Here are some strategies.
So, how do we build a winning hack? Here are some strategies.
So, how do we build a winning hack? Here are some strategies.
So, how do we build a winning hack? Here are some strategies.
So, how do we build a winning hack? Here are some strategies.
But it’s not enough to just build a winning hack -- in order for it to win, you have to showcase it. Demo strategies are important.
But it’s not enough to just build a winning hack -- in order for it to win, you have to showcase it. Demo strategies are important.
But it’s not enough to just build a winning hack -- in order for it to win, you have to showcase it. Demo strategies are important.
But it’s not enough to just build a winning hack -- in order for it to win, you have to showcase it. Demo strategies are important.
But it’s not enough to just build a winning hack -- in order for it to win, you have to showcase it. Demo strategies are important.