Depending on the size of the team/org/company, working on anything other than the next feature is a hard sell to PM/PO/PgM/management.

▲

NegativeK 13 hours ago | parent | next [-]

I've had to inform leadership that stability is a feature, just like anything else, and that you can't just expect it to happen without giving it time.

One leader kind of listened. Sort of. I'm pretty sure I was lucky.

▲

deaux 7 hours ago | parent | next [-]

Ask them if they're into pro sports. If so (and most men outside of tech are in some way), they'll probably know the phrase "availability is the best ability".

	▲	Herring 17 minutes ago \| parent [-]
		Or just look at your car. Heated seats are sexy in the short term, but boring old reliability and predictability is better long term.

▲

dijksterhuis 3 hours ago | parent | prev [-]

i got lucky at my last shop. b2b place for like 2x other customer companies. eng manager person (who was also like 3x other managers :/ ) let everything get super broken and unstable.

when i took lead of eng it was quite an easy path to making it clear stability was critical. slow everything down and actually do QA. customer became super happy because basically 3x releases went out with minimal bugs/tweaks required. “users don’t want broken changes immediately, they want working changes every so often” was my spiel etc etc.

unfortunately it was impossible to convince people about that until they screwed it all up. i still struggle to let things “get bad so they can get good”, but am aware of the lesson today at least.

tl;dr sometimes you gotta let people break things so badly that they become open to another way

▲

machomaster an hour ago | parent [-]

It's interesting how misaligned your effort is.

You put effort into writing an unnecessary tldr on a short post, but couldn't be bothered to properly Capitalize your sentences in order to ensure the readability.

Weird.

	▲	nsingh2 40 minutes ago \| parent [-]
		> Be kind. Don't be snarky. Edit out swipes [1] [1] https://news.ycombinator.com/newsguidelines.html

▲

BurningFrog 14 hours ago | parent | prev [-]

That's what I hear.

I've had some mix of luck and skill in finding these jobs. Working with people you've worked with before helps with knowing what you're in for.

I also don't really ask anyone, I just fix any bugs I find. That may not work in all organizations :)

	▲	ramon156 8 hours ago \| parent \| next [-]
		I can guarantee you this doesn't work in our team! you didn't make a ticket, so the PM has no idea what you're doing! Yes, a ticket takes 2 seconds. it also puts me off my focus :P but i guess measuring is more important than achieving
	▲	zelphirkalt 9 hours ago \| parent \| prev [-]
		micro-managing middle manager: "Are all your other sprint tasks finished?" code reviewing coworker: "This shouldn't be done on this branch!" (OK, at least this is easy to fix by doing it on a separate branch.)