今日已更新 151 条资讯 | 累计 39680 条内容
关于我们

标签:#t

找到 18906 篇相关文章

AI 资讯

How I Built BidXpert — A Real-Time Auction Platform with FastAPI

Hi, I'm Heet Sanghani, a Python Developer and AI/ML Engineer from Ahmedabad, Gujarat, India. I currently work at BrainerHub Solutions building backend systems and AI-powered applications. In this post, I want to share how I built BidXpert — a real-time auction platform using FastAPI. What is BidXpert? BidXpert is a real-time bidding platform where users can create auctions, place bids, and get instant updates using WebSockets. Tech Stack Backend: FastAPI + Python Database: PostgreSQL Real-time: WebSockets Auth: JWT Authentication Deployment: Docker What I Learned Building BidXpert taught me how to handle concurrent WebSocket connections efficiently in FastAPI and manage real-time state. About Me I'm Heet Sanghani — Python Developer & AI/ML Engineer based in Ahmedabad. Check out my portfolio and other projects at: 👉 https://heet-sanghani-portfolio.vercel.app/ python #fastapi #webdev #ai

2026-06-02 原文 →
AI 资讯

Hot take: "real-time" inventory sync is the biggest lie in ecommerce tooling

Every inventory tool says real-time. Every single one. Open the settings. Find the sync frequency configuration. It says 15 minutes. Or 10. Or 30 on the cheaper plan. That's not real-time. That's a cron job. There's a meaningful architectural difference and the industry has collectively decided to pretend there isn't. I want to make the technical case for why this matters — and ask why so few tools have actually fixed it. What "real-time" actually means technically Real-time in distributed systems has a specific meaning. It means the system responds to events within a bounded, predictable latency — not on a schedule. javascript// This is NOT real-time — this is scheduled // Latency: up to 15 minutes (the full interval) setInterval(async () => { const stock = await getSourceOfTruth(); await syncToAllChannels(stock); }, 15 * 60 * 1000); // This IS real-time — event-driven // Latency: network round-trip (~milliseconds) orderEventBus.on('order.confirmed', async (event) => { const updated = await decrementStock(event.sku, event.qty); await propagateToAllChannels(updated); }); The first example responds to state changes on a schedule. The second responds to events as they happen. These are fundamentally different architectures with fundamentally different latency guarantees. Calling the first one "real-time" is technically incorrect. It's scheduled sync. The schedule is just short enough that most users don't notice — until they do. When users notice The failure mode is predictable and well documented: javascript// Flash sale scenario — 10x normal velocity const normalOrdersPerWindow = 500 / ((24 * 60) / 15); // ~5.2 const flashSaleOrdersPerWindow = normalOrdersPerWindow * 10; // ~52 // 52 orders processed against potentially stale stock // per 15-minute window // across multiple channels simultaneously // none of which know what the others have sold 52 orders per window. At 2% oversell rate — just over 1 oversell per window. Across 96 windows per day — nearly 100 oversel

2026-06-02 原文 →
AI 资讯

AI directly in DRAM: The Float Detox – How Pure Logic Unleashes the Future of Learning

Float32 was the true enemy – not backpropagation, not the architecture. BIN16 replaces every floating-point operation with a single boolean operation: popcount16(XNOR16(a,b)). The result: 82 % MNIST at H=512 with zero floats, zero gradients, zero AdamW and zero learning rate tuning. The training converges immediately in epoch 1 – without warm-up, without decay, without hyperparameter search. Both layers use identical XNOR+popcount operations – training and inference run directly in off-the-shelf DRAM with only 5 transistors per cell. This is the only neural architecture where the same hardware performs both training and inference without modification. The remaining 18 % to 100 % is the bit-mass limit – no training deficit. The groundbreaking insight came when we stopped fighting against float and embraced pure boolean computation. Every complexity – AdamW, backprop, LR schedules, BLAS – dissolved as soon as we removed floating-point numbers from the architecture. Three groundbreaking insights changed everything. Float was the true enemy: backpropagation, AdamW or momentum were never the problem. Float32 introduced numerical noise and instability. Bitwise centroids converge instantly: a running bitwise majority vote per class reaches final accuracy in a single epoch. Random projection is entirely sufficient: W0 does not need to be trained – a random boolean projection provides adequate separation. The entire training consists of only four steps and 220 lines of C – without learning rate, without GPU, without any conventional optimization. This architecture opens the door to a future in which neural networks compute directly in memory. No more expensive GPUs, no endless hyperparameter tuning marathons. Instead, pure, efficient logic that is ready for use immediately and everywhere. Imagine: AI systems that train and infer in off-the-shelf DRAM – energy-efficient, lightning-fast and accessible to everyone. BIN16 is the first step into this new era. Identical operations

2026-06-02 原文 →
AI 资讯

The Download: AI can run your admin department now

This is today’s edition of The Download, our weekday newsletter that provides a daily dose of what’s going on in the world of technology. How small businesses can leverage AI From accounting to design to market research and product development, there’s a staggering breadth of skills needed to run a business. Large companies can hire…

2026-06-02 原文 →
AI 资讯

Why is tool access in a multi agent system so hard to manage without conflicts?

We ran into something that didn't seem like a problem until it was. Each agent had access to the tools it needed and everything worked fine in isolation. The issues started once agents were running in parallel. Two parts of the system would try to use the same tool or hit the same resource at the same time. Results became inconsistent and it wasn't obvious why. Limiting access helped in some cases but slowed things down elsewhere. Too much access caused race conditions. Too little caused steps to stall waiting for something to free up. Most of the coordination logic ended up sitting outside the agents themselves. Every new agent added more decisions around what it should be allowed to access and when. There isn't a shared way to manage tool access across a multi agent system. How are you handling this when multiple agents are running at the same time? submitted by /u/Logical-Bite-4221 [link] [留言]

2026-06-02 原文 →
AI 资讯

People are leaving a lot of weird stuff in their robotaxis

A unicorn Beanie Baby. A 15-pound green bowling ball. A pair of dentures. These are just some of the items left behind in robotaxis in the past year, according to Uber's annual Lost and Found Index. For the first time, the company is expanding its annual of accounting of things forgotten in Uber vehicles to […]

2026-06-02 原文 →
AI 资讯

Rehumanizing global health care with agentic AI

The global health care sector is under increasing strain. Decades of chronic underinvestment and constraints in recruitment have coincided with a surge in demand for services for aging populations. Gaps in provision are already taking a toll, with fragmented access to care and high rates of stress and burnout among staff. And it’s getting worse.…

2026-06-02 原文 →
AI 资讯

The Intersection of Encryption and AI

As part of their 20th Anniversary celebration, Dark Reading asked five cybersecurity industry leaders who wrote blogs or columns for them over the years to select their favorite piece and share their reflections on the topic today. This is my section. Renowned technologist and author Bruce Schneier contributed a column on June 20, 2010, warning about cryptography’s inability to secure modern networks , a point he says he has been trying to argue since 2000. “For a while now, I’ve pointed out that cryptography is singularly ill-suited to solve the major network security problems of today: denial-of-service attacks, website defacement, theft of credit card numbers, identity theft, viruses and worms, DNS attacks, network penetration, and so on...

2026-06-02 原文 →
AI 资讯

Microsoft Threatening Security Researcher

An anonymous security researcher called “Nightmare Eclipse” has been publishing a series of significant security exploits against Microsoft Windows—including one that breaks BitLocker. Microsoft has threatened legal action against the researcher. Lots of recriminations are being traded back and forth.

2026-06-02 原文 →
开发者

How to watch Microsoft’s Build 2026 conference

Microsoft is kicking off its yearly Build developer conference in San Francisco today, sandwiched between the recent Google I/O and Apple's upcoming WWDC event. While tickets to attend Build in person are sold out, the conference is being streamed for free online, with CEO Satya Nadella opening with a keynote at 12:30PM ET / 9:30AM […]

2026-06-02 原文 →