Lightnews — Scholar-powered news

Vaughn Vernon @vaughnvernon.bsky.social · 1d

"8 SaaS Niches Printing $20K-Plus a Month — And Nobody’s Built Them Yet"

You can't make this stuff up unless you wrote the post, in which case you did make this stuff up.

1

Vaughn Vernon @vaughnvernon.bsky.social · 2d

Well, I do whatever the team does. I don't refuse to use Scrum out of loathing. Even in the worst experiences, it's been survivable. Unpleasant, yes, but I can take a deep breath enough to keep going. There have been a few reasonable environments, mostly dominated with communication by Jira 😂

1

Vaughn Vernon @vaughnvernon.bsky.social · 2d

The problem is that nobody will be able to recapture the term for its proper use. So, if I say "Technical Debt," everybody thinks "Bad Code." If I say "Model Debt," people say, "What?" and have to listen (or at least hear).

1

Vaughn Vernon @vaughnvernon.bsky.social · 2d

or even "Knowledge Debt" because that distinguishes it from what is most often labeled "Technical Debt," which is just about anything for which you took shortcuts.

It's a matter of practicing agility, not totalitarian control that suffocates the team. 5/5

1 3

Vaughn Vernon @vaughnvernon.bsky.social · 2d

an inferior model (some feature/functionality) is recognized as lacking in knowledge that was only possible to gain by doing, what gets moved to a later Sprint is the well-defined Technical Debt as it is currently understood. I prefer to refer to Technical Debt as "Model Debt"... 4/5

1 1

Vaughn Vernon @vaughnvernon.bsky.social · 2d

That doesn't issue a license to be lazy or careless about business goals. It acknowledges that some work is impossible to complete well in a given timebox.

If "Technical Debt" is used in the way it was initially defined, ... 3/5

1 1

Vaughn Vernon @vaughnvernon.bsky.social · 2d

What I think is useful is that the timebox marks a goal for an increment having value worth releasing.

You don't necessarily need to meet all aspects of the goal. Some work items might of necessity be moved to a later Sprint. 2/5

1 2

Vaughn Vernon @vaughnvernon.bsky.social · 2d

Aren't Sprints bad?

Maybe. I think that defining a Sprint as a single iteration is silly. It makes an iteration very mechanical, as if there's no progress made until the timebox officially ends.

In reality, even in a single-week Sprint timebox, there are likely several iterations. 1/5

Vaughn Vernon @vaughnvernon.bsky.social · 2d

There is no single part of Scrum that is bad. It's the inseparableness of and strict adherence to all the parts of Scrum that is bad. By definition, you can't separate any parts of Scrum, as in use a subset of Scrum linked with common sense, and still call it Scrum. 1/6

Figure: Not complex enough.

Figure: Not nearly complex enough to sufficiently represent Scrum.

1 3

Vaughn Vernon @vaughnvernon.bsky.social · 2d

informed I needed to accomplish the previous day, and disappointment was expressed by the "Scrum Master" who didn't have a clue about agility or software development in general, having previously deployed Lotus Notes utilities very liberally known as "applications."

Now scale that. Enough said. 6/6

3

Vaughn Vernon @vaughnvernon.bsky.social · 2d

experience with Scrum after 20 years of software practice that was already quite agile (when I had a say).

I recognized the weaponization of Scrum the morning of the second day that I ever experienced Scrum. It was when I had to *report* that I wasn't able to accomplish to five things I was... 5/6

1 1

Vaughn Vernon @vaughnvernon.bsky.social · 2d

and you're expected to state things as a predefined bullet list, and your "master" tells you to be more enthusiastic when you speak. You are in a totalitarian state, not an agile software development practice.

That, my friends, is bad, and I've lived it with multiple teams from my first... 4/6

1 1

Vaughn Vernon @vaughnvernon.bsky.social · 2d

dares to say "stand-up" as a noun, that we're failing? Yeah, that's just as totalitarian and suffocating as the other extreme, and it doesn't reflect an agile mindset.

Stand-ups are lame and suffocating when they occur at precisely the same time every day and have an exact format and agenda... 3/6

1 1

Vaughn Vernon @vaughnvernon.bsky.social · 2d

Not being able to call it Scrum doesn't phase me in the least, but the very notion that you can't is totalitarian and suffocating.

Thus, stand-ups are not wrong or bad. Like, are you trying to tell me that if we huddle for five minutes to shore up some work to be done, and someone even... 2/6

1 1

Vaughn Vernon @vaughnvernon.bsky.social · 2d

There is no single part of Scrum that is bad. It's the inseparableness of and strict adherence to all the parts of Scrum that is bad. By definition, you can't separate any parts of Scrum, as in use a subset of Scrum linked with common sense, and still call it Scrum. 1/6

Figure: Not complex enough.

2 1 2

Vaughn Vernon @vaughnvernon.bsky.social · 3d

I'd like to make something perfectly clear. This kid covers Tool's full discography in a single take—7.5 hours, nonstop.

Thank you. That'll be all.

youtu.be/0kO0SnAu8Nc

TOOL's Discography in One Take (Drum Cover) - Tyler Visser

YouTube video by Tyler Visser

youtu.be

1 2

Vaughn Vernon @vaughnvernon.bsky.social · 7d

Being LLMs that run on GPUs that can't perform associative math, there's no reason to expect a given prediction. We want consistency, but the LLM platforms are inconsistency machines by design.

1

Vaughn Vernon @vaughnvernon.bsky.social · 7d

Unfortunately, many still make a snap judgment based on the words Monoliths and Microservices. 4/4

Vaughn Vernon @vaughnvernon.bsky.social · 7d

We were hoping that leading with both of these words would frame the more important point of using DDD strategic design and enabling architecture decisions to reveal themselves as purpose is understood by stepwise refinement. 3/4

1 1 1

Vaughn Vernon @vaughnvernon.bsky.social · 7d

We provide a slew of reasoned principles and guidance on making sound architectural decisions while focusing on the actual two most important words in the main title and subtitle: "Strategic ... Innovation." 2/4

1 1 2

Vaughn Vernon @vaughnvernon.bsky.social · 7d

Our book "Strategic Monoliths and Microservices" doesn't categorically (as an absolute) recommend modular monoliths. The key is in the subtitle: "Driving Innovation Using Purposeful Architecture." 1/4

Book: Strategic Monoliths and Microservices—Driving Innovation Using Purposeful Architecture #DDD #DDDesign #domaindrivendesign #eventdrivenarchitecture

1 5

Vaughn Vernon @vaughnvernon.bsky.social · 7d

OH: YAGNI is contextual.

Everything is contextual. One of the very worst software issues globally is people not understanding that.

1 1 3

Vaughn Vernon @vaughnvernon.bsky.social · 7d

Is that "appy yak" which is sort of like "happy yak (shaving)" only different?

Hans L’Hoest @hanlho.com · 8d

Instead adopt APYIAC : avoid painting yourself in a corner. That’s what I used to throw in the mix whenever someone brings up yagni in the wrong context.

2 1 2

Vaughn Vernon @vaughnvernon.bsky.social · 8d

YAGNI is too often a plague infecting otherwise good software design. It's a knee-jerk reaction to "I don't have a clue, so I'll ensure that I don't need to have a clue."

2 4 14

Vaughn Vernon @vaughnvernon.bsky.social · 14d

Harbor water sounds appropriate. Thanks!

Vaughn Vernon @vaughnvernon.bsky.social · 14d

I have felt before like I'm in a fish bowl. Now I'll actually be in a fish bowl. 🐟 🐟 🐟 🐟

Question: Which Berlin bier 🍺 pairs best with fish food?

1 1