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.
Prisma vs Vercel compared for TypeScript apps: what each platform provisions and checks for you, preview databases, migrations, runtime limits, and pricing.
If a data agent returns €18.6M, production observability should tell you exactly how that answer was constructed. Most Text-to-SQL pipelines log prompts, generated SQL, latency, tokens, and execution status. Those signals matter, but when a business user says, “This number is wrong,” they are not enough. The failure may have happened before SQL generation: "Revenue" → wrong metric "Germany" → wrong dimension Customer data → wrong relationship path "Last quarter" → wrong time interpret
Poll data released Tuesday by the New York Times and Siena University confirms what we've already been seeing, and what politicians are responding to - AI and data centers are incredibly unpopular. Asked if they support or oppose the construction of data centers to power AI tech, 61 percent of the 1,503 likely voters surveyed in early September (ahead of the recent AI safety slowdown discussion) said they were opposed, with only 14 percent saying they strongly support. The split was about even a
There is a complaint that sounds like nostalgia but usually isn’t: “it used to be better than this.” Last week we listened to paying users ask what their money still buys — a story about price, ads and upsell. This week the sum people are doing is different, and quieter. Not “what does it cost” but “what does it still do.” Across the busiest AI forums, the through-line was a felt sense that the tools they already pay for are being hollowed out from the inside: shorter answers, tighter limits, a
TL;DR: For Node.js event notifications, send transactional email first, poll its delivery status, and use SMS fallback only while the password-reset token remains useful. The deciding constraint is the expiry clock: a late fallback can create noise without helping a locked-out customer. For a customer-support system, this is a reliability problem with a security boundary. The useful outcome is not “an API accepted a request.” It is a reset message that is observable, bounded by its expiry, and s
While reading through some ai-generated code today, I was caught off guard when I saw a switch statement inside of a boolean. What on earth has ai done now, I wondered. Here is the suspect: public boolean canChangeTo(OrderStatus newStatus) { switch (this) { case PLACED: return newStatus == PROCESSING || newStatus == CANCELLED; case PROCESSING: return newStatus == SHIPPED || newStatus == CANCELLED; case SHIPPED:
Domain Excavation Because it requires constant discovery and refinement, building software is much like excavating a buried house. One requirement exposes a section of wall. A bug fix reveals a doorway we hadn’t accounted for. A conversation with a user turns up a hearth or a pottery shard. Gradually, the pieces begin to suggest architectural features yet to be discovered: rooms, connections, and the activities they supported. Recognizing the architectural whole changes how we understand the p
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]
