|
NVIDIA Research Advances Robotics From Simulation to the Real World
-
blogs.nvidia.com
-
1 week ago
-
eng
Robotics is entering a new phase: moving from controlled demos and scripted automation toward generalizable, reliable embodied autonomy in the real world. At the International Conference on Robotics and Automation (ICRA), eight of NVIDIA Research’s 28 accepted papers show how simulation-to-real transfer is becoming a foundation for that shift, helping robots perceive, reason, plan and […]
|
|
The Name’s Gaming … Cloud Gaming: ‘007 First Light’ Launches on GeForce NOW
-
blogs.nvidia.com
-
1 week ago
-
eng
License to stream, shaken and stirred. GeForce NOW is dialing up the espionage with the launch of 007 First Light, letting members slip into James Bond’s reimagined origin story from almost any device — no tux or preloads required. For a limited time, the game is included with the purchase of a 12‑month GeForce NOW […]
|
|
Switch from Gmail to Proton Mail and send and receive emails in one place. No more toggling between inboxes.
|
|
以前只记得要支持websocket 需要 nginx 改： location /ws-service-a { proxy_pass http://backend_a; proxy_http_version 1.1; proxy_set_header Upgrade $http_upgrade; proxy_set_header Connection $connection_upgrade; } 今天折腾忘记这茬了，一直在调 FastAPI ，@app.websocket() 死活不识别 wscat 的请求 WebSocket 协议的工作方式是： 1.客户端发 GET + Upgrade: websocket 头 2.服务端识别这个特殊 GET，返回 101 Switching Protocols 3.连接升级完成 opus-4.6 说：既然路由确实注册了，那问题几乎可以确定是：前面的反向代理/LB 没有透传 WebSocket 我就....
|
|
Learn how to use Claude Code Agent Teams and TimescaleDB to build a unified plant-floor data pipeline — one governed table, three protocols, zero middleware.
|
|
Today we're starting AirVPN 16th Birthday celebrations with big discounts on longer term plans. From a two servers service located in a single country providing a handful of Mbit/s, the baby has grown up to a wide infrastructure in 23 countries on four continents! AirVPN is now one of the few major consumer VPNs that is still independent. In other words, it is not owned by large corporations with diverse interests that interfere through e....
|
|
Career frameworks describe outcomes, not behaviors; interviewers collect impressions, not evidence. Here's how to fix both.
|
|
AI didn't break pull requests; it exposed the review queues, slow integration, and weak collaboration habits engineering teams already had.
|
|
Engineering Burnout Has Five Faces, and Your Career Ladder Walks You Through All of Them
-
leadership.garden
-
1 week ago
-
eng
Burnout has a different shape at every rung of the engineering ladder, and promotion doesn't cure it: it just trades one variant for another.
|
|
AI is cutting junior hiring. But the engineers that won't exist in 10 years are being decided right now. Here's what I think actually happens next.
|
|
Your team is not a school. You are not a teacher. The studio model is what actually grows engineers, and most of us are running classrooms.
|
|
Most 360 feedback fails not because leaders don't try to change, but because changed behavior doesn't automatically update other people's mental models.
|
|
AI doesn't care about quality. It accelerates whatever direction your team was already heading. Here's what engineering leaders need to change.
|
|
Verification debt is accumulating quietly in AI-assisted codebases. What engineering leaders need to watch for.
|
|
There is no standard Engineering Manager role. The job is defined by your team's biggest bottleneck - and it shifts constantly. Here's what that actually looks like.
|
|
The finger is not the moon. A guide for engineering leaders on recognizing when your ceremonies, OKRs, and 1:1s have become performance instead of practice.
|
|
When your engineering team grows past 15-20, what breaks first isn't documentation. It's that you were the routing layer and nobody knew it.
|
|
Why refusing to estimate doesn't solve your team's coordination problems - and what to do instead. For engineering leaders who are tired of broken planning.
|
|
Your Jira board shows process bottlenecks. It won't show you the approval chains, implicit rules, and leadership behaviors killing your team's throughput.
|
|
Most engineering managers coach too much, not too little, and they often do it for themselves, not their reports. Here's when managing is the more generous act.
|
|
Most software engineering teams swing between chaos and bureaucracy. Here's a framework to find the edge where scaling actually happens.
|
|
AI agents generate 98% more PRs but reviews take 91% longer. The work didn't disappear — it moved. A synthesis of eight perspectives on where it actually went.
|
|
Why do we assume everyone agrees with us? A deep dive into the False Consensus Effect, the Availability Heuristic, and how to fix cognitive bias in tech leadership.
|
|
Stop fighting the rumor mill and start using it. Learn why talking behind your team's back can be a good way to build trust and morale.
|
|
Learn the science behind developer flow states and implement practical strategies to increase your engineering team's focus, productivity, and satisfaction.
|
|
Engineering isn’t a meritocracy - it’s political. Learn how to navigate organizational dynamics, build influence, and ensure your technical ideas get heard and implemented.
|
|
An overview of the recurring laws and constraints that shape software engineering, from teams and estimation to architecture, testing, and performance.
|
|
The software engineering laws that govern code quality, complexity, and the tradeoffs of day-to-day development.
|
|
The UX and design laws that explain how people actually use software and why intuitive products follow recognizable patterns.
|
|
The human-side laws of software work: motivation, cognition, communication, and the habits that shape team behavior.
|
|
The laws that explain why metrics get gamed, what monitoring is actually for, and how to measure without self-deception.
|
|
The performance laws that explain bottlenecks, scaling limits, and why more hardware is not a strategy.
|
|
Why do software projects fail? Learn the unwritten laws of product development to avoid common pitfalls, diagnose issues, and build more successful products.
|
|
The testing laws that explain why quality is never finished, coverage is never complete, and tradeoffs matter.
|
|
The engineering laws that make risk and security inevitable design concerns, not compliance afterthoughts.
|
|
The laws that explain how systems evolve, why architecture drifts, and what makes technical structures hold up over time.
|
|
The laws behind software estimation, uncertainty, and why deadlines slip even when teams are trying to plan honestly.
|
|
Tech leaders: Build an environment where engineering teams can experiment freely, driven by clear intent and strong trust.
|
|
Cut through business jargon with 20 essential terms every engineering manager needs to understand to advocate effectively for their team.
|