1,026 karma · joined September 25, 2010
- Ongoing work on an airline announcement engine that works with flight simulators
https://github.com/fearlessfrog/MSFS_Universal_Announcer
- A multiplayer board game for Discourse forum users that is not the popular Risk (tm).
https://github.com/fearlessfrog/discourse-not-risk
Both have a fair bit of traction, but is often the case, keen to do something new this month.
Also, is there a way to stop the 'Satellite Inspect' dialog from coming up when clicking around the globe? It obscures a bit of the map.
We do home property and inventory services using AI on photos as well and the key thing we've found so far is that the biggest rival to those features is just people dragging photos into chatgpt and asking away. So the key here is differentiating from that and making something better and more accurate. What we did was to basically build a better and deeper prompt and history, e.g. context is king in a vertical. So that means the other info the user has put about the property, the memory of previous things asked or seen, combining with publicly available property info we already gather - this would make the information more valuable than straight gpt usage.
So what more can you bring to the bare prompt on the photos to help? What can you build in terms of info about the zip, so you do more 'vertical stuff' before the api call.
> ChatGPT is widely used for practical guidance, information seeking, and writing, which together make up nearly 80% of usage. Non-work queries now dominate (70%). Writing is the main work task, mostly editing user text. Users are younger, increasingly female, global, and adoption is growing fastest in lower-income countries
hermes4: We're all just stupid atoms waiting for inevitable entropy to plunge us into the endless darkness, let it go.
But like you said, it was meant more TDD as 'test first' - so a sort of 'prompt-as-spec' that then produces the test/spec code first, and then go iterate on that. The code design itself is different as influenced by how it is prompted to be testable. So rather than go 'prompt -> code' it's more an in-between stage of prompting the test initially and then evolve, making sure the agent is part of the game of only writing testable code and automating the 'gate' of passes before expanding something. 'prompt -> spec -> code' repeat loop until shipped.
One thing I've done with some success is use a Test Driven Development methodology with Claude Sonnet (or recently GPT-5). Moving forward the feature in discrete steps with initial tests and within the red/green loop. I don't see a lot written or discussed about that approach so far, but then reading Martin's article made me realize that the people most proficient with TDD are not really in the Venn Diagram intersection of those wanting to throw themselves wholeheartedly into using LLMs to agent code. The 'super clippy' autocomplete is not the interesting way to use them, it's with multiple agents and prompt techniques at different abstraction levels - that's where you can really cook with gas. Many TDD experts have great pride in the art of code, communicating like a human and holding the abstractions in their head, so we might not get good guidance from the same set of people who helped us before. I think there's a nice green field of 'how to write software' lessons with these tools coming up, with many caution stories and lessons being learnt right now.
edit: heh, just saw this now, there you go - https://news.ycombinator.com/item?id=45055439
[1] https://developers.googleblog.com/en/introducing-gemini-2-5-...
Buy, make and domestically develop drones, lots and lots of drones.
https://steamcommunity.com/sharedfiles/filedetails/?id=21021...