I get that writing logs can be incredibly frustrating, but most of the time people are looking at logs because either something went wrong, or they have a hunch that the program is misbehaving and they're looking for a clean sign or signal that they are on the right track.
If I've spent multiple hours on someones broken piece of code, the last thing I want to be thinking is "did some non-deterministic chat-bot write this?", "are these logs even internally consistent?", "Why does this log mention code that doesn't exist?".
I get that is most devs least favorite part, but logs and errors are supposed to be unshakable, ground-truth understandings, things that point you to the light in a dark room of broken spaghetti code and misunderstandings.
Think about this from a users or a testers perspective, can you imagine the compounding frustration you would experience? To be chasing a skein of understanding through wall of text that you only mostly understand, to find out that the hunch was based on a red-herring by a dev who wasn't bothered to help you in return.
Not to mention the amount of non-bugs you are generating for yourself in the future, we already have bug bounties being swarmed by LLM-gen faux-bugs, how is anyone supposed to reason about real bugs if the logs are only tangentially related to the truth?
I'm no history buff, so i found it quite fun just as a game.
the system is quite easy to cheese by simply going back and re-guessing once you have the answer, was really enjoying the scoring aspect until I figured out how simple it was to get close to 100%.
Understandable cause its still a PoC and very much a beta, but thought I'd give you the heads up.
Looking at the comments, most people are approaching this as 'grow, like trees'.
We're literally talking moonshot projects here and nowhere does the brief mention specifically trees, or aerobic respiration/processes, there is plenty of room for using Chitin, Spider silk, keratin or a combination of biopolymers to form resilient composite structures.
There's already been videos of people using these as doping agents or additives for bulletproof armor, to middling success.
The synthesis via yeast or e.coli for most of these are partially solved problems, its more texturing them or using bio-mechanical processing to form thread or ply or load bearing panels that seems to be the major hurdle.
Also, being able to reliably source component and materials from near vacuum or whatever asteroid that happens to wander by that makes this a much more difficult problem to even define.
I get that is most devs least favorite part, but logs and errors are supposed to be unshakable, ground-truth understandings, things that point you to the light in a dark room of broken spaghetti code and misunderstandings.
Think about this from a users or a testers perspective, can you imagine the compounding frustration you would experience? To be chasing a skein of understanding through wall of text that you only mostly understand, to find out that the hunch was based on a red-herring by a dev who wasn't bothered to help you in return.
Not to mention the amount of non-bugs you are generating for yourself in the future, we already have bug bounties being swarmed by LLM-gen faux-bugs, how is anyone supposed to reason about real bugs if the logs are only tangentially related to the truth?