In 2012, AngularJS made us think about moving business logic completely into the client-side as an actually sensible idea. Meteor give that idea two thumbs up.
In 2014, it’s time for some sobering up. The backends we built over a decade in Ruby and Python aren’t going away. New languages like Go and Hack are tantalising us with new possibilities. Our applications are increasingly distributed, often involving third party APIs. In such a scenario, where does your business logic reside?
This year’s edition spans four days, with two days of workshops and two days of conference. All days feature a single track. We invite proposals for:
- Full-length 40 minute talks
- A crisp 15-minute presentation
- Sponsored sessions, 40 minute duration
- Flash talks of 5 minutes duration. Submissions for flash talks will be accepted during the event
- Three hour workshops where everybody gets their laptop out and follows along
Criteria to submit
You must be a practising web developer or designer, and must be able to show how your own work has advanced the state of the web in the past year. You are expected to present original work that your peers — this event’s audience — recognise as being notable enough to deserve a stage.
If you are excited about someone’s work and believe it deserves wider recognition, we recommend you contact them and ask them to submit a proposal.
Voting is open to attendees who have purchased event tickets. If there is a proposal you find notable, please vote for it and leave a comment to initiate discussions. Your vote will be reflected immediately, but will be counted towards selections only if you purchase a ticket.
Proposers must submit presentation drafts as part of the selection process to ensure that the talk is in line with the original proposal, and to help the editorial panel build a strong line-up for the event.
There is only one speaker per session. Entry is free for selected speakers. HasGeek will cover your travel to and accommodation in Bangalore from anywhere in the world for speakers delivering full sessions (30 minutes or longer). As our budget is limited, we will prefer speakers from locations closer home, but will do our best to cover for anyone exceptional. If you are able to raise support for your trip, we will count that as speaker travel sponsorship.
If your proposal is not accepted, you can buy a ticket at the same rate as was available on the day you proposed. We’ll send you a code.
Commitment to Open Source
HasGeek believes in open source as the binding force of our community. If you are describing a codebase for developers to work with, we’d like it to be available under a permissive open source license. If your software is commercially licensed or available under a combination of commercial and restrictive open source licenses (such as the various forms of the GPL), please consider picking up a sponsorship. We recognize that there are valid reasons for commercial licensing, but ask that you support us in return for giving you an audience. Your session will be marked on the schedule as a sponsored session.
Let’s learn from the collective intelligence of hundreds of contributors to take home at least a few coding lessons we can put to use immediately. Let’s focus on the language again and rekindle that romance!
Someone as smart as me was able to add these two things together and come up a topic for a talk!
- Did you know that the backbone.js is only 1600 LoC?
- Do you know how backbone router deals with the History API
- Do you know how backbone Object.extend pattern works?
- Do you know how backbone is instantiated?
- Do you like hacks and/or funny comments that make you smile?
In 40 minutes, we’ll take a look at some of the most interesting code snippets from the Backbone source and understand the clever hacks and patterns that have ended up there by the collective effort of hundreds of contributors. I hope you take away at least a few new patterns or ideas from this talk that you can start applying practically straight away.
Just knowing vanilla.js syntax should be enough.
He’s not sure whether he should be writing this in the third-person.