78 karma · joined September 15, 2025
I was rather commenting on the tone that Thoughtworks decided to "take 10 engineers and put them in one room". I took that wording literally, imagining how they grabbed these 10 engineers with a big hand and dropped them off where they wanted them to develop their airline IROps system.
I hope you asked them beforehand :-)
Care to elaborate? We are using TOML for config files and just do fine.
We wanted to make the onboarding as simple as possible so that we can:
0. Log you in through your existing GitLab.com or GitLab self-hosted account 1. List all your groups and projects to decide where to install the runner 2. Disable GitLab.com's own instance runners (otherwise our Runners are not picked up) 3. Install the Runner 4. Optionally: When installing an agent runner, we are able to reply to read and reply to all your issues where you tag us via `@Rocket` -- this runs completely on your machine that we host for you! It doesn't run on our infrastructure and we only access your runner machine for auto-cleaning its caches.
That's really all the RocketRunner does with you granting us permissions when logging in.
We are looking into ways how to possible scope access better! Thanks for your feedback!
(Sorry for posting this twice, but we'd really love to get more user feedback)
Are they implying a causal relationship between their shrinking user base and their focus expansion? The article doesn't give any proof whatsoever.
Quoting from your other website (linked from OT website): https://www.overflow.dev/
> React Flow examples show possible approaches, not production coverage. They omit edge cases, performance considerations, and maintenance paths. Overflow gives you the end result: hardened behavior, documented APIs and types, and components that are ready to ship.
So it's "us" vs. "they"? "They" actually build a very widely adopted open-source solution, why don't you contribute back if "they" omit so much?
What Linux tools are you guys using for image generation models like Qwen's diffusion models, since LMStudio only supports text gen.
Some historian say this might have actually caused the 1st world war since these German activities provoked the British empire.
[1] https://en.wikipedia.org/wiki/Berlin%E2%80%93Baghdad_railway
Happy user of https://reflex.dev framework here.
I was tired of writing backend APIs with the only purpose that they get consumed by the same app's frontend (typically React). Leading to boilerplate code both backend side (provide APIs) and frontend side (consume APIs: fetch, cache, propagate, etc.).
Now I am running 3 different apps in productions for which I no longer write APIs. I only define states and state updates in Python. The frontend code is written in Python, too, and auto-transpiled into a React app. The latter keeping its states and views automagically in sync with the backend. I am only 6 months into Reflex so far, but so far it's been mostly a joy. Of course you've got to learn a few but important details such as state dependencies and proper state caching, but the upsides of Reflex are a big win for my team and me. We write less code and ship faster.