It would be nice if it showed you 1st, 2nd, semi-finalist, quarter-finalist...

It would also be nice to see progress of some kind, a few minutes in I was wondering if I was near completion or just getting started.

We're building alphaLENS (https://alphalens.io), a suite of tools for professional market research and trading. Public registration opens in days. You can see our company at https://thinkalpha.io.

Stack: Svelte (migrating from React/Redux), MVVM architecture with signal primitives, class-based models with IoC for cross-platform targeting (web + Electron, mobile later). Heavy emphasis on testing and performance.

Looking for: Someone who thinks about problems in detail. You should be comfortable with OOP in JS, understand reactive primitives at a deeper level than hooks, and be able to operate autonomously on a small team.

If this is you, please reach out to me with your resume and a brief intro: jason [at] thinkalpha [dot] io

People want to pretend fundamentals of economics don't exist AND the company has moral obligations to fulfill to consumers. It's laughable.

It's not just nVidia, I've seen other expensive consumer brands getting the same sentiments.

Right, so if you take away the resolver composition (this is graph composition and not route federation), you can do the same things with a similar amount of effort in REST. This is no longer a GraphQL vs REST conversation, it's an acknowledgement that if you don't want any of the benefits you won't get any of the benefits.

My initial goal is to make a functional SillyTavern (AI roleplaying) replacement. SillyTavern builds prompts from a few rigid buckets (character, scenario, lore, system prompt, author's note...), which makes complex setups hard to manage. Content gets duplicated, settings have to be toggled in multiple places, and it’s easy to accidentally carry or modify state across conversations. Over time, it becomes difficult to tell what context is actually in effect.

I’m building an alternative that treats context as small, reusable pieces that can be composed and organized flexibly, rather than locked into fixed categories. Characters, settings, and behaviors can be mixed, reused, or temporarily enabled without duplication or manual cleanup, and edits preserve clear history instead of rewriting the past. The goal is to make managing complex context deliberate and controlled instead of fragile.

Although I’m trying to get the functionality required for roleplaying done first, the app is generic enough for other AI workflows where fine-grained, explicit context control is an improvement over existing chat interfaces. Think: start a new conversation with an assistant and start checking off rules, documents, and instructions to apply to the chat. Regenerate responses with clarifications or additional one-time context layers.

The ones who spend more time developing their agentic coding as a skillset have gotten much better results.

In our team people are also more willing to respond to feedback because nitpicks and requests to restructure/rearchitect are evaluated on merit instead of how time-consuming or boring they would have been to take on.

This could be great for students without sysadmins needing to lodge complaints.