SteveVeilStream

I wanted to play with Jev but was not sitting on a large collection of text I wanted to classify. Games are a fun way to experiment because you can start from nothing but take advantage of being able to use a large number of fast and affordable decisions to allow a simulated environment to evolve over time.

Because this is a demo of Jev, you can access a lot of the underlying details to see what calls are made and what the responses were.

There is a demo you can play with (link in the readme) that uses my API key. The API is very affordable.

I think I need to tweak the gameplay variables to make it a little more engaging.

I just received an e-mail indicating this may be required by April 20th. I can't think of two accounts that people would want to keep more separated than these two. I've never actually trusted GlassDoor enough to leave a review and have always been happy with my employers but I can imagine a lot of people would not feel comfortable with this mixing of accounts.

"Connect accounts for one easy login Glassdoor is teaming up with Indeed to streamline your job search. We're introducing one login to connect Glassdoor and Indeed accounts.

When you connect accounts, your recent profile data will be synced, giving you access to better job matches and hiring employers across both sites.

Our commitment to anonymity Your anonymous activity on Glassdoor, like company reviews or demographic information, won't be shared with Indeed and will remain anonymous.

What's next For right now, you’ll need to connect accounts to apply to jobs on Glassdoor and get improved job matching. Starting on April 20th, 2026, you may be required to log in with a connected account to get full access to Glassdoor."

Thanks. Adding memory is an interesting idea. I'd probably want to do it a little differently than what is done in the main apps to avoid overlap. I like the idea of being able to tag conversations and then use that "tag" to organize memory. E.g. You might want to have one set of conversations about fitness, another about travel, another about career, etc. with no overlap between them.

Claude Code does it. Check out the JSONL files.

Sometimes I need to give Claude Code access to a secret to do something. (e.g. Use the OpenAI API to generate an image to use in the application.) Obviously I rotate those often. But what is interesting is what happens if I forget to provide it the secret. It will just grep the logs and try to find a working secret from other projects/past sessions (at least in --dangerously-skip-permissions mode.)

If I am not mistaken, Claude sometimes pulls an API key out of a .env file and drops it into that folder. It might be neat for you to add a feautre specifically for identifying any keys that are in that folder.

This is an exmaple of a potentially problematic prompt: "You are an expert data analyst combining statistical rigor with deep domain knowledge. Your goal is to deliver data-driven insights — not summaries or visualizations — grounded in real data and supported by complete and transparent reasoning."

And they say: "This includes detection of chain-of-thought elicitation used to construct reasoning training data." ... "We are developing Product, API and model-level safeguards designed to reduce the efficacy of model outputs for illicit distillation, without degrading the experience for legitimate customers."

It's going to be very hard to generate outputs that people need but that also can't be used for distillation. For example, it's a good practice for many reasons including audibility to ask for the chain of thought. In fact, I'd argue it's essentially impossible to modify the outputs in a way that makes them less useful for distillation without degrading quality for legitimate users.

So then their only viable option is to try to identify the traffic. However, that is very hard because: "In one case, a single proxy network managed more than 20,000 fraudulent accounts simultaneously, mixing distillation traffic with unrelated customer requests to make detection harder."

This local legislation has been the subject of some discussion. Is it prudent or does it discourage tech investment? I'm personally not excited to see that AI and data-centre customers have to compete for MW under a fixed cap while other industries are exempt.

"Through Bill 31, the Energy Statutes Amendment Act, and a new regulation, there is now a requirement for prospective AI and data-centre projects to take part in a competitive selection process to access clean electricity. This requirement does not apply to traditional industries, such as mining, liquefied natural gas (LNG), forestry, manufacturing or hydrogen for domestic use." "The allocation targets for these projects are for as much as 400 megawatts for the first two years."

That's a fair point. I do think what's most interesting this time is the potential for new use-cases (users) vs the replacement of existing ones. I agree that there are better ways for serious developers to work than to be using Claude Code on the web. On the other hand, you can now set up someone in the marketing or product management departments with the tools in an afternoon and then they can create widgets, perform custom analysis on data, experiment with prototype ideas, etc. and they don't even need a laptop. All you need is a mobile phone with a browser. It could be neat for students as well. "Build me an app to help me study for X". Time will tell exactly how people use it.