|
|
|
|
|
by simsla
116 days ago
|
|
I've used stuff like this for a hobby project where "effort to write it" vs "times I'm going to use it" is heavily skewed [0]. For production use cases, I can only see it being worth it for things that require using an ML model anyway, like "summarize this document". [0] e.g. something like the below which I expect to use maybe a dozen times total. Main routine: In folder X are a bunch of ROM files (iso, bin, etc) and a JSON file with game metadata for each. Look for missing entries, and call [subroutine] once per file (can be called in parallel). When done, summarise the results (successes/failures) based on the now updated metadata. Subroutine: (...) update XYZ, use metacritic to find metadata, fall back to Google. |
|