AI can generate a thousand articles a minute. But it can't do your thinking for you. Hashnode is a community of builders, engineers, and tech leaders who blog to sharpen their ideas, share what they've learned, and grow alongside people who care about the craft.
Your blog is your reputation — start building it.
1h ago · 3 min read · In our last post, we looked at the stark reality of the modern threat landscape: legacy patch management cannot keep pace with machine-speed exploits. When a zero-day drops or a vendor delays a critic
Join discussion4h ago · 25 min read · Dart backend frameworks exist on a spectrum. At the minimal end sits Shelf, with raw primitives and full control. You wire everything yourself. At the maximal end sits Serverpod. It's a full framework
Join discussion
5h ago · 6 min read · The first three phases of my study system handled the session loop: generate a problem, grade the solution, log the result. Useful, but with a fundamental gap — there was no memory of what I struggled
Join discussion6h ago · 8 min read · When I started building a real-time application, I thought the hardest part would be designing the features. Things like: Live notifications Real-time dashboards Presence indicators Collaborative
Join discussion
8h ago · 7 min read · A quick introduction to Go types According to https://go.dev/ref/spec#Types, in Go, a type specifies a set of values, along with operations and methods specific to those values. This is something fund
Join discussion
Exploring technology, business trends, digital innovation and practical insights.
1 post this monthFull Stack Developer & ML Researcher | Built govt & NGO systems @FAITE | MERN · Laravel · FastAPI · Python | BSc Software Engineering @SLIIT
1 post this monthAI-Powered Analytics: Turning Complex Business data into Decisions
1 post this monthExploring technology, business trends, digital innovation and practical insights.
1 post this monthFull Stack Developer & ML Researcher | Built govt & NGO systems @FAITE | MERN · Laravel · FastAPI · Python | BSc Software Engineering @SLIIT
1 post this monthAI-Powered Analytics: Turning Complex Business data into Decisions
1 post this monthThis was the first issue, the major issue I faced while migrating my Node.js codebse to Golang was during the implementation. I was tired googling "What is the best alternative of express package in Go?" and so on. It was never ending. searching for each package and then you see multiple results, filter them according to the reviews, github stars, stack overflow, etc. What if there was a tool who could do all this? Thats why I build PackagePal, It is a code migration assistant which suggest the best alternative of a package in target language. It helps developer with best alternative packag
Really enjoyed this walkthrough. Deploying multiple microservices to EKS is one of those things that sounds straightforward on paper, but in practice the number of moving parts can get messy very quickly. I like that you showed the process step by step instead of skipping straight to the “final architecture” part. What stood out to me most was how Docker Compose helped bridge the local development setup with the Kubernetes/EKS deployment flow. That transition is often where people get stuck, so this makes the whole journey feel a lot more approachable. I’m also working through
I like that this post doesn't turn it into a local-vs-cloud debate. They're really different stages of the same journey. Running Ollama locally is one of the fastest ways to understand what AI workloads actually cost in terms of memory, compute, and latency. A lot of those realities are hidden when you're only consuming APIs. What I've seen in practice is that local models are great for experimentation, internal tools, and privacy-sensitive workflows, while cloud infrastructure becomes important once reliability, concurrency, and operational support matter. Most teams will pro
Great explanation, especially the way the example shows how quickly things break once real usage increases. One thing I find interesting is how different apps handle that jump from small to real scale. A lot of it only becomes visible once people actually start using the product, not during initial development. I have been browsing a lot of these kinds of apps on https://unstore.io and it is interesting to see how different projects deal with scaling challenges in practice.
My takeaway: Angular provides a well-defined structure where both junior and senior developers can contribute using the same conventions. React offers more freedom, but that also means teams need stronger discipline to stay consistent. 🚀
Infrastructure is the engineering function startups defer most. Not the core product. Requires specific expertise. Competes directly with feature time. In 2026, Dockerfiles, Helm charts, and Kubernete
The point about building Kubernetes readiness into the codebase from the start rather than treating it as a panic migration project is exact...
This resonates from a non-technical perspective too. As someone in marketing at a tech company, I've seen firsthand what happens when infras...