Tweet fijado
Maluda | Fullstack Dev (React • Next.js • Node)
4.1K posts

Maluda | Fullstack Dev (React • Next.js • Node)
@maludatechdev
Fullstack dev building clean, fast websites & mobile apps. I fix bugs, build APIs, ship dashboards and get sh*t done fast. DMs open for work.
100% open to remote roles Se unió Eylül 2024
47 Siguiendo92 Seguidores

@maludatechdev Appreciate that 🙏
The initial focus is people who know the answer but temporarily lose access to structure under pressure.
Things like interviews, meetings, presentations, investor calls, and brain fog moments.
English

@Dillonlayson Please check your DM @Dillonlayson
English

Hiring Full Stack Developer🚨
Job:
FRONT END AND BACK END (UI/UX, the whole machine)
WEB BASED -> APP BASED BOTH ENDS.
Budget: 4-7k
**not hiring roles from India,Pakistan (apologies)**
#developer #webdev #hiring
#fullstackdev
#dev #css #coding
English

@LeeMazzone87 EchoMind sounds interesting, real-time support during live conversations is a genuinely hard
problem to solve well.
What's the primary use case you're targeting first?
Sales calls, support agents, something else?
English

@maludatechdev Nice to meet you let's connect,
Currently building EchoMind.
Upload context → Start conversation → Difficult question → Realtime support appears → You respond naturally.
Simple idea. Surprisingly common problem.
echo-clarity-site.lovable.app
English

That makes sense. Silent rewrites are dangerous
because the user loses trust the moment the system acts on outdated context without telling them.
The confirmation step is the right call, especially when the decision affects code output or architecture recommendations.
Are you building this as a standalone tool or
is it meant to sit inside existing IDEs like Cursor?
English

@maludatechdev Yeah, that is where it breaks. I do not want automatic superseding to silently rewrite memory. Better path is detect likely contradiction or staleness, lower confidence, then ask for confirmation when it would affect behavior.
English

@Slave2MyBeauty Are you open to working with remote developers?
I'm a Fullstack Developer with experience in Next.js, React, TypeScript, Node.js, PostgreSQL and React Native. I'd be happy to share my portfolio if remote collaboration is an option.
English

@codespicious Definitely, already followed back.
English

@7xuanlux The staleness problem is interesting,
how do you handle detecting when a decision
has been superseded without the user
explicitly flagging it?
Feels like that's where most memory systems
quietly break down.
English

@maludatechdev Mostly hybrid. Embeddings help with recall, but I don’t want Origin to become just vector search. The harder part is capture quality, confirmation, staleness, and building a small context packet instead of dumping everything back into the model.
English

@ccodyy69 Real ones know that Next.js >>>>
English

@raulinvests Highly interested @raulinvests
Portfolio: maluda.vercel.app
GitHub: github.com/maludatech
English

@buildwithkiro Sure, man. Follow back.
English

@bachelord001 Sure! Follow back
English

@Abhishe35257568 Sure, follow back.
English

@GoldilocksOrbit Think you replied the wrong tweet, bro.
English

@maludatechdev that's a bold claim on returns. tracking live premiums and using AI for analysis could definitely add some clarity. just curious how you handle the risk side of that strategy.
English

@_Rhand69 It’s all good, my bro.
Followed back already.
English

@_Rhand69 You never followed to begin with😒
English
Maluda | Fullstack Dev (React • Next.js • Node) retuiteado

@7xuanlux That's actually a problem I deal with constantly re-explaining context every session gets old fast.
How are you building the memory layer?
Vector embeddings or something else?
Always curious about the technical approach
behind tools like this.
English

@maludatechdev At a high level, Origin is local memory for AI agents. The goal is that Claude, Codex, Cursor, etc remember your project decisions without you re-explaining them every session.
English











