flowty (@flowty) header
flowty (@flowty) profile picture

Don't forget to interpret things around you in your own way; avoid the mistake of letting yourself be shaped by someone else's perspective

Joined May 2024
My first conclusion in this journey of learning programming: I used to think programming was like playing with Lego: you take ready-made pieces of code, connect one to another, and voilà, it is done. But I am realizing that it is much more like writing a book while you are still discovering the story, or shaping clay that needs to hold itself together as a whole. You do not build only by looking backward. You build by looking forward. Before creating a class, a variable, a function, or any logic, you start thinking: “What will this need to do later?” “Where can this connect?” “What problem does this help me solve?” For me, this is one of the biggest challenges for a beginner: not studying tools as isolated things. When you learn something new, that knowledge starts as an isolated point. It is not exactly a skill yet. It is just a loose piece that you can forget very easily. The first thing you do is try to see possible paths for that point. It is as if it starts pulling magnetic lines toward other pieces of knowledge you already have. Some lines are weak, others seem to have more strength. Then you start testing, messing around, examining, using it in isolation, and trying to understand: “What does this mean for me when it comes to solving problems?” When you find a possible connection, that magnetic line starts becoming a thin line of clay. It already connects one thing to another, but it is still fragile. If you do not reinforce it, it breaks. If you do not practice it, it disappears. If you do not organize it, it becomes confusion. So you need to put more clay on that path. Test more. Relate more. Compare it with something you already understand. Create analogies. Use it in small problems. Go back, adjust, and strengthen it. Until that thin line stops being fragile and becomes a solid structure inside your baggage. At that moment, you did not just “understand an explanation.” You built a real bridge between knowledge A and knowledge B. And when that bridge exists, you can visit that path as many times as you want. That is why, for me, programming is not about memorizing everything. Depending on your IDE, you do not even need to remember the full name of things. Sometimes you remember the first letters and it already helps you. The center is not memory. The center is logic, connection, and construction. Because understanding someone else’s explanation is one thing. Building your own mental road to that explanation is something completely different.
1
2
109
you had to take profits sir
1
2
130
Replying to @novabladeth
Here to support 👑
1
20
71
2fd2d6id3k9gHGe2Tvn2cDaHSLntcEXAQqUYq5nJeSDG probably nothing
2
122
In 2026, the name Perceptron comes back with a new, powerful meaning @PerceptronNTWK turns you into a living node of a decentralized data network for AI You share idle internet → the network collects clean public web data → humans + agents verify it → high-quality datasets are produced to train models without Big Tech bias → you earn points and $PERC It’s the classic perceptron concept at community scale: small individual contributions → valuable emergent intelligence. The difference? Now the network rewards you instead of just using you for free. I’ve already installed the extension + app on 3 devices. Daily farming active. How many nodes do you have online? Did you catch the airdrop waves? Still early. Let’s build the future of decentralized AI together
18
17
785
This is what crypto has been missing @RialoHQ Native privacy for users, but compliant for banks and institutions Encrypted transactions, hidden amounts, and regulators only see what they need through viewing keys No more of that transparent blockchain bullshit that exposes everything and scares away the real world Backed by Pantera Capital this is going to fly Who else is hyped? I’ll be keeping an eye on the devnet
12
11
2,020