Insights
Practical writing on software architecture, SaaS products, AI automation, legacy modernisation, and the business of building reliable systems.
Curated links from external sources — not 360Softy original articles.
Most Flutter tutorials show you how to build a todo app. This is not that. Flutter (Dart) — cross-platform mobile Why MercadoPago and not Stripe? Flutter devs building for the Latin American market Get it [email protected]
*This is a submission for the [Hermes Agent Challenge] Hermes Commander is my first AI agent project built using Hermes Agent. The goal of this project was to explore how an AI agent can go beyond simple question-answering and perform structured tasks using tools. Hermes Commander acts as an autonomous research assistant that can understand requests, create research plans, access available tools, and organize workflows. As someone interested in AI, prompt engineering, and research, I wanted to b
I built a self-improving and healing workflow for Antigravity 2.0 where your AI review prompts update themselves based on your actual codebase. No more stale checklists that still reference packages you removed months ago. The core idea: meta-prompts — instructions that tell the AI to scan your package.json, GEMINI.md, skills, and MCP config, then generate hyper-specific review prompts from scratch. Every time. What's in the repo: 🧠 Self-optimizing prompts for code review, spring cleaning, and
How I built a real-time serverless security detection pipeline on AWS using CloudTrail, EventBridge, Lambda, DynamoDB, and SNS — and what broke along the way. All source code for this project is on GitHub: aws-siem-detection-pipeline Most cloud security tutorials show you how to turn on GuardDuty and call it a day. I wanted to better understand what actually happens under the hood. Things like how a detection pipeline routes an event, evaluates it, and fires an alert in real time? So I built one
Most developers using AI coding tools hit the same ceiling eventually. The agent writes code, you accept or reject it, and next time it starts from scratch again. There's no memory of what worked, no accumulated judgment about your codebase, no improvement from one session to the next. You're getting faster, but the tool isn't getting better at helping you specifically. Compound Engineering is a plugin that tries to fix that. Built by Every.to and available for Claude Code, Cursor, Codex, GitHub
"50 resumes. Same 5 mistakes. Over and over. Nobody told these developers what was wrong. Until now." A few weeks ago I posted in a developer community — 👇 "Drop your resume link — I'll give honest feedback." I expected maybe 10-15 responses. 50 developers sent their resumes. 😳 Freshers. Career switchers. Developers with 1-2 years of experience. All struggling to get callbacks. I read every single one. Gave feedback on every single one. And here's what shocked me — the same 5 mistakes appeared
Your SPF record looks correct. You added the include values your email provider told you to add. You saved the record. Emails are still landing in spam. The problem is almost certainly one of five things — and four of them are invisible in your DNS provider's interface. You cannot tell by looking at the record whether you have exceeded the 10-lookup limit. You cannot tell from a browser whether your propagation has completed. You cannot see from the dashboard that a second SPF record was created
Comments
Work with 360Softy
Book a free consultation and we will tell you honestly whether we can help.
