DDisasm: Reversible (bi-directional) Disassembler
Comments
Insights
Engineering perspectives on architecture, product development, AI, and the everyday decisions behind useful software.
From the engineering desk
Browse practical articles or follow the latest technology updates.
Subscribe via RSS →Curated links from external sources — not 360Softy original articles.
Comments
Factory on Vercel Non-technical teams were bottlenecked on engineering Droids hit Vercel's APIs to build and deploy autonomously Going self-serve exposed Factory's backend to a new category of threat Observability and WAF handle protection at the network level Tens of millions of backend API requests served daily 350ms p95 response time Scaled backend, internal tooling, and security without a dedicated infrastructure team API routes handle the customer-facing API, which launched in its own
Factory on Vercel Non-technical teams were bottlenecked on engineering Droids hit Vercel's APIs to build and deploy autonomously Going self-serve exposed Factory's backend to a new category of threat Observability and WAF handle protection at the network level One billion backend API requests served daily 350ms p95 response time Scaled backend, internal tooling, and security without a dedicated infrastructure team API routes handle the customer-facing API, which launched in its own section
Article URL: https://www.modelrepublic.org/articles/the-reporters-at-this-news-site-are-ai-bots.-openai%E2%80%99s-super-pac-appears-to-be-using-it-to-advance-its-political-agenda Comments URL: https://news.ycombinator.com/item?id=49150561 Points: 205 # Comments: 104
Article URL: https://qwen.ai/blog?id=qwen3.8 Comments URL: https://news.ycombinator.com/item?id=49150470 Points: 1045 # Comments: 558
Article URL: https://sf.isopolis.city/ Comments URL: https://news.ycombinator.com/item?id=49149966 Points: 331 # Comments: 74
Load balancing analytics now shows traffic served by your fallback pool separately from traffic routed to the same pool by normal steering. Previously, requests were grouped by pool name alone. If the pool acting as your fallback also received traffic through your steering policy, both appeared as a single series, so it was not obvious from the graph whether Cloudflare was still making health-based routing decisions or had fallen back to the pool of last resort. Because the fallback pool ignores
Let’s start with a conversation
An idea, a challenge, or a system that needs to work better. We’ll help you understand the next step.
Prefer email? [email protected]