> Endpoint views break down request volume, errors, latency, and status codes. Crash and ANR detail adds the app version, device, and thread context around a failure. This is where a problematic UI transition can be connected to a backend or runtime condition.
The project README reads like a first draft straight out of Claude, and it's incredibly off-putting. The 'Show HN' post here is so much better; clearly you're capable of writing a decent explanation of what this project is, its history, and for whom you've built it. Take the time and write the damn README yourself.
If you expect human attention, put in human effort.
You're a sophomore at UT, so as a UTCS alum (:wave: from a fellow Turing Scholar) I'm not letting you off the hook. Unless things have majorly changed, I know you're taking 6 hours of writing-heavy coursework.
Wow Turing Scholars! you guys are like the navy seals of CS at UT lol. Yes I appreciate the insight and will actually hand write it (and copy some parts of this post, but it is a bit too goofy to just use the post straight up). One thing you mentioned, I've never heard of Readmes including a history of the project, because I thought Readmes were like a small intro doc with a bunch of hyper links only.
> Endpoint views break down request volume, errors, latency, and status codes. Crash and ANR detail adds the app version, device, and thread context around a failure. This is where a problematic UI transition can be connected to a backend or runtime condition.
The project README reads like a first draft straight out of Claude, and it's incredibly off-putting. The 'Show HN' post here is so much better; clearly you're capable of writing a decent explanation of what this project is, its history, and for whom you've built it. Take the time and write the damn README yourself.
If you expect human attention, put in human effort.
You're a sophomore at UT, so as a UTCS alum (:wave: from a fellow Turing Scholar) I'm not letting you off the hook. Unless things have majorly changed, I know you're taking 6 hours of writing-heavy coursework.
Wow Turing Scholars! you guys are like the navy seals of CS at UT lol. Yes I appreciate the insight and will actually hand write it (and copy some parts of this post, but it is a bit too goofy to just use the post straight up). One thing you mentioned, I've never heard of Readmes including a history of the project, because I thought Readmes were like a small intro doc with a bunch of hyper links only.
For example, I looked at the these two Readmes: https://github.com/rybbit-io/rybbit/blob/master/README.md <-- this one is lovely https://github.com/supabase/supabase/blob/master/README.md
Both include pictures, features, ect, but not really histories, unless I'm understanding your comment incorrectly.