More nonsense buzzword soup de jour. Can I play along at home? How about Vibewatermaxxing? Surely in the new age it should catch on.
This industry is just getting more and more bonkers.
Specsmaxxing – On overcoming AI psychosis, and why I write specs in YAML
81–90 of 316 posts
Re: Specsmaxxing – On overcoming AI psychosis, and why I write specs in YAML
#82What is it with people and procrastinating with the most useless shit you can imagine? First it was choice of editor: people were micro optimizing every aspect of their typing experience, editor wars where people would literally slaughter over suggesting another camp. Editor wars v2: IDEs arrived and second editor war began. Revenge of the note taking apps: Obsidian/Roam/Joplin/Apple Notes/Logseq. Just one plugin, ju…
A lot of people sadly, nowadays don't have anything resembling to a social life and family... So here we are now, specmaxxing and shit :)
Re: Specsmaxxing – On overcoming AI psychosis, and why I write specs in YAML
#83Earlier quoted context omitted.
> will always care what the spec says, and that’s never going to change Did I miss something or is everyone back in 1970s, working in waterfall processes now?
All through the agile era I wrote detailed specs for projects and then followed an agile process. The most successful parts of every project were the ones that we were able to spec best even when they diverged significantly from the original spec. You don't plan to follow the plan. You plan in order to understand the whole problem space. Obviously no plan survives contact with reality.
Agree!
Another point of view is that LLM:s perform to an extent on the same level as outsourcing does. This interface requires a bit more contract mass than doing everything within single team.
Re: Specsmaxxing – On overcoming AI psychosis, and why I write specs in YAML
#84I also have started numbering my Acceptance criteria and pushing that across the team(s). It’s going pretty well. Some note however are
1. Don’t write in yaml. It’s really hard for humans. Write in markdown and use a standard means to convert to lists / yaml.
2. Think beyond you writing your own specs - how does this expand into teams of tens or more. The ticketing system you have (jira? Bugzilla) is not designed for discussion of the acceptance criteria. I think we are heading into a world of waterfall again where we have discussions around the acceptance criteria. This is not a bad thing - is used to be called product management and they would write an upfront spec.
If this new world of a tech and a business user lead the writing of a new spec (like a PEP) and then then AI implements it and it’s put into a UAT harness for larger review and a daily cycle begins, we might have something.
Good luck
Re: Specsmaxxing – On overcoming AI psychosis, and why I write specs in YAML
#85What is it with people and procrastinating with the most useless shit you can imagine? First it was choice of editor: people were micro optimizing every aspect of their typing experience, editor wars where people would literally slaughter over suggesting another camp. Editor wars v2: IDEs arrived and second editor war began. Revenge of the note taking apps: Obsidian/Roam/Joplin/Apple Notes/Logseq. Just one plugin, ju…
It's fun how people brag of their agentmaxxing, but if you ask them what those agents are busy actually producing, it's invariably another agent harness so they can agentmaxx better. NFT/blockchain ecosystem was much the same.
Re: Specsmaxxing – On overcoming AI psychosis, and why I write specs in YAML
#86Author here, if you don't want to read all that, I'll post one excerpt that I think sums it up nicely: > My point is, the spec must live somewhere, even if you don’t write it down. The spec is what you want the software to be. It often exists only in your head or in conversations. You and your team and your business will always care what the spec says, and that’s never going to change. So you’re better off writing it…
> will always care what the spec says, and that’s never going to change Did I miss something or is everyone back in 1970s, working in waterfall processes now?
I read that as "the business caring about what the spec says will never change" rather than "the spec will never change".
Re: Specsmaxxing – On overcoming AI psychosis, and why I write specs in YAML
#87the token usage isn’t sustainable. formal english is a barrier but requirement for specification. brevity is the language of money and that’s the premise of management using ai. fyi language alone can’t define/describe requirements which is why UML existed.
Natural language is a fully general system and can define and describe everything. You could deterministically process any UML diagram into a prose equivalent. And in fact you couldn't do the other way around (any prose -> UML) because UML is less powerful than natural language and actually can't express everything that natural language can.
> can define and describe everything.
Can it also fully describe a composition by Bach or a Rembrandt's painting? In some weird, overly complex way it probably 'could', but it would be very painful. That's why we pick other forms of expression. We use other forms of expression to compact and optimise information delivery. Another benefit is that we cut out the noise. So yes UML cannot describe everything natural language can, but then again why should it - it was designed as a specific framework for designing relations between objects. Not more and not less. Similar for sequence diagrams or other forms of communicating ideas efficiently.
Re: Specsmaxxing – On overcoming AI psychosis, and why I write specs in YAML
#88What is it with people and procrastinating with the most useless shit you can imagine? First it was choice of editor: people were micro optimizing every aspect of their typing experience, editor wars where people would literally slaughter over suggesting another camp. Editor wars v2: IDEs arrived and second editor war began. Revenge of the note taking apps: Obsidian/Roam/Joplin/Apple Notes/Logseq. Just one plugin, ju…
[deleted]
Re: Specsmaxxing – On overcoming AI psychosis, and why I write specs in YAML
#89What is it with people and procrastinating with the most useless shit you can imagine? First it was choice of editor: people were micro optimizing every aspect of their typing experience, editor wars where people would literally slaughter over suggesting another camp. Editor wars v2: IDEs arrived and second editor war began. Revenge of the note taking apps: Obsidian/Roam/Joplin/Apple Notes/Logseq. Just one plugin, ju…
>Do people NOT have anything else in life? How are y’all finding time to do all of this shit? Are you doing it on company time? Do you have hobbies, do you learn foreign languages, travel, have kids or spouses, drive a car, other thousand “normie” things outside of staring at the freaking monitor or thinking about this shit 24/7? Did I miss the invention of a Time Machine? How are any of those things even remotely as…
If you have ever been to car forums, it's quite the same there.
People are people.
Re: Specsmaxxing – On overcoming AI psychosis, and why I write specs in YAML
#90I'm tired, boss. This industry has become a parody of itself, and people are celebrating.
It's ok friend, all I did is put acceptance criteria in a list so I can parse it and quickly track cross-references. The rest is just Elixir/Phoenix and some creative writing.