24 hours is better imo than am-pm.

I made an app widget to measure time in percentages instead of 24 hours

https://www.reddit.com/r/Time/comments/1ujj9py/comment/ov6qo...

Constant battle in my (American) house. I set my digital devices to 24-hour time years and years ago, because I ran into situations where there could be genuine confusion about which "4:32" someone might be referring to (global company, irregular work hours, etc.), but my family insists on calling it "military time", which is so very strange because they're well travelled and have been plenty of places that use 24-hour clocks.

“Military time” is the common name for it in the US. It’s the only way to ever hear people refer to it.

this is definitely a backdoor, not necessarily that they use it to infiltrate users but definitely they put them at risk.

reminds me of a bug I found in some tplink router it compared passwords of 3 different users but that table was empty so basically 15 NULL bytes would log you in as admin lol

what if it contained a zero day for tesseract and the script you thought you got is just a throwaway

those spikes in march and june? war with iran. interesting...

my experience with ffmpeg scene detection is that it's flaky. it works, sometimes, but not reliable by any means

would be nice to be able to simply get the list instead of having an ominous heatmap

I will make it happen tonight. keep in touch.

this was absolutely fascinating to read

that's sort of what skills are.

create a skill that transformed the json then "/<skill> <prompt>"

code is like assembly now.

in the olden days (pre-LLMs) we would write high-level code.

the entire layer was high-level code and rarely would we ever need to peak into the assembly:

writing, debugging, architecting, reviewing, testing - all were done in the high-level language layer.

---

welcome to present day:

since we don't write code - we write intents, we also shouldn't review code either - we should review intents.

I don't review my code anymore. I ask the agent to generate markdown docs, graphviz diagrams, changelogs, audit reports, etc. I only review that.

I also ask it to write test and evaluate by whether the tests passed or not. I don't need to peak into the tests code - I can also ask plain english, pseudocode, control flow graph, whatever it is I want.

I can ask it to find errors or missing tests and improve that too!

code is like assembly now.

rare are the cases you would need to peak into that level.

> I ask the agent to generate markdown docs, graphviz diagrams, changelogs, audit reports, etc. I only review that.

From an alternative perspective, that is the code.

I sometimes end up at or near this conclusion when considering the future.

Consider some software that was written by AI purely using markdown files. The spec was sufficient enough to classify all of the business logic, conditionals, etc... You might even end up creating "loops" that tell AI to do something over and over again. Some markdown files become standard, repeatable "functions" that are to be followed EXACTLY (determinism). Some markdown files become assertion tests. Heck, the markdown file might eventually invent some kind of "typing system" so that you know when you're working with the person "class", it's always going to have the same facets.

I love the concept of it going in this direction - we already had plenty of languages to tell a computer what to do, we've just generated MORE text at a higher level and made it less deterministic.

Just to clarify, I don't think it's likely that this is the end result, but it sure is funny to think about.

this is amazing exactly what I always wanted

how did this even get approved by app store? that's actually surprising