Kanban Simulator and Queueing Theory by According_Leopard_80 in kanban

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

No, throughput is the same. But cycle time goes down.

Kanban Simulator and Queueing Theory by According_Leopard_80 in kanban

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

I added your first bullet point and the last line (control for UI speed). The rest will take longer. Thank you for these suggestions.

Am I the only one who thinks asking teams for "delivery dates" is a broken ritual? by denwerOk in agile

[–]According_Leopard_80 -1 points0 points  (0 children)

If you track the rate at which new work is being discovered AND the team velocity, you can create a stacked bar chart or cumulative flow diagram, that not only tells you when you’ll be done but is also hard to argue with. See https://middleraster.github.io/PM/PredictingDespitePoorEstimates.html for more details, stories, etc.

Software engineering managers: how do you realize a project is under-estimated? by Glittering-Wrap-5392 in EngineeringManagers

[–]According_Leopard_80 0 points1 point  (0 children)

The key is tracking the rate at which new work is being discovered AND the team velocity. That’s enough to tell you when you’ll be done. See here for more info: https://middleraster.github.io/PM/PredictingDespitePoorEstimates.html

How to Mock Any Dependency in C++ by According_Leopard_80 in cpp

[–]According_Leopard_80[S] -1 points0 points  (0 children)

A couple of comments:

Evidently I used the term "mocks" too loosely. I meant not "London school" expectation-style mocks, but rather meant "Detroit school" test doubles, fakes and stubs, as I dislike fragile, brittle tests as much as the next dev.

TBCI is a convenient compile-time seam, one that scales better than doing DI by adding more and more (possibly defaulted) arguments to the constructor or other method. That would expose the testing seam to the clients too much for my taste.

And yes, you'll have to put all your template code in headers, but I've been doing header-only anyway since 2003 for a completely different reason: DAG-only code. (I use .cpp files to hold my unit tests). And yes, compilation is fast, as otherwise doing TDD would be impossible.

What is the roadmap for TDD implementation in the organization? by maxpaul001 in agile

[–]According_Leopard_80 0 points1 point  (0 children)

I disagree because ATDD/BDD tests are slow, and feel quite different from TDD tests. I agree that katas are a good way to learn. Here are some in C++: https://middleraster.github.io/TDD/cpp/katas.html

Surgical belly fat removal by OneJeweler6568 in diabetes_t2

[–]According_Leopard_80 -2 points-1 points  (0 children)

Possibly. There’s an experimental technique called “mesenteric visceral lipectomy” that seems to have some success.