Post #1761161
2026-04-28 11:26 UTC
Replies (7)
-
@trebach@functional.cafe 2026-04-28 11:32
@AtanasE@mastodon.social If it's not in scope, the product owner and I can figure out if it's something that needs to be fixed now, logged to fix later, or if we're just going to leave as is because it's so rarely encountered
-
@rjhale1971@fosstodon.org 2026-04-28 13:27
@AtanasE@mastodon.social under 40 try to fix it - over 40 pretend i didn't see it.
-
@bakachu@infosec.exchange 2026-04-28 13:32
@AtanasE@mastodon.social all of the above
-
@dr_a@mastodon.social 2026-04-28 13:40
@AtanasE@mastodon.social it really depends on the problem. usually it’s the first option with a hint of the fourth.
-
@sotolf@polymaths.social 2026-04-28 14:10
@AtanasE@mastodon.social I'll do one of them, depending on the problem.
-
@xarvos@outerheaven.club 2026-04-28 14:29
@AtanasE@mastodon.social what’s the difference between 2nd and 3rd options?
-
@bflipp@vmst.io 2026-04-28 16:16
@AtanasE@mastodon.social I always just fix it. Getting support from anyone higher up is a waste of time at nearly every job I’ve ever had and I’m generally rewarded more for just doing things without asking permission first. It’s also the only way nearly anything meaningful gets done as generally whatever roadmap your leadership rolls out in Q1 is either too conservative to provide you with interesting things to do or so aggressive you’re going to lose 40% of your staff by mid-year.