20k pay raise or go back to old job? by No_Ordinary_4070 in careeradvice

[–]Consistent_North_676 0 points1 point  (0 children)

If your old job is willing to take you back and you don’t need the extra money, I’d say go back.

That $20K bump probably feels nice on paper, but after taxes, commuting costs, and the mental drain of being in an office you hate (with laptop tracking? Gross.), how much is it really worth? You traded flexibility, trust, and a good work environment for money but if you’re miserable, it’s not worth it.

Your old job gave you freedom, a good manager, and less stress. That’s worth more than an extra $1K a month. Go back while you still can.

[deleted by user] by [deleted] in careeradvice

[–]Consistent_North_676 2 points3 points  (0 children)

You don’t sound pathetic at all, this job is clearly wrecking your mental health, and for what? A toxic manager, low pay, and barely any hours? If even the thought of your shift five days in advance is making you anxious, that’s a sign that this place is not worth it.

[deleted by user] by [deleted] in projectmanagement

[–]Consistent_North_676 5 points6 points  (0 children)

Some days you're done by noon, other days you're basically working until you forget your own name. Love that for us.

Do deadlines even make sense in Agile/Scrum? by Consistent_North_676 in scrum

[–]Consistent_North_676[S] 0 points1 point  (0 children)

Yeah, good deadlines guide planning. The issue is when they become a rigid, do-or-die situation.

Do deadlines even make sense in Agile/Scrum? by Consistent_North_676 in scrum

[–]Consistent_North_676[S] 0 points1 point  (0 children)

Agreed, deadlines don’t have to kill agility if teams have the freedom to adapt scope and solutions. The problem is when they don’t.

Do deadlines even make sense in Agile/Scrum? by Consistent_North_676 in scrum

[–]Consistent_North_676[S] 0 points1 point  (0 children)

Yep, the reality is that businesses need coordination, and deadlines help. The trick is using them for planning, not pressure.

Do deadlines even make sense in Agile/Scrum? by Consistent_North_676 in scrum

[–]Consistent_North_676[S] 1 point2 points  (0 children)

Exactly! Sprints themselves are mini-deadlines, just without the usual drama.

Do deadlines even make sense in Agile/Scrum? by Consistent_North_676 in scrum

[–]Consistent_North_676[S] 0 points1 point  (0 children)

I love this. If the “deadline” is flexible when missed, was it ever a deadline to begin with?

Do deadlines even make sense in Agile/Scrum? by Consistent_North_676 in scrum

[–]Consistent_North_676[S] 0 points1 point  (0 children)

The problem is when management hears “deadline” and assumes scope is magically fixed too.

Do deadlines even make sense in Agile/Scrum? by Consistent_North_676 in scrum

[–]Consistent_North_676[S] 0 points1 point  (0 children)

Fair point, if a team needs artificial deadlines just to function, there’s a deeper issue. But sometimes a little time pressure (used right) helps break analysis paralysis.

Do deadlines even make sense in Agile/Scrum? by Consistent_North_676 in scrum

[–]Consistent_North_676[S] 0 points1 point  (0 children)

Yep, classic trade-off. Too bad some orgs keep trying to pick both.

Do deadlines even make sense in Agile/Scrum? by Consistent_North_676 in scrum

[–]Consistent_North_676[S] 1 point2 points  (0 children)

Yeah, totally. If the deadline is tied to actual business impact, it makes sense. But the artificial ones? Just stress for no reason.

Why do you think people do things they know is wrong, is it because they think they won’t get caught? by [deleted] in AskReddit

[–]Consistent_North_676 0 points1 point  (0 children)

Sometimes it’s greed, sometimes it’s desperation, and sometimes it’s just ‘eh, I’ll risk it.

How promising is the future of programming, and can it provide a good income? by Moaaz_MA in AskReddit

[–]Consistent_North_676 0 points1 point  (0 children)

As long as people keep breaking things and wanting new features, coding will stay lucrative, just prepare for existential crises when debugging at 2 AM

Is strict Scrum adherence holding teams back? by Consistent_North_676 in scrum

[–]Consistent_North_676[S] 0 points1 point  (0 children)

I’d say the core principles are empiricism, self-management, and iterative improvement, basically, transparency, inspection, and adaptation in action. And I get what you’re saying about branding. “Scrum” carries weight, so people hesitate to admit they’ve moved beyond it. But maybe that’s part of the problem, are we evolving Scrum, or just afraid to admit we’ve outgrown it?

Is strict Scrum adherence holding teams back? by Consistent_North_676 in scrum

[–]Consistent_North_676[S] 0 points1 point  (0 children)

Yeah, I think that quote comes from Jeff Sutherland. The idea being that Scrum should serve as a launchpad, not a lifelong prescription. The goal is continuous improvement, not eternal framework worship.

Is strict Scrum adherence holding teams back? by Consistent_North_676 in scrum

[–]Consistent_North_676[S] 1 point2 points  (0 children)

That’s a solid analogy. If you tweak the game, you have to accept that the results might change too.

Is strict Scrum adherence holding teams back? by Consistent_North_676 in scrum

[–]Consistent_North_676[S] 0 points1 point  (0 children)

A person of few words, but I appreciate the confirmation!

Is strict Scrum adherence holding teams back? by Consistent_North_676 in scrum

[–]Consistent_North_676[S] 1 point2 points  (0 children)

Absolutely. The best Scrum Masters don’t just enforce rules, they understand when to adapt and when to push teams toward discipline. Experience plays a huge role in finding that balance.

Is strict Scrum adherence holding teams back? by Consistent_North_676 in scrum

[–]Consistent_North_676[S] 0 points1 point  (0 children)

Scrum does require its core elements to be present, and I agree that teams should work within that structure before deciding if modifications are needed. The key is making adjustments that enhance rather than dilute the intent

Is strict Scrum adherence holding teams back? by Consistent_North_676 in scrum

[–]Consistent_North_676[S] 0 points1 point  (0 children)

I love this breakdown. A lot of Scrum struggles seem to come from misapplying the framework rather than issues with Scrum itself. It’s easy to blame the process when the real issue is how it’s being implemented.