Daniel

🚀 I build and share projects in AI and automation. Right now, I’m exploring how to make APIs more visible to AI models. Follow for the wins, pivots, and lessons from building in public.

@naturedotcom Yeah, you must leverage AI to save you time and money

Am I just wasting my time by avoiding AI while building projects?

@amooh001 What do you mean with stay present on timelines?

Build your X account 🗣️💰 Reply to people daily 🪄 Stay present on timelines 🪄 Become easier to notice 🪄 Gain daily 🤝

@Gavel_on_X Yeah watch out, X might find it suspicious

Start this day on X well 🫡 hello everyone! I try to follow everyone if X doesn't block me! 😅

@Heyyanyaa We already are mutuals, I'm here just to say Hi ☺️

IF YOU ARE STILL UNDER 5K FOLLOWERS Say hi Let’s be Mutuals 🙋‍♀️

@JoshuaUrasa2 Consistency is everything 💪

Good morning builders ☀️ Someone is quietly changing their life right now by: - learning - building - posting - improving - staying consistent Small daily actions compound harder than people think.

@Gavel_on_X I try to support as much as possible! ☺️

Do you support others on X with likes and comments or only think about yourself?

@vladsiu @X Backend engineer here! Let's connect 😁

Hey all - @X I'm looking to #connect with people interested in: - SaaS - Startup - Marketing Let's grow together 🤝

@Internethunts It's like competing with casinos, the house always wins

you can't compete with politicians in terms of money and power

MCP is the USB-C moment for agent-to-API communication. APIs that expose MCP interfaces get automatic tool discovery and standardized auth handling. No custom integration code. Single interface, universal compatibility.

MCP Apps launched in January. Nobody talking about it. MCP servers can now return interactive HTML in sandboxed iframes. Day-one partners: Figma, Slack, Asana, Box, Canva, Hex, monday.com. MCP becoming an application platform, not just a tool-integration protocol.

Good backend engineering is often just good data modeling. Once relationships are designed properly, many backend problems become simpler.

One phrase change can lift your API docs' LLM citation rate by 36%: "Requests might return 401" vs "Requests without valid tokens return 401 Unauthorized" Same information. Different confidence signal. LLMs treat definitive language as more authoritative.

@StevBuilds I just started, I would say idea and validation for now.

Where do you waste most of your time as a founder?

@JoshuaUrasa2 yeah... when I was a AuthN engineer, nobody thanked me for being able to login, but everyone complained when they couldn't...

@MnFounder 😂😂 backend and data engineers really live in the shadows People only notice when something breaks, not when insane architecture and optimization make everything feel instant.

@JoshuaUrasa2 bro... lets do it!

@MnFounder Same here 😄 Maybe one day we should even host our own Space and talk about backend architecture, system design, and real engineering decisions. Could be fun and useful for other builders too.

A lot of backend scalability issues start with database decisions made too early without thinking long term

I envy you bro... I would love to work with Golang. When I was at the university I learned about Golang and wanted to try it so much that I asked a teacher if I could do the thesis using Golang. He asked me if I knew the language and that it would be much simpler to do the project in python since there were already tested libraries for what I wanted to implement. I told him that I had never programed in Golang before, but I wanted to learn on the go. So I implemented the whole decision tree AI algorithm using Golang. It was beautiful (the language, not the decision tree)

Yeah 😂 I’ve worked with Spring Boot, Node.js/Express, and Django too, but these days I’m focusing more on Golang for backend systems and APIs because I really like the simplicity and performance side of it. Most of my current Go work is for my own projects though. At work we do more enterprise integration stuff using WSO2 and Apache Camel.

Yup... I am tired of this scenario: BE: Optimizes the shit out of a query using caching to make sure it is fast. FE: adds a button to call the endpoint we implemented in BE User: This button is amazing No one: The way they implemented this logic is insane. But even worst: Data engineers... These guys are never mentioned. Respect for them.

@MnFounder Backend engineers have been waiting for this moment for years 😂

@JoshuaUrasa2 I hope so! I love to have discussion partners 😄

@MnFounder 😂😂 fair enough Architecture discussions are honestly one of the best parts of backend engineering too. That’s where most of the long term scalability decisions are made before the code even exists. Looks like we’ll be having more architecture discussions from now on 😂

@JoshuaUrasa2 btw, you use Golang right? (saw in your profile)

@MnFounder Kotlin + Spring Boot + PostgreSQL + Redis + RabbitMQ… Yeah you’re deep in backend for real 😂

@JoshuaUrasa2 I used it on a AuthZ system. My team at the time compared several NoSQL DBs and ScyllaDB outperformed every one of them in every possible way, it was insane. It has a built-in cache that works like a charm.

@MnFounder Honestly PostgreSQL keeps proving why so many backend engineers trust it for serious systems 😂 And interesting point about ScyllaDB too, I’ve never used it before but now you’ve made me curious enough to try it and see how it performs compared to the usual setups.