Coming bright up
Get ready for a week of technology, creativity, and community — all online and free. Here’s what WWDC26 has in store. Learn more
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.
Get ready for a week of technology, creativity, and community — all online and free. Here’s what WWDC26 has in store. Learn more
Every engineering team I talk to has the same problem. When a P1 fires, coding stops. An engineer gets pulled in, spends 30 to 60 minutes hunting through logs, tracing requests across three or four systems, and cross-referencing deployment history before they can even form a hypothesis about what broke. By the time they have a diagnosis, they've already burned the better part of their morning. We've normalized this. It's just become part of the job. But the math is brutal: A team handling 50 inc
If you have been building anything non-trivial with Genkit, you have probably bumped into the same set of cross-cutting concerns over and over again: retrying transient model errors, falling back to a cheaper model when quota explodes, gating tool execution behind human approval, injecting filesystem access for coding agents, logging every request and response for observability... Until now, you ended up either wrapping ai.generate() calls by hand or writing ad-hoc helpers that ended up duplicat
Frontend Nation 2026 is back June 3-4 as a free, two-day online event covering web development and AI. Laravel is named in the framework lineup, with Pascal Baljet, Steve McDougall, and Vishal Rajpurohit among the speakers. The post Frontend Nation 2026 Returns June 3-4 with Laravel in the Lineup appeared first on Laravel News. Join the Laravel Newsletter to get Laravel articles like this directly in your inbox.
Comments
Monday opens with a trust problem. A mail server flaw is under active use. A network control system was targeted. Trusted packages were poisoned. A fake model page pushed a stealer. Then came the familiar ransom claim: the data was returned and deleted. The pattern is clear. One weak dependency can leak keys. One leaked key can open cloud access. One cloud foothold can become a production
This is Part 1 of a two-part series about cross-document view transitions, going over all the gotchas, from ditching the deprecated way to opt into them to a little-known 4-second timeout. Cross-Document View Transitions: The Gotchas Nobody Mentions originally handwritten and published with love on CSS-Tricks. You should really get the newsletter as well.
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]