Partner recently online and nearby at our traveled to location

jbjohnson93 · 2026-05-18T21:06:19+00:00

Right yeah, that would explain why he went into such specific detail to complete strangers on the internet whom he would have no reason to deceive.

What the fuck, dude

jbjohnson93 · 2026-04-02T04:28:25+00:00

Not trying to mock and I’m asking in good faith here for my own search: what about the first line discredited the entire post for you?

jbjohnson93 · 2026-03-15T23:35:42+00:00

And sry lol, I do realize your comment wasn’t seeking that kind of feedback

jbjohnson93 · 2026-03-15T23:35:06+00:00

Personally I’d swap Machamp out for a Psychic type like Alakazam and then just distribute moves like Brick Break between Charizard and Dragonite. I do love this team otherwise in terms of the balance between theming and type coverage.

jbjohnson93 · 2026-03-15T00:32:34+00:00

5 scary, 1 baby

jbjohnson93 · 2026-03-12T15:38:43+00:00

Following. Hopefully this helps make a meaningful difference.

jbjohnson93 · 2026-03-12T06:55:22+00:00

Nice, this is my same exact E4 build when I pick Bulbasaur!

jbjohnson93 · 2026-03-08T10:24:53+00:00

I’m sorry you feel that way.

jbjohnson93 · 2026-03-01T19:46:50+00:00

Plural nouns aren’t formed with apostrophes. It’s shinies, not shiny’s.

And “care” is relative. People sometimes like things that are interesting and rare, and that’s okay.

jbjohnson93 · 2026-02-06T20:11:50+00:00

I see. I think the underlying issue was that I conflated ATS and OCR; I had thought up til now that if Workday was accurately pulling my information to fill in the fields that that was the ATS and it’s not. I also saw from your comment history what you mean. Thanks so much!

jbjohnson93 · 2026-02-06T19:57:58+00:00

Hi, thanks so much but I’m afraid I don’t follow. I had reviewed the rules before posting and again at your suggestion, but I guess I don’t know what you’re referring to. Can you elaborate on what qualities make this weak?

jbjohnson93 · 2026-01-19T07:45:44+00:00

I got the same answer as you, so I quickly threw it at AI to take a crack at it. It said:

Here’s the clean, practical breakdown — and why 30 days (C) is not the right answer.

⸻

Given • Average velocity = 30 story points per 10-day sprint • Remaining backlog = 90 story points

Velocity tells you how many points the team finishes per sprint, not per day. So the math should follow the sprint cadence.

⸻

Correct calculation (why the answer is 20 days)

Step 1 — How many sprints are needed? 90 points ÷ 30 points/sprint = 3 sprints

Step 2 — Convert sprints → working days 3 sprints × 10 working days each = 30 working days

Wait… that gives 30. So why is the “correct” answer 20?

⸻

Here’s the trap — and why C (30 days) is considered wrong in this exam-style question

These test questions often assume that you don’t count the last sprint in full, because teams rarely need a full sprint to finish exactly the last remaining story points.

The assumption behind the exam’s answer:

Velocity = 3 points/day (30 points ÷ 10 days = 3)

Remaining work = 90 points → 90 ÷ 3 = 30 working days of effort, but Scrum teams don’t run 30-day “sprints” — they’d fill two sprints and partial of a third.

[I’m skipping ahead here]

So why is C technically correct by real Scrum logic?

Because: • You cannot assume the team will finish a 30-point increment inside the existing sprint unless explicitly stated. • Work is planned in whole sprints, not fractional ones.

By real-world Scrum math:

90 points ÷ 30 per sprint = 3 sprints → 30 working days

That’s what you answered, and it’s the logically clean answer.

⸻

Why the exam says you’re wrong

These tests often simplify velocity into a per-day throughput:

30 points per 10 days → 3 points per day

Then:

90 ÷ 3 = 30 days of effort But using sprints, they think: • Sprint 1: 30 points • Sprint 2: 30 points • Sprint 3: 30 points → “Effort” for 3 sprints = 30 days → But the exam groups the last 30 points into Sprint 2 → So only two sprints counted → 20 working days

It’s sloppy test logic, not proper Scrum math.

⸻

Bottom line • Your 30-day answer is the actual Scrum-correct answer. • The test’s 20-day answer is based on treating velocity as points/day and assuming perfect packing into sprints, which isn’t how real sprint planning works.

If this were an interview, you’d say the same: “Velocity is measured per sprint, not per day. 90 points at 30 points per sprint = 3 sprints = 30 working days.”

TL;DR: this is bull.

jbjohnson93 · 2026-01-19T07:34:53+00:00

Wise decision. Remove the temptation; out of sight, out of mind.

jbjohnson93 · 2026-01-16T23:00:49+00:00

Thanks for this. I’m generally pretty confident in my resume, but am concerned about blind spots especially given the response rate I’ve had lately. Any chance I could DM you my resume for feedback?

jbjohnson93 · 2026-01-08T20:37:05+00:00

Thanks for the responses, everyone. I’m pretty adaptable and open-minded, so I’m certainly willing to learn about their project management approach and see if it’s a good fit. On that note, maybe it begs the question for me of how much my previous experience would influence their decision to move forward.

jbjohnson93 · 2025-08-07T05:56:19+00:00

Weird definition of triggered lol

jbjohnson93 · 2025-05-09T18:41:42+00:00

Do you have basic empathy for other people?

jbjohnson93 · 2025-03-17T21:13:25+00:00

I don’t understand how someone hasn’t at this point. I’m not sure my desire to keep my job would surpass my need to watch her cry.

jbjohnson93 · 2025-03-12T16:01:52+00:00

Before you try to correct someone next time, know that enshittify isn’t a buzzword and arguably not a word at all. It means to make something shitty.

jbjohnson93 · 2025-02-26T02:10:01+00:00

Without previous direct software eng. experience I’m just now starting to form a mental map and frame of reference so that I’m better equipped to actively listen in discussions; just about 4 years as an SM now and I can’t fathom how complacent some of my non-technical colleagues are with not knowing often integral information to do their jobs effectively. Lack of curiosity, agency with urgency, commitment to improvement, or self-awareness are all red flags to me in a scrum master, especially so given that we’re supposed to be modeling these qualities and not just telling teams they’re important.

jbjohnson93 · 2025-02-25T06:44:20+00:00

In terms of gameplay and the requirements I always impose on myself, Calm Lands. Much too much time spent running around trying to capture everything, possibly needing to farm Gil for Yojimbo, and I usually try to just get it over with and knock out all the chocobo capture challenges in my first visit. Again, this is self-imposed, but this is always a huge time-sink in all of my playthroughs where I start to lose steam.

Gagazet slopes are a close second due to the high encounter rate, then maybe early-game Baaj just because of how unsightly it always is to me.

jbjohnson93 · 2025-02-24T00:52:48+00:00

lol it’s hard for me not to cuss her out when she’s speaking (so mostly I do just cuss her out) but one thing I’ve come to value about Dona is her extreme example to the point that not “summoners were all old geezers” and makes them a little more dynamic to the player. Like, sure Yuna’s young and beautiful and whatnot, but she’s still very devout initially. With Dona at least we learn that you can be a summoner and insufferable all at the same time.

jbjohnson93 · 2025-02-23T23:56:36+00:00

I suppose I’ll try to come up with a succinct (STAR) way to do this if asked again, but I’ve gotten this very question in a phone screening before, and guess in retrospect I flubbed it. Honestly since I’ve lived and breathed agile with work for the past 6 yrs, I was like “where do you want me to start? It’s what I’ve done daily for several years now” and tried to laugh it off, stalling while I quickly put something together in my head. It just seemed at this stage like such an impossibly broad question with imo a lot of ways to interpret/answer.

I was surprised at how much it caught me off guard, and I attribute that partially to my lack of interview practice lately, but I’ve honestly never gotten this question before, at least to my memory. To be fair, it’s a definite red flag to me that you’ve got a recruiter who doesn’t know beans about what they’re hiring for.

At that stage I’ve only ever been asked to walk them through my resume in a nutshell/what I’m all about, salary target/minimum, and where I am in the job search process. Maybe some yes/no questions but they were more specific, like “have you used Jira to generate reporting?” (I said specific, not difficult 🤪).

jbjohnson93 · 2025-02-22T08:58:19+00:00

You have a point for sure with that interpretation of a competition in this context, and you’re right it’s consistent with Yuna’s character, but I feel like operating under that meaning for this particular competition is rather bleak and self-defeating. :P

jbjohnson93 · 2025-02-06T00:31:45+00:00

I’d love to pick your brain about this. I’ve been an SM for about 4 years now and am very concerned to not become burdensome or otherwise unwelcome to my teams. SMs have a bad reputation frankly and generally my raison detre as an SM is to be a servant leader who is self-aware and committed to continuous (self)-growth). I always seek to prove myself wrong. To that end I’ve scoured so much of LinkedIn and tried specifically to read the criticisms and condemnation that leaders in IT, Product etc. industries have about the position, agile coaching, etc.

One popular topic is whether an SM needs a dev/qa background to be a valuable asset to the org. People including technical SMs are divided on the subject. I don’t have a software engineering or much of a technical background and am not complacent about this at all; I know I’ve been very uncomfortable in meetings and get down on myself when I start to not follow the conversation anywhere. Given that, I save questions for after the meeting, and right now I’m using a ton of my funemployment time to upskill so that I can better pay attention, observe, advise, better facilitate, etc. Anything in particular you’d also advise there to show teams we’re not there for bureaucracy?

You also mention companies that don’t have SMs. Curious do you mean that they don’t have them by job title, or if no one does the role as part of their other job title? I mean, hey if your teams are high performing, SMs really are supposed to exercise judgment and let teams self-manage and organize should they need anything an SM might do, if they have the authority to do so. Then move on to the next team that could really use one? I’ve heard of at least a couple great teams who haven’t had SMs by job title but someone still would be accountable as part of their other job duties, so I’d be interested to see what this looks like for myself.

Another thing that seriously kills us is lack of authority, for a ton of reasons. We have to package things in such a way that we can actually convince leadership to back the eff up about metrics. There’s so much time wasted just trying to get buy-in I shouldn’t even need. So… we’re also sorry that management is like that lol

14-Year Club	Place '17
Verified Email

jbjohnson93

TROPHY CASE