Skip to content
360SOFTY
HomeInsights

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.

ExternalSoftware Engineering
DEV Community

I spent 10 years building enterprise search for clients. Then I open-sourced all of it.

Every enterprise search project I did in the last decade ended the same way. A search engine (Solr or Elasticsearch), a pile of glue code for facets and relevance, then, in recent years, a RAG pipeline bolted on the side, and finally an agent framework on top of that. Three stacks, three sets of bugs, one recurring client requirement: the data cannot leave our network. After repeating that build enough times, I turned it into a single platform. This year I open-sourced the whole thing under Apac

opensourceairag
DEV CommunityRead original
ExternalSoftware Engineering
DEV Community

Construindo uma plataforma GitOps do zero: Kubernetes, ArgoCD, Terraform e Observabilidade

Durante muito tempo, meu contato com Kubernetes foi do tipo "já mexi": subi um pod aqui, apliquei um manifesto ali, vi um deploy acontecer. Mas existe uma distância enorme entre usar uma ferramenta e entender o que ela faz por baixo. Eu venho de backend Java e automação de testes, e decidi atravessar essa distância de propósito construindo, do zero, uma plataforma GitOps completa e local. Este artigo é o registro dessa construção. Não é um tutorial de "cole esse comando"; é uma explicação de por

kubernetesdevopsgitops
DEV CommunityRead original
ExternalSoftware Engineering
DEV Community

Workflow JSON Is Generated Code

A screen recording can show a whole job without explaining it. Someone opens an inbox, checks a sender, copies a value into a customer record, compares it with a spreadsheet, sends a summary, and moves on. That work is visible, but automation still has to survive a harder test: can the system rebuild the job without dropping a step, wiring the wrong action, or importing something that looks right and fails later? I built the n8n side of the screen-analysis project around that problem. The genera

n8nworkflowautomationcodegeneration
DEV CommunityRead original
ExternalSoftware Engineering
DEV Community

6 AI Gateways Compared for 2026: Routing, Governance, Caching, and Observability

TL;DR An AI gateway is one control plane for every LLM request your application makes, regardless of which provider serves it. Without one, the pieces scatter: provider keys in one place, rate limits in another, caching somewhere else, and separate homes for permissions, spend reporting, and logs. That sprawl gets harder to govern with every new service that starts calling a model. The things worth evaluating are fairly concrete — does it consolidate provider access, cap spend, deduplicate cal

aillmmonitoring
DEV CommunityRead original
ExternalSoftware Engineering
DEV Community

AI Can Write Code. But Are You Really a Software Engineer?

AI Can Write Code. But Are You Really a Software Engineer? "The question isn't whether AI wrote your code. The question is whether you could have built, debugged, and defended it without AI." This isn't an anti-AI article. I use AI. Professional engineers use AI. The world's best engineering teams use AI. The problem isn't AI. The problem is confusing AI-assisted coding with software engineering. Some of the best engineers I've worked with use AI every day—not because they can't code, but beca

discusscareerai
DEV CommunityRead original
ExternalSoftware Engineering
DEV Community

Before your DV team writes a single testbench line, make sure you have these 7 things. (Most teams skip at least 3.)

The Pre-Testbench Verification Checklist: ✅ 1. Spec version locked — Which version of the spec is RTL implementing? If it's not locked, you're verifying a moving target. ✅ 2. Interface list finalized — All clocks, resets, interfaces, and their reset polarity documented. Surprises here cost days. ✅ 3. Functional coverage model drafted — Write your covergroups before writing your driver. Coverage-first design. ✅ 4. Corner cases listed explicitly — Max burst, min burst, back-to-back, simultaneous r

DEV CommunityRead original

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.

Discuss your project

Prefer email? [email protected]