Pavel

frankly it is unfair for anyone to hold being weird and off-putting against me

We ran out of posts from your follows. Here is the latest from Discover.

This place is not a place of honor...no highly esteemed deed is commemorated here...nothing valued is here. What is here is dangerous and repulsive to us.

You load 16 server racks, what do you get?
Another day older and deeper in debt
St Peter, don't @ me 'cause I can't go
I owe my soul to the company store

Ehhh, the content is what drives the form, so lorem ipsum tends to produce pointless artifacts just like AI

It is faster not to.

Process friction is my #1 jam

cover your own ass; the impetus behind Agile came from the goalie problem of waterfall development: when something goes wrong, the immediate cause gets the blame. The goalie is blamed for the other team scoring; engineers get blamed for missing deadlines.

Hence, no need for problem framing.

If they are going to do that then they might as well just write out the scenario and not have visuals. Part of the learning comes from the making; thinking about what needs to be drawn.

The other good reason not to do it is that the AI generated cartoons all look the same and make me want to vomit.

When my synapses are congested, nothing clears them out like some vindaloo

the purpose of a pilsner is what it does

cracking open a stafford beer with the boys

Integrating bullshit engines/ Like-My-Outputs next token preditors into any environment related to maintaining the access to and security of data was basically only ever going to be a mistake

(Original image reposted with alt text)

There's an ecosystem that of glommed onto Agile incorporating Lean and Scrum things to various extents, but they fail precisely because the roots of Agile are a COYA maneuver for low trust environments.

"Give me requirements in small doses, and I will ship them" is how Agile wants teams to work.

There is no user story grooming in the Agile manifesto.

I am very comfortable saying that if someone doesn't know how to run critique, they are not a good UX designer.

cache me outside girl

This is another good point that bears repeating; go read the Agile Manifesto and behold the absolute lack of problem framing.

The developers wait for "customers" to give them "requirements" that can change unpredictably, without wondering why customer needs (which are usually STABLE) change.

this is a very good thread. the point of rough drafts is that by creating them, you *learn about the nature of the problem you are trying to solve* and your new understanding shapes your strategy

Influencers are promoting peptides for better health. What does the science say? The latest wellness craze involves injecting these molecules for athletic performance, longevity and more. Scientists say the research isn't keeping pace with the health claims.

I don't understand how we have to beg people to get vaccinated while other people are fine shooting themselves up with untested compounds for unproven "gains" risking god knows what

you were finally going to read them! any minute!

i'm in ur base closing ur tabs

Cards that look like old VHS covers

Basic Land but make it actually nostalgic

Made by Ron Lecher

soup is stored in the nuts

I thought this was going to be related to the "infinite porridge" fable lol

YES! Just because vibe coding gives you a fully-greebled model without you having to learn, ever, doesn't mean you have good code; it means you have instant complexity that makes testing harder and will break worse, even if it is ostensibly functional. Functional has never been the hard part.

Usually the stuff I post on here is a coarse run-through for refining down the line, so I'd love to hear what doesn't land!

Yes, often it just hides that there's no "there" there

Debbie Levitt on UXR:

"If ChatGPT tells you that millennials want more sustainability from eCommerce websites, do we know what to do? Do we know how these people define sustainability and how our target audiences expect us to execute on that?"

Output-driven teams look at velocity improvements and think "faster = smaller timeboxes!" but what that actually enables is more feedback loops within the timebox, which is what actually drives quality.

I have written piles of essays on why this "build to learn" approach is incredibly wasteful:
- it locks you in to local optimization
- it burns trust
- it can still only function at a human pace
- "fix the problems" relies on a problem-finding feedback loop no one sets up
- there is never a v2

Without the synthesis process of critique, everyone who vibe coded a thing now has their own mental model, which means they are no longer actually a team.

This kills the project.

When you treat low fidelity artifacts (regardless of the amount of detail) as disposable sketches, this doesn't happen.