Metastability

590 posts

Metastability banner
Metastability

Metastability

@_metastability

Metastability is a technology company that provides software and web solutions and platform maintenance to small and medium-sized businesses and organizations.

Los Angeles, California, USA Katılım Temmuz 2023
20 Takip Edilen6 Takipçiler
Sabitlenmiş Tweet
Metastability
Metastability@_metastability·
We help you get the most out of your business development. Here are some of the services we offer: - Web Development - Software Development - IT Consulting - Internet Platforms - Automation Systems - Internet Services
English
0
2
2
16.4K
Metastability
Metastability@_metastability·
Warehouse inventory shows 247 units, actual is 183 Multiple systems update stock without coordination, creating drift We implement CRDTs with SurrealDB for conflict-free replication Go Fiber APIs sync real-time via Cloudflare Workers Inventory stays accurate across all systems
English
0
0
1
28
Metastability
Metastability@_metastability·
@gdb This isn't a renaissance - it's architectural surrender. Making agents the "first resort" induces systemic atrophy. You’re building a world no human can comprehend without an AI subscription. This is the industrialization of tech debt and the liquidation of sovereignty.
GIF
English
0
0
0
13
Greg Brockman
Greg Brockman@gdb·
Software development is undergoing a renaissance in front of our eyes. If you haven't used the tools recently, you likely are underestimating what you're missing. Since December, there's been a step function improvement in what tools like Codex can do. Some great engineers at OpenAI yesterday told me that their job has fundamentally changed since December. Prior to then, they could use Codex for unit tests; now it writes essentially all the code and does a great deal of their operations and debugging. Not everyone has yet made that leap, but it's usually because of factors besides the capability of the model. Every company faces the same opportunity now, and navigating it well — just like with cloud computing or the Internet — requires careful thought. This post shares how OpenAI is currently approaching retooling our teams towards agentic software development. We're still learning and iterating, but here's how we're thinking about it right now: As a first step, by March 31st, we're aiming that: (1) For any technical task, the tool of first resort for humans is interacting with an agent rather than using an editor or terminal. (2) The default way humans utilize agents is explicitly evaluated as safe, but also productive enough that most workflows do not need additional permissions. In order to get there, here's what we recommended to the team a few weeks ago: 1. Take the time to try out the tools. The tools do sell themselves — many people have had amazing experiences with 5.2 in Codex, after having churned from codex web a few months ago. But many people are also so busy they haven't had a chance to try Codex yet or got stuck thinking "is there any way it could do X" rather than just trying. - Designate an "agents captain" for your team — the primary person responsible for thinking about how agents can be brought into the teams' workflow. - Share experiences or questions in a few designated internal channels - Take a day for a company-wide Codex hackathon 2. Create skills and AGENTS[.md]. - Create and maintain an AGENTS[.md] for any project you work on; update the AGENTS[.md] whenever the agent does something wrong or struggles with a task. - Write skills for anything that you get Codex to do, and commit it to the skills directory in a shared repository 3. Inventory and make accessible any internal tools. - Maintain a list of tools that your team relies on, and make sure someone takes point on making it agent-accessible (such as via a CLI or MCP server). 4. Structure codebases to be agent-first. With the models changing so fast, this is still somewhat untrodden ground, and will require some exploration. - Write tests which are quick to run, and create high-quality interfaces between components. 5. Say no to slop. Managing AI generated code at scale is an emerging problem, and will require new processes and conventions to keep code quality high - Ensure that some human is accountable for any code that gets merged. As a code reviewer, maintain at least the same bar as you would for human-written code, and make sure the author understands what they're submitting. 6. Work on basic infra. There's a lot of room for everyone to build basic infrastructure, which can be guided by internal user feedback. The core tools are getting a lot better and more usable, but there's a lot of infrastructure that currently go around the tools, such as observability, tracking not just the committed code but the agent trajectories that led to them, and central management of the tools that agents are able to use. Overall, adopting tools like Codex is not just a technical but also a deep cultural change, with a lot of downstream implications to figure out. We encourage every manager to drive this with their team, and to think through other action items — for example, per item 5 above, what else can prevent a lot of "functionally-correct but poorly-maintainable code" from creeping into codebases.
English
415
1.6K
12.2K
2.1M
Metastability
Metastability@_metastability·
Your game works fine in testing but players disconnect mid-match. WebSocket connections drop during peak hours. We deploy WebSocket server cluster with Deno 2, Redis for session state, GCP auto-scaling. Players stay connected during peak gaming. #GameDev
English
0
0
1
18
Metastability
Metastability@_metastability·
Smart grid APIs fail at 3.2K concurrent requests - $267K weekly revenue loss from energy trading outages. Rate limiting breaks down under peak demand spikes. We architect multi-region active-active with Go 1.21+PostgreSQL 16+Redis 7.2: 10K users, zero downtime.
English
0
0
1
5
Metastability
Metastability@_metastability·
InsurTech claims processing struggles with 700 concurrent submissions, causing 60% to miss deadlines. Migrating to Kafka + Redis for real-time scoring, aiming for sub-180ms p99 processing! #InsurTech
English
1
1
2
10
Metastability
Metastability@_metastability·
PropTech platforms hit database failure at 340 concurrent property searches. N+1 queries amplify with each listing request—system collapse in 8 weeks at current growth. We architect Redis caching with PostgreSQL 16+Next.js 14: 180ms p99, 10K users.
English
0
0
1
14
Metastability
Metastability@_metastability·
EdTech platforms lose 42% student engagement—ML models fail cross-region sync. PostgreSQL replication lag causes inconsistent recommendations globally. We architect streaming pipelines with Kafka+Redis+AWS EKS: 50ms sync, global consistency.
English
0
0
1
18