Introducing HackOne for Chrome

Nearly 4 months ago, I launched a project called HackOne. You were able to store information such as your shirt size, dietary needs, work history and projects you've built and you could share all of this with any hackathon you wanted to in a single click. It formed an incredible way to sign up to any hackathon you wanted to.

However, it did have its issues. Adoption was/is slow, and that was largely because people didn't want to have such data online, myself included, and with good reason. The growth we've had has been great and I know we had a few power users, and for that, I'm thankful and have been working on a new version.

With that being said, I'm proud to announce the future of HackOne. Introducing HackOne for Chrome.

Your data is finally secure and local.

I have focussed on building a Chrome extension that is truly secure, with no backdoors, and no way for us to access that data without your authorisation through the Chrome tab. It utilises Chrome's storage APIs and syncs across all of your devices. We have a new "domain verification" layer that asks you for additional permission if we're not sure about how they might handle your data.

Our beautiful JSON editor

The beautiful JSON editor that was in HackOne has been ported over to Chrome and now you'll be able to edit your profile within the luxury of your Chrome settings. I'm excited that we managed to pull this off and hope that it will improve further over time.

Easy to integrate, easy to use.

Our old integration no longer works because of Chrome compatibility reasons, but we've adhered to a new EventListener that we will be permanently using from now on. You'll get access to the same data and you can do almost all of the exact same things. Our documentation can be found online and we're improving it as frequently as we can.

Try it out.

For safety reasons, all users who've previously created a HackOne account online will have their data permanently destroyed. There will be no way to retrieve it and you'll need to create another account, but it's all in the name of security.

That aside, I invite you all to try our public beta by visiting

My first two North American hackathons

Earlier this summer, I received an invitation to attend two incredible student hackathons, PennApps and Hack the North, in the United States and Canada respectively.

These events happened within the last 10 days. I have only just caught up with my sanity to write about it all. I had the opportunity to attend other US hackathons and one in Croatia, but I turned them all down for these two. Why? They both stood out in very different ways - PennApps is the oldest student hackathon in the world and Hack the North is the newest student hackathon in the world. A bonus was they both offered to pay for my travel (out of few other British students) and thus my decision was then already made.

As I'm about to board my flight back to England, I thought it would be worth sharing my incredible short trip to North America.

PennApps X

When I arrived in Philadelphia for PennApps, I immediately felt this surreal sense of excitement for what seemed like an out-of-this-world weekend of hacking. PennApps was located in Central Philly and was unbelievably easy to access through Philly's awesome underground system.

The hackathon was spread through numerous buildings throughout the entire Penn campus. It really did give off a unique feel like PennApps had really took over Philadelphia. They had different buildings for food, hacking and presentations all of which were a five minute walk from each other.

Picture: Tomer Kagan keynoting PennApps X

Tomer Kagan, kicked off the tenth edition of PennApps with a talk about the company he founded, Quixey. We was then welcomed by ex-Penn students who were two-time past winners of PennApps and are on an adventure with their startup that was born right of the PennApps experience. I'll admit: the amount of APIs and hardware was insane and I'm still trying to catch up on what they all were.

There was a large emphasis on prizes and health; the grand prize was $5,000 and copious on copious amounts of hardware. I'll quickly note that I am not a fan of cash prizes whatsoever. I know a competitive hackathon when I see one, and PennApps was exactly that through the cash offerings. However, the exploration into making health an integral part of their hackathon culture was interesting and I'm excited to see where this goes in the future. And quite a few of the sponsors attending were actually Penn alumni.

I arrived to the event with a pre-made team (via their Facebook group) but it just didn't happen. We never found an idea we were all equally passionate about and the competitiveness of the hackathon quickly pushed us all away. Even as an experienced programmer, I was treated as a lone beginner (which was refreshing and provided an interesting perspective) and I felt essences of a culture which did not welcome fellow hackers. What about hackers at hackathons who don't come with friends or aren't female? There is no exceptions with making anyone feel uncomfortable, and I'll make sure I address this as an organiser myself. A reason for this was largely because everyone had already made teams, including myself, and it gave off almost a "transactional" feel with people already arriving and knowing what is expected of them in exchange for food, sleep, swag and the possibility to win or no prizes. Maybe the overwhelming popularity and overall strict selectiveness of PennApps got everyone topping the charts for what was a whole new spectrum of competitive. The point was, the environment at PennApps was not the best I've ever seen. The buildings and schedules were definitely confusing (though the text updates were somewhat of a life saver) and some sort of "small tours" prior would have been oh-so beneficial.

The food at the event was incredible. The pretzels, the Insomnia cookies and even the infamous cheesesteak - I was frequently reminded that I was in Philly. You can definitely see the PennApps organisers worked on the quality and content within the meals in detail.

The "science fair" demo format (everyone had a table and judges walked around) was something I was excited to see for the first time. Sponsors would walk around to hacks that implemented their challenges and judges would look at every hack in order to pick the top ten finalists. However, after speaking to a lot of fellow hackers, it was apparent that judges didn't even visit every table which would make it unfair. I didn't particularly attempt to win any prizes as I wanted to take the opportunity to learn Swift and build my first app alongside the support from incredible Apple engineers onsite. Overall, I loved PennApps but it taught me the problems of scaling hackathons.

Hack the North

This was the first large student hackathon in Canada at the University of Waterloo. The reason why I was equally as excited about this hackathon was because they wanted to take risks - and lots of them.

Having arrived in Toronto (where I was seriously minutes away from missing my flight, phew!), I took their shuttle to their university campus which was 1.5 hours. We left our coach in the freezing cold that is Canadian nights and checked in tents outside their phenomenal engineering building. It was something spectacular.

Picture: Chamath Palihapitiya being interviewed by Jason Calcanis

I arrived with no team. I found two hackathon newbies and we built an incredible hack with great contributions from everyone. The one thing I can applaud from both PennApps and Hack the North is the quality of attendees - everyone was incredibly passionate about hackathons!

Then the opening presentations. Wow. Wow. Wow. Wow. Wow. Wow. Wow. Wow. Yes, it is worthy of that. And another one: Wow. No hackathon in the world will be able to beat the speaking lineup of the Hack the North. It included Jason Calcanis (famous Silicon Valley investor), Chamath Palihapitiya (billionaire largely by taking Facebook to a billion users), Sam Altman (President of Y-Combinator), Eric Migicovsky (founder of Pebble) and Evan Stites-Clayton (founder of Teespring) and I don't think I'm even halfway through. Their talks were really awesome, but nothing in the world could beat their sheer presence. They could have not said a word and I would have been just as impressed.

Now we had to get back to hacking. I think the Wi-Fi was that good at both PennApps and Hack the North that I forgot I had to mention it. The commitment from sponsors was unique and many of them wouldn't sponsor other hackathons. Also, again, an insane amount of sponsors!

Of course, I did see growing pains with Hack the North. The presentations were in a building really far from the hacking building which was really uncomfortable in the freezing Canadian cold. Even grabbing the food at the tents outside during the night was not particularly pleasurable. There wasn't enough food for everyone either. However, the obsession with Tim Horton's (Canada's answer to Starbucks) definitely made me feel like I was Canada and that I actually was!

Even after a phenomenal amount of hacking (which was put short considering it started at midnight and we decided to sleep!), I had little idea on how best part of the event was yet to come. The judging process was very risky (which was different) and I was impressed by the attempt to be unique. But when the top 10 teams were selected out of 200 teams, little did I know they didn't have a grand prize - all 10 teams won the same prize of one selection of a list of devices (including Apple Watch)!

Nobody seemed like they were left out, and the volunteers at the event was super phenomenal. They were all as passionate about other people to put Canada on the map and I'm super excited about having England do the same when we welcome North American students!

Tiresome but incredible

I don't think I've written so much code over the two weekends for a very long time. I'm already exhausted and don't know how students on the other side of the Atlantic can go to a hackathon of this scale every weekend. I still can't fathom the logistical insanity that must go into these as organisers.

I think it's worth to note I applied to the last two PennApps and was rejected from both (along with the many other hackathons in the US!) and all I did was contribute a lot more on GitHub which seemed to help me massively. Finally, I had the opportunity to see first hand what Mike Swift and MLH were doing for the US student hackathon scene and I couldn't be more excited to help them grow MLH in the UK.

Now back to sleep, only with even more excitement!

The unofficial Yo API for Ruby

I will be attending the awesome Yo hackathon in New York this week considering their event in SF was incredibly successful. Looking at their documentation, I seen there was no love shown for the awesome Ruby community and so I decided to write one over a few hours in my friends apartment in NYC.

As with all of my work, I have tried to put a bit of flavour into it. I haven't written tests but you're more than welcome to on GitHub and it is available under the "yo-ruby" gem. I would love to see what awesome stuff people build with the wrapper and if you're hanging at the hackathon, don't forget to say hi!

San Francisco & Silicon Valley

I think I was born for San Francisco.

I mean, who wasn't? This place is frequently referred to as the tech capital of the world, where the technically gifted gods of the world flock to the beautiful parks of San Francisco to smoke a few joints in aid of inspiration for building "the next big thing". There is a strong emphasis about young talent all over the world, but the only thing it means in SF is the opportunity to take risks with little-to-no lifestyle complications. There is equality flourishing everywhere, even within the homeless, within the land of opportunity - with the real winners being the landlords.

When I arrived late in SFO one month ago, it hit me. The cold nights, that is. The land of opportunity doesn't let you down, even on the weather, and the consistency of such a schedule makes time seem to go so fast and I can attest to this. This place moves so fast on technological advancements, but the culture of the West Coast does not align with such a pace and so you are masked with the chilled out culture. You can't make a bigger impact by working harder here, it's all about working smarter.

The living cost absurdity that is SF is world renowned. It doesn't take a new-funded startup to understand why proud San Franciscans refuse to leave the city and so are forced into the cruel world of gentrification which leaves them homeless on the cold streets of SF.

Besides the normal good and bad, I have met so many incredible people in SF. There are some people who have took it for granted, but I'm not one to argue with human nature and I personally love the lack of interest towards elitism which allows a higher focus towards solving some of the many problems the world currently has. To put this to test, I have spoken to numerous successful founders stay at "hacker hostels" out of preference who can easily afford to rent something better.

I originally thought SF was a part of Silicon Valley. I was wrong. SV is where it all started but it is a suburban area dominated by cash-rich tech companies such as Google, Facebook, LinkedIn and eBay amongst many others and SF has been upcoming for the past decade. You can't really tell the difference these days. I would argue that SV isn't a place for young tech people who are still trying to understand where they fit in the world, unless you're looking for a very well paid job at a large tech company.

It's kind of obvious software engineers are scarce in the Valley. Software engineers who aren't happy are even more scarce. They are considered the kings of progression and innovation, but equally as important, the non-engineers are the kings of happiness and pure sanity. I didn't actually know how easy it is to go nuts as a programmer. We obsess about problems that take years to solve and attempt to solve them over weeks and months. Equally so, there is a unique level of thinking in the Valley and the expenditure towards trying new paid products is far greater than anywhere else makes it very easy to build a startup that only works in the Valley; people don't move from the other side of the world and deal with the stringent US visa process to change the already-always-changing Silicon Valley.

San Francisco & Silicon Valley really are as good as you want them to be. Inspiration lurks on every street in the Valley and many are sensitised to it, even if there's a lifetime supply of this scarce commodity for technology. No other place can compete for SF on this basis alone, but I can point the largest attribute to the success of the Bay Area towards the West Coast culture. You can easily leave this town knowing nothing new, or you can leave as one of the greatest innovators that ever lived.

Hybrid ecosystems

When I realised we live in a world obsessed with ecosystems, I got really excited.

I like to think of the World Wide Web as an ecosystem of ecosystems. Building an ecosystem is empowering people; a well-known premium of the old world. Anyone who has access to the Internet is empowered enough to teach themselves whatever they want, whenever they want which is truly incredible no matter how many times it has been said.

Two days ago, I was visiting Stanford University to hear Bill & Melinda Gates commencement speech (which is available on YouTube; I highly recommend). When Bill talked about how allowing everyone to access a computer was a paradox, it interested me to think how if his philosophy were any different how it could have changed the course of the computer revolution itself. His philosophy is what made him the richest man on earth, but he believes in it for social good which is why he runs The Bill & Melinda Gates Foundation; an ecosystem itself.

Ecosystems exist in both open and closed varieties.

Ecosystems are a wonderful thing, but there is often controversy about closed ones. Namely Apple. They have built one of the most popular ecosystems on the Internet, which is the App Store, but offer a limit to how what people can build on it. People are often in doubt about whether it is a right design for an ecosystem of such large reach, but given its monopolisation, people still build applications on top of it.

In contrast, there are plenty of open ecosystems. The most obvious one is the World Wide Web itself, which is unregulated by design. It is one of the reasons the governments and ISPs are constantly trying to filter content they subjectively believe should not be accessible to us. The ramnifications of an open ecosystem have damaged industries all over the world, but have forced them to cease or adapt.

Open ecosystems are powerful because people have been fully empowered, but also are incredibly saturated and can cause unparalleled levels of damage (i.e. lost revenue and jobs) in certain cases because there is no monopolisation in an open ecosystem.

Hybrid ecosystems

I don't want to build a closed ecosystem. I don't want to build an ecosystem that is so open that it causes problems or saturation either. I believe in the concept of a hybrid ecosystem that empowers and motivates users to build deeply on top of the ecosystem, yet closes on a certain level in order to build a high quality ecosystem that holds a large reach and equally a large impact towards its purpose or market.

This is purely a food-for-thought note, though I'm very interested in hearing your thoughts.

Improving email address input

In the past few years, I have become less of a hardcore programmer and more of a generalist. I have a large fascination into developing beautiful products by way of design and UX.

In my first foray into improving user experience, I have observed that we could make typing emails in better. That one less keystroke and click that save users those simple seconds into getting what they want. You want people to become habitual with your products.

Anyway, over a few hours, I decided to hack up a prototype of email autocompletion.

The idea is not to autocomplete everything on earth. You'll only want to suggest the domain the user may have considering it is likely to be mutual (i.e., and so it can prove useful. This doesn't warrant the need to make an AJAX request upon every keystroke, so I would recommend caching a list of the top 100 (or n) email domains typed in by users into JavaScript.

I have kept this short and sweet, but the beauty is, UX is all about that. And it's open sourced as a jQuery library. Let me know your thoughts.


The news has broken that Apple has acquired Beats Electronics for $3.2 billion. Nothing unanticipated; the discussion of acquiring Dr. Dre's most successful venture yet has been subject of talks for numerous weeks now. The core reason why Apple is considering Beats is because they have become a deteriorating subset of the consumer-music industry - which ultimately was their first foray into global success - and watching other companies such as Spotify, Pandora and Rdio change the way consumers pay for music has largely affected iTunes.

The perception of Beats lines of headphones and musical devices is they are very well designed but focus less on engineering feats and more on brand development and endorsements. The world's most successful stars are wearing Beats and its success is entirely built on such a foundation and that's entirely opposite to what Apple's foundations were built on - great products that sell themselves.

Though, I'm still not sure how Beats aligns with Apple. Here is what I've gathered.

  • Apple is planning to announce a product (most likely a music streaming service) that aligns with music for WWDC.
  • Apple plans to launch Beats in new countries.
  • There is no merger with Beats; it will still run independently.
  • Consume the talent behind Beats and give music a refresh within Apple.
  • Capture the revenue of Beats and further increase their cash reserves weekly.

Quite literally, out of a $150 billion cash reserve, it costs them around 2%. There is no risk here whatsoever and I think that's a great consideration to why Apple pulled through. I guess I'm questioning more about whether bringing Dre as a newly-minted Apple executive is a good idea considering Dre's motivations are highly around money and arguably less so for innovation. There is clearly no bad acquisition here, however.

One thing is for certain, however; if I ever do work for Apple, it would be pretty cool to say Dre is my boss.

The doubt of innovation

My two best attributes are craziness and naivety. In traditional sense, these go with age; I consider that a problem. In correlation, with age, you are becoming more aligned with behaviourial patterns ultimately defined and influenced by other people. Naive people ultimately have to attain such an experience for them to become aligned, and as such, have the unique opportunity to question what the very basis most of our surrounding society aligns with. Crazy people will embrace the attribute of being naive and take advantage of it.

In today's world, the biggest innovations are those which are simple. Communication and social are very hot areas in Silicon Valley right now and that's why the billion dollar acquisitions for unprofitable startups in this space are happening. Innovation often holds strong prestige from other people who try to innovate and often big companies will want to capture such prestige to help them acquire customers and talent.

Two innovations we all know of are Facebook and Twitter. They solve the same problem with the same solution, both using different approaches - similarly to caged and organic eggs - where they both have the same output but using their own respective methods of production. Twitter is almost uncensored and organic solution and Facebook offers a complex (and a forever imperfect) algorithm that will decide what you should see in your News Feed.

Crazy people are often the best innovators; it is crazy (pun intended) to think there was once no place for them. Those who perservered and made an impact, we remember. There are so many great innovators today, that alone is not enough and thus we are likely to forget those who don't donate money to charity or those who actually care about their employees over their wealth.

Let me state the obvious: Innovators love to innovate. Engineers love to engineer. Designers love to design. That is the child-like philosophy that we should all believe is true and real. But the unnecessary complexity of society teaches us to overthink in a non-conclusive way that we forcefully forget to think at all. The day that happens, I will no longer have the opportunity to innovate - ever.

Besides being crazy and naive, I'm also awkward and incredibly observational. These both have their advantages in that in my state of awkwardness, I take the time to observe my surroundings and often try to identify problems constantly and I largely accredit this ability from being self-taught as I had time to for my own style of identifying and solving problems. With school, you're being mass induced with the same discipline as every other person in your class which means you're never behind, but consquently you're also never in front.

The one thing I love about being able to innovate is that it doesn't have to be subjected to the health of our societies or economies. You'll be subjected to them when you build a product out of your innovation; but experimenting is the beauty of innovation. You don't know if it will work or not, and we rarely find an individual who posesses a limitless scope of execution. That isn't easy, but it is far easier today than it was when few innovators existed globally. Now there are societies within societies of innovators.