← Feed

Posts

• View post

  @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

• View post

  @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 exhaustin...

• View post

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

• View post

  @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

• View post

  @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.

• View post

  @marcoarment did you manage to score one?

• View post

  @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