Andrei
120 posts

Andrei retweetledi

stop overthinking, start building:
the best way to predict the future is to invent it. and the best way to invent is to start building.
you can dream all you want. you can think in abstract, map out perfect systems in your head, debate the ideal architecture. but none of that matters until you start making something real.
building is like mounding clay. you don't start with the perfect form. you start with a lump. you push, you shape, you feel the resistance. the material talks back. it tells you what works and what doesn't. you learn by doing, not by thinking about doing.
with Cursor, the gap between idea and reality is basically zero now. you don't need to know every syntax, every framework, every pattern. you just need to start. Cursor helps you shape the clay. it fills in the gaps. it lets you focus on what you're making, not how to make it.
overthinking is just fear dressed up as preparation. you're not getting ready, you're just delaying. the longer you wait, the more you convince yourself it needs to be perfect before you start. but perfect doesn't exist at the beginning. it only emerges through iteration.
every great thing you've ever seen started as something rough. the first iPhone was a prototype held together with tape. the first Notion was a clunky tool that barely worked. the first anything was messy. but it existed. and because it existed, it could be improved.
so stop planning the perfect app. stop debating the right tech stack. stop waiting for the right moment. just open Cursor and start building. make something bad. make something that barely works. then make it better. then make it better again.
the future isn't something you think your way into. it's something you build your way into. one line of code at a time. one iteration at a time. like mounding clay until something beautiful emerges.
start today. start now. start messy. just start.
English
Andrei retweetledi

the uncanny valley of creation
you ship your mvp, get some users, maybe even hit some early metrics – and think you're done. but you're actually in the most dangerous spot possible.
that first version works but it's not good yet. it's functional but clunky. users try it but don't stick. you're in this weird limbo between "it works" and "people actually want this" – that's the valley.
most people stop here because going deeper feels uncertain. the feedback is mixed, the paths forward are many, and honestly it's just hard work. but this is exactly where you need to double down.
pmf isn't just finding users who'll use your thing – it's making something so good they can't imagine living without it. that happens in the details. in how every interaction feels, how the whole experience flows, how it just works the way they expect.
the thing about mvps is they get you to the starting line, not the finish line. excellence lives in iteration after iteration after iteration. going deeper into every level – the copy, the transitions, the edge cases, the moments of delight that make people smile.
when you know something needs to exist, you don't need to doubt every decision. you just keep iterating toward that future vision while solving the concrete thing right in front of you. the path becomes clearer as you walk it.
the hardest part is holding both the big vision and the tiny details at the same time. but that's what separates good from greatness. many builders give up in the valley between "it works" and "it's magical" – but that's exactly where the magic happens.
English

@useenclave @fireplacegg Oh, nice approach. If you isolate it just for this type of function “claimRewards” (e.g) and you add a relayer that not only uses that session key to sign the user’s transaction, but also wraps it in another transaction to cover the fee for them, then yeah, sounds cool to me👌🏻
English

@andreichirita_ @fireplacegg session keys with limited permissions :)
English
Andrei retweetledi
Andrei retweetledi

Just posted a draft for the Supernova proposal on the Agora.
Please note there are other improvements left out from this proposal, so we can speed up going on mainnet (those can come in a subsequent release/patch).
Let's continue the discussion here:
agora.multiversx.com/t/mip-27-super…
English
Andrei retweetledi

complexity first, simplicity second
people say “keep it simple,” but most approach it backwards. they start from simple, then add on complexity without seeing the whole. that’s how you end up with frankenstein products: clean-looking components awkwardly stitched together, held in place by duct tape and wishful thinking.
true simplicity emerges only after you’ve grasped the full complexity first. you can’t abstract away what you don’t fully comprehend. once you deeply understand the entire system — the edge cases, feedback loops, emergent behaviors — then the elegant patterns start to surface, creating solutions that genuinely click.
people often misunderstand complexity as the enemy of simplicity. but complexity isn’t the enemy, it’s reality. your goal isn’t to ignore complexity, but to master it. when you think holistically, you create systems whose parts reinforce each other rather than clash. the UI naturally mirrors the underlying data model. the API aligns seamlessly with how users think. the entire product feels inevitable.
real builders dive into the messy reality and embrace it. they map out the bizarre edge cases, user mental models, technical constraints, and business pressures. they sit patiently with complexity until the right patterns emerge. only then do they craft the simple, intuitive interface that makes all that complexity invisible. it’s like a swan, serene on the surface but paddling like hell beneath.
this is why Notion succeeds where most productivity apps fail. we didn’t start by saying, “let’s build a simple notes app.” we asked, “how would people organize and share information, with the fewest primitives” then we built abstractions that aligned with those conceptual models.
systems thinking is essential because it’s the only path to building products that scale — not just technically, but cognitively. users shouldn’t need to grasp your internal complexities to extract value. that’s the paradox: the more deeply you embrace complexity in your thinking, the simpler the experience becomes.
English

