TE
科技回声
首页24小时热榜最新最佳问答展示工作
GitHubTwitter
首页

科技回声

基于 Next.js 构建的科技新闻平台,提供全球科技新闻和讨论内容。

GitHubTwitter

首页

首页最新最佳问答展示工作

资源链接

HackerNews API原版 HackerNewsNext.js

© 2025 科技回声. 版权所有。

Ask HN: Anyone else hate company "hack days"

83 点作者 throwarayes大约 1 年前
As someone that generally likes their day to day work, and dislikes arbitrarily Mandatory Corporate Fundays, I really just wish companies would stop this hack days nonsense. It just means I&#x27;m going to be more behind on tasks I&#x27;m already behind on.<p>To do a hackdays successfully, I find good projects have already had a lot of personal upfront investment before the hackdays project. The hackdays project then assembles a team of potential labor that might (or often not) accelerate the idea to a demo. And then, even if there&#x27;s a snazzy demo, you have to engage in a tremendous push after the hackdays to turn them into successful projects.<p>I can just as easily spend my time doing this in normal planning channels. And instead of hackdays, maybe we should encourage prototyping and demos to be part of the normal planning process, not some out of band activity likely to screw up schedules and deliver nothing.<p>Please, companies, stop these mandatory corporate fundays. And just fix your normal planning processes.

20 条评论

Jemaclus大约 1 年前
As an engineer, my view on days&#x2F;hackathons is pretty simple: you don&#x27;t pay me enough for my good ideas. If I had an idea that could make the business $5M, I&#x27;m better off going into business for myself. Instead, I&#x27;m going to do whatever I can to try something new and different to learn<p>So with that in mind, as a leader, I view them as opportunities for sanctioned on-the-job learning. I would hope that you spend the time automating existing processes or learning a new technology that might be useful. At our most recent company hackathon, we focused on a new way to do the old thing. Everyone could build basically whatever they wanted, but they had to use the new tool to do it. Not because we want the output, but because we want everyone to feel comfortable with the new tool. There was zero expectation about turning anything into a production project, although we did have two projects come out of it that are likely to go to prod soon without disrupting the roadmap.<p>I get where you&#x27;re coming from, and I agree wholeheartedly with your assessment. If your work is doing hack days, and then getting mad because features aren&#x27;t shipped, that&#x27;s pretty shitty of them. Might want to try and find another place with better culture -- easier said than done!
评论 #39450218 未加载
评论 #39451956 未加载
评论 #39449677 未加载
评论 #39452299 未加载
评论 #39471515 未加载
wilg大约 1 年前
If hack days are screwing up scheduling, that&#x27;s a scheduling problem. (You&#x27;ll have to figure that out with your company.)<p>If hack days are used to prototype work that&#x27;s definitely going to be done anyway, that&#x27;s a planning problem. (You&#x27;ll have to figure that out with your company.)<p>If people are investing work upfront just to make a good impression at hack day, that&#x27;s a cultural problem. (You&#x27;ll have to figure that out with your company.)<p>But generally, just relax and do something creative and fun and low-pressure.
评论 #39451282 未加载
karmakaze大约 1 年前
I for one really enjoy Hackdays. It&#x27;s a chance to do something not in your normal line of work and experiment in a different area, or with different people, sometimes even different places (but often remote pairing).<p>A couple of hackday projects were proof-of-concepts that eventually made it to prod, in a very organic way. Other teams would learn what was done and adapt it for their needs. They do sort of play out like R&amp;D playtime. I was <i>so</i> lucky to have started my career at companies that actually did software <i>Research</i> as well as Development.
drekipus大约 1 年前
We use hack days (or we call it &quot;spa days&quot; - as in, giving the codebase&#x2F;product a spa treatment) as a day to fix things up, tidy things that have been bugging you for a while but no one ever got around to doing it, etc.<p>Often it&#x27;ll be a case of &quot;hey this table is actually searchable now&quot; or &quot;that page is now split into two&quot; or &quot;I removed a tonne of deprecated code&quot;<p>It&#x27;s actually really enjoyable in my company, we all like it. My only issue is that I rely on structure, and given &quot;free-reigns&quot; I tend to pick too big of a thing that I can&#x27;t get done in a day or two, and I end up doing too much = nothing at all.<p>I usually use it as a &quot;level up&quot; day (which we also have, so I get 2) which is just a day to go learn something new and level up your skills as a developer.<p>I think the issue isn&#x27;t so much the &quot;hack day&quot; but rather your company is trying to get more golden eggs out of it, rather than looking after the goose.
评论 #39452584 未加载
elintknower大约 1 年前
Yeah, when I&#x27;m at work my rule is I need to be getting paid. For those who don&#x27;t understand this is why some loathe company &quot;offsites&quot; and &#x2F; or &quot;hackathons&quot; at any kind of event where I&#x27;m sent by my employer.<p>I thought hackathons were dumb in college (most people just cheat and bring pre-baked projects) and it&#x27;s still dumb after that.<p>If you want to get out of it, just send an email explaining your health and productivity is implicitly tied to your sleep. Worst case just do what I did and get a doctor&#x27;s note that staying up too late for non-work essential tasks is damaging to your physical well-being.
评论 #39449632 未加载
评论 #39453148 未加载
评论 #39452311 未加载
jjice大约 1 年前
I always liked them. We had less work allocated to us on the sprint of a hack day to account for it, so that wasn&#x27;t an issue (and it never should, that sounds like poor planning by a higher up). We also didn&#x27;t force results. If you had nothing of value at the end of a hackday, which is pretty common, who cares - it was a hack day. Some people didn&#x27;t do anything, which was completely fine. The majority of people had a personal vendetta against something in the codebase that they wanted to personally improve or add to, and that&#x27;s where the results came from.<p>The best speed&#x2F;quality ration of features came from hackdays for us because we actually cared about what we were implementing.
skp1995大约 1 年前
I have a love&#x2F;hate relationship with &quot;hack days&quot;. Back when I was an intern I had a lot of fun during hack days. Getting to see a new part of the codebase and getting to interact with new teams is always fun.<p>When I was working full time, my idea of &quot;hack days&quot; changed quite a bit. I took it as time to work on the weird idea in the back of my mind. My demo&#x27;s were not impressive by any means but I learnt quite a bit out of it. I also think its part of the team dynamics, some teams embrace hack days while others do not. Think if the tech lead of a team actively encourages hack days the vibes would be completely different say compared to just doing your day job and planned activities.
sounds231大约 1 年前
Hate them so much. As an iOS eng I feel like I always end up doing 10x more work than others. But it’s also my fault for accepting invites to teams with new feature ideas. Been burned enough times now that I won’t be doing that anymore.
infotainment大约 1 年前
I love them, because they give me an excuse to work on silly joke projects. Usually if you make something amusing enough you can win some award for &quot;people&#x27;s choice&quot; or whatever.<p>At my old company, people would often go and work on projects that were somehow meaningful to the business. It&#x27;s no wonder people like that didn&#x27;t enjoy it. Go work on a VR first person shooter game based on your company&#x27;s mascot; that&#x27;s what&#x27;s gonna get the votes!
评论 #39451931 未加载
catchnear4321大约 1 年前
you haven’t lived until you have watched hackday output, ostensibly made for the lulz, rushed to prod, because customers would love that.<p>if you include the hackday as a day that counts towards velocity, then you will fall behind. because that’s hackday. if your scrum master is doing this, call them out on the dishonesty. make it their problem. let them complain about the velocity hit, and you have some hacky fun.<p>ultimately you have to make the call - are you too fed up to collect that paycheck? or are you comfortable leaning into the insanity for a buck?
评论 #39451943 未加载
elpalek大约 1 年前
In my previous position, management employed the concept of a &#x27;hackathon competition&#x27; as a sales pitch to the judges. One team, having received advance instruction, constructed their work in progress as a hackathon demo in advance and ultimately &quot;won&quot;. It pissed so many people once it was known.
082349872349872大约 1 年前
I always thought &quot;hack days&quot; were a way to officially introduce slack at the end of a scheduling period — not valuable so much for the hack day projects themselves, but as a buffer in case non hack day projects need a final push?
paulcole大约 1 年前
This question is a good example of how companies make decisions to reach their goals, <i>not</i> to make individual employees happy. If your employer could reach their goals but make you miserable, they’d take that trade off in a heartbeat.<p>If you hate hack days that much, interview and find someplace to work that doesn’t do them. Or help your company “just fix” their normal planning process. Or take PTO on hack days.<p>You’ve got plenty of options. The idea that the company has to change to make you happy is the wrong way of looking at it.
roarcher大约 1 年前
I worked at a company that had these and was initially excited about it, but my experience ended up matching yours. The &quot;real&quot; work is planned as if these days don&#x27;t exist, so I spent all of them on my regular duties so I wouldn&#x27;t slip deadlines. One day a week was never enough to make significant progress on anything interesting anyway.
JohnFen大约 1 年前
I&#x27;ve never experienced these &quot;hack days&quot;, and it sounds like I&#x27;m glad for that! Employer-mandated &quot;fun events&quot; are pet peeves of mine in general.
swman大约 1 年前
Companies that do this kind of stuff are really either late stage where everyone is just cruising and vesting, or it’s on the way down.
anemoiac大约 1 年前
Yeah, definitely not a great experience for anyone on a team that already doesn&#x27;t have enough time to do their actual work...
kypro大约 1 年前
I&#x27;ve developed the somewhat controversial opinion that anything that can be conceived and built in a day is almost never worth doing. What I&#x27;ve seen work better is companies setting aside some team resource (maybe 10%) for innovation projects.<p>Specifically instead of running hackathons just give a team a very open ended business problem and ask them to investigate how they can use tech to improve or solve the problem. Give the team a month for an initial investigation and if they come up with something interesting provide them time to develop a POC.<p>Hackathons in my experience just end up with people rushing into mostly useless POCs because they neither have adequate time to investigate a problem or the time to actually build something interesting. You&#x27;ll generally just get devs building things that already exist with whatever the new hot tech stack is at the time.<p>I&#x27;ll also add that corporates generally do these things because a management consultant like McKinsey told them it&#x27;s a good idea. It&#x27;s the same reason why agile is so poorly implemented in corporations because they have no real care or understanding of it, they&#x27;re just implementing the guidance given to them to the letter.
评论 #39470485 未加载
koliber大约 1 年前
Imagine you are in a new city for the first time. You have an old-school printed map in hand. You&#x27;re trying to find your way to some landmark.<p>You can sit down and plan out a route along the map. That will work. You&#x27;ll find a way to get there. It will feel safe and controlled.<p>You can also wander, drop into an alley, and potentially find a shortcut through a park. That path was not on your map, so you would not have found it had you followed your map. Along the way, you might discover something that will make your trip memorable and unique.<p>Many companies follow a planned approach to feature development. The draw up a map, and then follow it. A hack day allows people to wander around the idea space and solution space unencumbered. Sometimes, a hack day brings forward a shortcut, a novel idea, or shows off a piece of functionality which would not see the light of day with the traditional approach. Often, it&#x27;s a matter of catching someone&#x27;s attention by showing them a good idea™ in action. Companies are sometimes in a rut, and a hack day creates a chance for new things to surface.<p>Are hack days fun? For some people, sure. For others, no. Do they serve a business purpose? Absolutely. It isn&#x27;t all fun and games, even if it feels like it.<p>I have personally seen &quot;hack days&quot; accelerate concrete and valuable functionality.
whoopsie大约 1 年前
Are you R&amp;D or just D?
评论 #39450029 未加载