---
title: "kramgyorgy (@gyorgy) | Hashnode"
description: "Infrastructure as Framework for TypeScript microservices. Read the latest articles by kramgyorgy on Hashnode."
url: "https://hashnode.com/@gyorgy"
---

@gyorgy

# kramgyorgy

@gyorgy · Amsterdam, Netherlands · Joined April 2026

Infrastructure as Framework for TypeScript microservices.

### [Agent knowledge is a trigger problem, not a writing problem](https://tsdevstack.hashnode.dev/agent-knowledge-is-a-trigger-problem-not-a-writing-problem?utm_source=hashnode&utm_medium=feed)

I put everything an agent needs to work in my framework into an MCP resource. Conventions, workflows, which files are generated, where secrets come from. It was accurate, it was complete, and it was o

4 min read · [tsdevstack.hashnode.dev](https://tsdevstack.hashnode.dev/agent-knowledge-is-a-trigger-problem-not-a-writing-problem?utm_source=hashnode&utm_medium=feed)

[Aug 8](https://hashnode.com/posts/agent-knowledge-is-a-trigger-problem-not-a-writing-problem/6a76fcb3e60de820b3f2d472)

### [IaC, FdI, IaF: three ways a codebase becomes infrastructure](https://tsdevstack.hashnode.dev/iac-fdi-iaf-three-ways-a-codebase-becomes-infrastructure?utm_source=hashnode&utm_medium=feed)

Published June 17, 2026 by gyorgy Infrastructure used to be something you wrote separately from your application. Lately that boundary has been dissolving, and the vocabulary has not kept up. Three di

8 min read · [tsdevstack.hashnode.dev](https://tsdevstack.hashnode.dev/iac-fdi-iaf-three-ways-a-codebase-becomes-infrastructure?utm_source=hashnode&utm_medium=feed)

[Jun 13](https://hashnode.com/posts/iac-fdi-iaf-three-ways-a-codebase-becomes-infrastructure/6a2d2dd26951e2544fd79b2c)

### [Getting a production WAF out of Azure Front Door Standard](https://tsdevstack.hashnode.dev/getting-a-production-waf-out-of-azure-front-door-standard?utm_source=hashnode&utm_medium=feed)

Front Door Standard caps a WAF at 100 custom rules for $35 a month. What that covers, and when Premium's $330 tier earns the extra $295.

5 min read · [tsdevstack.hashnode.dev](https://tsdevstack.hashnode.dev/getting-a-production-waf-out-of-azure-front-door-standard?utm_source=hashnode&utm_medium=feed)

[3](https://hashnode.com/posts/getting-a-production-waf-out-of-azure-front-door-standard/6a2d2d40c0bc15d227c14213) [Jun 13](https://hashnode.com/posts/getting-a-production-waf-out-of-azure-front-door-standard/6a2d2d40c0bc15d227c14213)

### [Agentic loops don't fix lying agents](https://tsdevstack.hashnode.dev/agentic-loops-don-t-fix-lying-agents?utm_source=hashnode&utm_medium=feed)

Loop engineering is the current answer to unreliable coding agents. But a loop is only as good as its verifier, and I have the receipts for what slips through.

7 min read · [tsdevstack.hashnode.dev](https://tsdevstack.hashnode.dev/agentic-loops-don-t-fix-lying-agents?utm_source=hashnode&utm_medium=feed)

[Jun 12](https://hashnode.com/posts/agentic-loops-don-t-fix-lying-agents/6a2c20f74e433d40f174f92c)

### [Cloud Run private networking without a VPC Connector](https://tsdevstack.hashnode.dev/cloud-run-private-networking-without-a-vpc-connector?utm_source=hashnode&utm_medium=feed)

Tool annotations like readOnlyHint are server-declared hints, not enforcement. Treating them as permissions is a category error the spec warns against

8 min read · [tsdevstack.hashnode.dev](https://tsdevstack.hashnode.dev/cloud-run-private-networking-without-a-vpc-connector?utm_source=hashnode&utm_medium=feed)

[May 13](https://hashnode.com/posts/cloud-run-private-networking-without-a-vpc-connector/6a042ef652a9c969d61d19eb)
