pbowyer
Joined 13 years ago
Joined 13 years ago
He's right that histories start too late, and I'd like to see more posts like this that trace the history back further than the last 5 years. Like for databases, a lot can go back 20+ years and it's good to read how the idea came about (independently from many people), how it developed over time and why.
I've had Tuya and Aqara sensors outside, undercover and out of direct rain for the past 3 years, and every one lasts about a year before the humidity sensor gets stuck at the maximum reading. Even bringing it indoors doesn't get it working again. I'm hoping the built-in heater on the SHT45 will help when we're sat in sea mist or sea fog and keep the sensor working for longer.
Ignore the haters, they're a HN rite of passage. Good luck with your writing!
I've been experimenting with using Markdown (in Typora) in place of Word, but it (and others I've looked at) have zero support for image positioning or sizing, or a way to have different (pre-defined) styles on different tables.
Which is a shame because I like keeping my documents in plain text, in version control and efficiently read by my LLMs. LyX (https://www.lyx.org/) for LaTeX is the closest to what I'm thinking of that I know of, but maybe something exists for Asciidoc or Typst.
To fix this you currently need to make your own copy of the bundled model catalog [2] and opt Luna into MultiAgent V2.
1. https://github.com/openai/codex/issues/32031
2. https://github.com/openai/codex/issues/32031#issuecomment-51...
I keep Claude around for some specific tasks:
- Linked up to Figma MCP to implement front-end stuff
- Data analysis, in the "Connect AI to a data source and ask questions" way. I've tried both Opus 4.8 high and GPT 5.5 high for this and Opus is stronger because it gets the intent in the question better
I used to keep it around for planning too, but the 4.8 plans have had more holes than swiss cheese.
Do you find that makes a difference in your work? I've been using 5.5 high/xhigh to optimize and benchmark a C codebase, and just reading the initial code virtually fills the first context window. A session will auto-compact 5-15 times, but it seems to do okay in spite of that because the task is mainly focused on the latest window each time.
I think for programming the strength of GPT over Opus is winning here over the context window.
AI native in the sense that it papers over the pain points.
New JIRA admin? AI will set it up to do what you want (after all, Atlassian has a great training set as they can see which Cloud installs work well)
Need to set up a workflow? Bam, AI to do that.
Need to onboard a user or manage permissions? Again, have a chatbot to do it (as a time-to-time Jira standin Admin, changing permissions always needs doing in 2+ places and devolves into a "Can you see this yet?" round of questions)