ramoz

5 ms·

91.
by ramoz 5mo ago
yes, am familiar with the "code is spec" trope. Shame us all for moving away from something so perfect, precise, and that "doesn't have edge cases." Hey - if you invent a programming language that can be used in suc
92.
by ramoz 5mo ago
> If I had to roll out such a development process today, I’d make a standardized Markdown specification the new unit of knowledge for the software project. Product owners and engineers could initially collaborate on this spec and on test
93.
by ramoz 5mo ago
I was about to comment: "HTML creates too much friction after doing all sorts of visual explainers" ... thanks for articulating it well. As a layer of abstraction, it also creates more requirements: need a browser, likely need inc
94.
by ramoz 5mo ago
He's already within the consulting sphere around hospitals in his area.
95.
by ramoz 5mo ago
He's already in the whole consulting sphere around these hospitals in his area.
96.
by ramoz 5mo ago
I don't have time for that. I just told him he needs to hire somebody
97.
by ramoz 5mo ago
A non-technical friend of mine has just won some hospital contracts after vibecoding w/ Claude an inventory management solution for them. They gave him access to IT dept servers and he called me extremely lost on how to deploy (cant co
98.
by ramoz 5mo ago
Yea that's fine and understandable. But like I said, this is something for those users. I launch many review processes locally with `claude -p`
99.
by ramoz 5mo ago
This is much of a something burger for users who actively use `claude -p` under their subscription. Users will have to do their own math, but that 200 could come and go quite fast and then you're hitting normal API rates versus what yo
100.
by ramoz 5mo ago
Happy to change the title if there is explicit clarity on what my `claude -p` usage costs me today & it not differing from what it'll cost me once the change is in effect.
101.
by ramoz 5mo ago
I wasn't able to post the official links because it was already posted by simple reposters who didn't understand, and titled their HN posts as "you get credits" basically this is the original thread https://x.
102.
Claude subscription changes coverage of `claude -p`(x.com)
60 points by ramoz 5mo ago|50 comments
103.
by ramoz 5mo ago
The wording in the press is very confusing. Not sure if deliberate. If you're an active `claude -p` user, it will now cost you API rates vs being able to user your subscription. UPDATE: https://x.com/lydiahallie/s
104.
by ramoz 5mo ago
I’ve done a lot of exploration here. Visual explainers certainly come in hand. You need to have both the extra time and cost of tokens accounted for when you ask for these. As well as maintainability - you lose things like vcs/diffs ov
105.
Show HN: jj diff review integrated with agents(twitter.com)
5 points by ramoz 5mo ago|0 comments
106.
Show HN: Rig – a Ghostty sidecar for managing agents(github.com)
6 points by ramoz 5mo ago|0 comments
107.
by ramoz 5mo ago
It never worked well for me. The only thing I really needed outside of the harnesses was a better plan review surface. https://github.com/backnotprop/plannotator
108.
by ramoz 5mo ago
https://plannotator.ai/ now works for codex. free & open source: https://github.com/backnotprop/plannotator
109.
Show HN: Plannotator for Codex(twitter.com)
2 points by ramoz 5mo ago|1 comments
110.
Show HN: Embed your Codex pets in React apps(github.com)
1 points by ramoz 5mo ago|0 comments
111.
by ramoz 5mo ago
Codex actually feels severely lacking to me, trying to switch off Claude Code. I'm trying every day. The models honestly feel on par, but the Harness and the CLI are somewhat painful to work with.
112.
by ramoz 5mo ago
Yeah, dude, stop being fucking weird. Im an adult, you're an adult that misinterpreted my gripe (with langchain mention, not the grammar)... If you want to get fussy, be better about it. Your fuss is annoying and unintuitive. Ask gen z
113.
by ramoz 5mo ago
I wasn't complaining about grammar. I didn't even notice that.
114.
by ramoz 5mo ago
Rigghht. If you're trying to make a point, go ahead and be straighter about it.
115.
by ramoz 5mo ago
There was a bigger opportunity here to mention OpenCode, Pi, etc - open Harnesses that provide accessibility to the oss models, a platform others can build around, and something enterprises can adopt in reliable ways; for the most dominant
116.
by ramoz 5mo ago
> DeepSeek, Qwen, Kimi, GLM — running on the LangChain, vLLM, llama.cpp, and Ollama stack "running on the LangChain" ?? EDIT: look, I think the general discussion is important, so I don't want to denounce the article. I,
117.
by ramoz 6mo ago
What provider do you use for Kimi
118.
AI Progress doesn't feel as fast as we're told(backnotprop.com)
4 points by ramoz 6mo ago|1 comments
119.
by ramoz 6mo ago
Opus 4.7 is very rough to work with. Specifically for long-horizon (we were told it was trained specifically for this and less handholding). I don't have trust in it right now. More regressions, more oversights, it's pedantic and
120.
Show HN: Bro Skills – address the daily gaps your agents still struggle with(github.com)
1 points by ramoz 6mo ago|0 comments

More ›