Awax

@tvaziri@mastodon.social I raise you with the Paramount logo at the beginning of Indiana Jones movies. https://youtu.be/idoLHJiDOY8?is=aPkQi7Ls7me9KaFt

@tvaziri@mastodon.social well it matched exactly my recollection. This was the “non boring version” ;)

@tvaziri what are you talking about? There are no robots no spaceships no wizards no monsters in “The Pitt” so they can’t be any VFX in that show. #clueless

@marcoarment@mastodon.social If “major” means “used for a significant portion of code written/generated”, I would want to leave room for one or two new languages, authored by LLM for LLMs Otherwise, with access to LLM themselves, my guess is that we will see a Cambrian explosion of small purpose built languages

@stroughtonsmith@mastodon.social maybe this is what Tim Cook belives when he hangs out with the president.

@caseyliss and when he was driving F1, the joke in France was that he was spending more time in the gravel pit than on the track

@isaiah@mastodon.social if a spec driven session is failing to produce good outcome on its own, requiring a lot a steering and correction, I take time with the agent to analyse what went wrong and update the agent overall instructions, the instructions on how to conduct research, how to create a spec from that research and how to follow the spec Hopefully it converges to instructions that output reliable specs and corresponding code

@marcoarment did you manage to score one?

@mongrelion@fosstodon.org @isaiah@mastodon.social the details of the bug is irrelevant to keep the spec in sync. What matters is the state of the code once the bug is fixed. You could start a different context and ask to sync the spec just based on the current diff. Also, as the context window increases, compaction ensures that the information relevant to sync the spec is still present.

@atpfm@mastodon.social @siracusa@mastodon.social regarding looking at the internals of the discussion with the agent, you can check OpenCode, the OSS alternative to ClaudeCode. Famously you cannot use it with your ClaudeCode plan (and will get banned for it), but it can connect it any other model provider (even the one redistributing Claude models). This is why we use it at work using a mix of Copilot and Bedrock//Vertex. If you open the context details window, you will see ALL messages exchanged with the model. And those are stored in a local SQLite DB. We built tools at work to read that DB and assess the cost of features and find efficient patterns.

@isaiah@mastodon.social this is what one tries to achieve with Spec-Driven-Development and committing the spec along with the generated code Generating the code a second time can output something completely different but it could still be considered valid with respect to the spec.

@isaiah@mastodon.social learning to let go also helps Who am I to say if this does or does not respect the spec :)

@isaiah@mastodon.social so far the framework for SDD that gave me the best result is OpenSpec for small stuff or bug fixing not part of a new feature, I work directly on the code and then ask the agent for help to “resync” the spec with the new reality of the code. OpenSpec is very resilient and works very well for that. The other SDD frameworks I explored could not cope with that

@isaiah@mastodon.social like with coworkers, especially junior ones, let go the fact that the code will be exactly as you want it to be and that there’s one perfect implementation for the thing you want to achieve and that any alternative is subpar and inacceptable. Settling for good enough and that many different alternatives can still meet the initial requirement. You cannot win every battle so focus on those than allow to win the war on what a good product actually is instead of exhausting yourself fighting the agent on every single line of code. Knowing that product management will change their mind in two weeks anyway also helps: the agent will help you adapt

@marcoarment@mastodon.social no issue mixing PLA with support interface filament in the one nozzle of the H2S ? That’s the one argument for the “auxiliary nozzle” of the X2D: no mixing of support material

@pyrtsa@mastodon.social @joe@f.duriansoftware.com packing (int32,int32) into a single int64 is safer