Insights
Ideas for building
better software.
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.
Run a Chatgpt-like Chatbot on a Single GPU with ROCm
Introducing RWKV - An RNN with the advantages of a transformer
Automatic recursion protection for Vercel Functions
Vercel now has automatic recursion protection for Vercel Functions. This provides safety against your code inadvertently triggering itself repeatedly, incurring unintentional usage. Recursion protection supports using the module or in the Node.js runtime for Serverless Functions, both for user-defined code and dependencies. Requests using the bare constructor are not protected against recursion.httpfetchSocket Recursion protection is available free on all plans. It does not require any code c
Assisted Generation: a new direction toward low-latency text generation
Announcing Vue 3.3
Today we're excited to announce the release of Vue 3.3 "Rurouni Kenshin"! This release is focused on developer experience improvements - in particular, SFC <script setup> usage with TypeScript. Together with the 1.6 release of Vue Language Tools (previously known as Volar), we have resolved many long-standing pain points when using Vue with TypeScript. This post provides an overview of the highlighted features in 3.3. For the full list of changes, please consult the full changelog on GitHub.
What does Vercel do?
Vercel builds a product—they make it easy for engineers to deploy and run the user facing parts of their applications.frontend-as-a-service Read more
Backward compatible database changes
A common question I often hear is, “Should I make my application code changes before, after, or at the same time as my database schema changes?” The reality is that neither our application nor database live in a bubble. In almost every case, you should never couple your database schema and application code changes together. While shipping them simultaneously might seem like a great idea, it often leads to pain for you and your users. There are five main reasons for this: Risk: By deploying chang
Let’s start with a conversation
Tell us what you’re working on.
An idea, a challenge, or a system that needs to work better. We’ll help you understand the next step.
Prefer email? [email protected]
