3 ms·
it depends on what hackathons are geared to doing - if it's _actual_ client/business work that they'd be doing normally, then it's not a proper hackathon, and j
by chii 10y ago
it depends on what hackathons are geared to doing - if it's _actual_ client/business work that they'd be doing normally, then it's not a proper hackathon, and just an excuse to get more hours out of the employees.
But if it's a free for all, do anything you want style, and participation is optional (truly optional, not fake-optional via management peer pressure), then it's a good sign.
- culturestate 10y agoMy hangup is that in either case, it's still extra work that benefits the company rather than the employee. It's performed on company premises with company equipment - gamified overtime, essentially. I suppose there's an argument to be made that a good employee can make it mutually beneficial (use the time to learn a new, marketable skill that can get them a raise or a better job), but still...
- dack 10y agoIn the situation the parent described, I find it hard to construe it as benefiting the company over the individual (other than naturally making the company more attractive to work for). We did this when I was at Guidewire and it was amazing. I explored Event Sourcing during a hackathon and eventually went on to build it into a product using those skills - it's a really happy memory. In another hackathon I built easter eggs into our internal seating chart application - the vibe of everyone hacking together was great. This was a hackathon where it was broad enough that "reading an interesting programming book" counted, and nobody really bothered you if you did something completely different.
- jasonlotito 10y agoExplain simply how building something the company won't use or learning something new on company time is essentially gamified overtime when doing this on normal company hours.