Insights
Practical writing on software architecture, SaaS products, AI automation, legacy modernisation, and the business of building reliable systems.
Curated links from external sources — not 360Softy original articles.
Recent and related: Noise infusion banned from statistical products published by Census Bureau - https://news.ycombinator.com/item?id=48517377 - June 2026 (604 comments) Comments URL: https://news.ycombinator.com/item?id=48768992 Points: 408 # Comments: 135
We have released version 5 of @cloudflare/workers-types. This release simplifies the package to expose only the latest runtime types. We still recommend that you generate types for your Worker using wrangler types, but if you want to use the package directly, you can install it with your package manager of choice: npm i -D @cloudflare/workers-types@latest yarn add -D @cloudflare/workers-types@latest pnpm add -D @cloudflare/workers-types@latest bun add -d @clo
segments can now be managed from the with the new command.Vercel FlagsVercel CLIvercel flags segments A segment is the targeting primitive a flag uses to decide who sees what. Membership composes from three repeatable tokens: , , and . Pass them to or for incremental edits. For full replacement, takes the entire segment definition as raw JSON.include:exclude:rule:--add--remove--data All segment commands support output, making them scriptable from CI, local workflows, and agent-driven pipel
Your agent can now inspect via the Vercel MCP and CLI for , the open-source agent framework.Agent Runseve eve traces are automatically ingested when deployed to Vercel and available as Agent Runs. The new and let you find projects with runs, list recent runs, and retrieve full traces, including reasoning, tool calls, and token usage.Vercel MCP toolsVercel CLI commands Vercel MCP tools: Vercel CLI commands: Every CLI subcommand supports for machine-readable output, and traces render as markdo
Article URL: https://righttointelligence.org/ Comments URL: https://news.ycombinator.com/item?id=48768951 Points: 536 # Comments: 191
I wasn't looking for a bug,I was auditing one of the foundational primitives in my infrastructure. The implementation was compact, the test coverage was solid, and nothing immediately stood out. For a long time, I believed that low-level infrastructure should protect developers from making questionable modeling decisions. It felt like responsible engineering. If a value looked practically useless, why should a primitive allow it to exist? That assumption naturally led me to introduce another rul
A research note prepared for the Superteam Australia bounty program If you've spent any time around Australian startup Twitter, LinkedIn, or a Stone & Chalk co-working kitchen, you've heard some version of the same sentence: "the ecosystem here is fine, but." Fine funding, but scattered across a hundred portals. Fine regulatory intent, but slow to actually land. Fine talent, but expensive and mobile. That "but" is doing a lot of work, and I think it's mostly hiding a more useful truth. Here's th
The Problem If you've ever built a fintech product, you know this truth: the hardest part isn't moving money — it's making sure you never lose it. A wallet engine sounds simple on the surface. Credit. Debit. Balance. But the moment you introduce concurrency, network failures, and the need for auditability, it becomes one of the most demanding distributed systems problems you can tackle. I built a wallet engine that needed to: Handle credits, debits, and wallet-to-wallet transfers Guarantee tha
Work with 360Softy
Book a free consultation and we will tell you honestly whether we can help.
