[SketchySeaBeast]

Don't worry, it's not robbing you of the the evenings and weekends, which "maybe you like", it's a fun new challenging opportunity. Have you had a chance to panic yet on Saturday morning at 3 AM? Would you like to? It's such a thrill.

[babyshake]

See also: exciting hackathons where you get to work late nights and weekends on "fun ideas" that the leadership would like implemented ASAP.

[dvtrn]

What's been everyone's experiences/takes/opinions, specifically with not doing Hackathons? My org is moving them to quarterly-we used to have one yearly-I skipped the last one, probably going to skip the next one but I wonder how long that's going to last before someone in management sticks a head up and asks why I'm not participating (a question for which I have an answer ready to go)

(edit: and by "hackathon" because I realize there's a bit of room for ambiguity, I mean internal corporate Hackathons where the company "allows" dev teams to take a "break" from "regular" work in order to ideate and build new features and functionality that--if their idea gets chosen--becomes "regular" work in and of itself. It's those kinds of hackathons I've started removing myself from)

[HowTheStoryEnds]

It's not a hackathon if my idea needs to be chosen and ordained by Papal seal. I already have that, it's called work.

[dvtrn]

Testify.

[andrewf]

I'd just pick something from the backlog that I don't think is prioritized highly enough, and do that.