Harness Engineering
habitat-thinking.github.io
Harness Engineering
1–10 of 47 posts
Re: Harness Engineering
#2I like how agent review is a deprecation target. explicitly. Se then a harness matures by getting dumber and cheaper, not smarter.
Re: Harness Engineering
#3What even is this "AI Literacy framework"? When I see such overengineering I look at what the author has done. In this case, I find the author runs a consultancy on engineering "Habitats for Humans and AI" (https://www.russmiles.com/), listing a bunch of books he did not write (the author names are conveniently cropped out). This doesn't even belong on LinkedIn.
Re: Harness Engineering
#4Not saying this is AI-gen but it's very dense and doesn't read like something I could glean info from easily
Re: Harness Engineering
#5It’s fascinating to live through a the emergence of a new technology and to see people trying to make sense of it as they go.
I personally think that a lot of the words used around AI, harness, SKILLS, agents, RAG.. are make up words or close to it, words that do not have profound semantics, even though people are trying to, often after the fact, make sense of them.
It’s just popular words that are different enough that people like to use them to claim a new knowledge, or to market a product.
But we could use AI tooling instead of harness in the abstract, and it would be better to use more precise terms for more concrete use cases, agent loop, CLI, IDE..
It was a fun game at a time where papers were competing for attention, but now that it has become a proven technology, I hope we can find more precise and meaningful words.
Re: Harness Engineering
#6[dead]
Re: Harness Engineering
#7What even is this "AI Literacy framework"? When I see such overengineering I look at what the author has done. In this case, I find the author runs a consultancy on engineering "Habitats for Humans and AI" ( https://www.russmiles.com/ ), listing a bunch of books he did not write (the author names are conveniently cropped out). This doesn't even belong on LinkedIn.
I'm not the author -- but I am currently fortunate to be sitting in a workshop he is teaching on the topic and figured HN might like (especially since he gives a lot of his content out for free/OSS).
As someone who does loads of AI-driven dev and governance, I'm finding there are a lot of great nuggets here. Between him (chaos engineering) and Kent Beck (extreme programming) I'n a kid in the candy store and wanted to share.
Re: Harness Engineering
#8Not saying this is AI-gen but it's very dense and doesn't read like something I could glean info from easily
It is pretty obvious that Claude wrote it. No human writes README that long, and it's one of the contributors: https://github.com/Habitat-Thinking/ai-literacy-superpowers
Re: Harness Engineering
#9It’s fascinating to live through a the emergence of a new technology and to see people trying to make sense of it as they go. I personally think that a lot of the words used around AI, harness, SKILLS, agents, RAG.. are make up words or close to it, words that do not have profound semantics, even though people are trying to, often after the fact, make sense of them. It’s just popular words that are different enough t…
Hear hear! We techies are bad at naming things. "NoSQL" is probably a top contender there.
Re: Harness Engineering
#10This part seems relevant - they make explicit the difference between their HARNESS.md document and AGENTS.md. It's actually interesting: https://habitat-thinking.github.io/ai-literacy-superpowers/p...