en
Feedback
Anticodeguy

Anticodeguy

Open in Telegram

Technomad & systems thinker exploring paths to freedom and prosperity https://stan.store/anticodeguy

Show more
649
Subscribers
No data24 hours
No data7 days
-330 days
Posts Archive
Most people think they need to be world-class experts to monetize their knowledge Read more how Your Experience Is Worth Million Dollars: How To Build A One-Person Knowledge Business Watch more videos like that on my YouTube @anticodeguy

Learning by doing is the greatest way for skill acquisition, no doubt about it. But why stop here? You can master your skill by applying these 3 steps that accelerate your learning even further: (The first three steps read in my previous thread) --- Step 4: Share your work publicly. Even if it's incomplete. Even if it's imperfect. Build an MVP - minimum viable product. Something people can touch, try, give feedback on. Real feedback destroys your brain's protective fantasies. --- A study found feedback has a 0.7-0.79 effect size on achievement. People sharing weight-loss progress on Twitter (back then) lost more weight than those who kept it private. Every 10 tweets = 0.5% more weight loss. #buildInPublic works even for fat. --- Step 5: Iterate and improve. Edison said it: "I haven't failed. I've just found 10,000 ways that won't work." Your first version is only the beginning. Make a second version. Then a third. Each one teaches you what the next should be. --- I learned this with my product ANTIghostwriter. First sale was a disaster. Customer left mean feedback about my speaking in videos. I'm not a native English speaker. Recording screencasts in English was new. So I rewrote every script, reshot every video, and published v2. --- This is kaizen - continuous improvement. Most people never get good because they never get past version one. They build once, call it "good enough," and move on. Don't do that. --- Step 6: Teach what you know. There's no better way to learn than teaching someone else. Studies show students who prepare to teach recall more and organize knowledge better. Teaching forces you to clarify everything. --- When you teach, you can't hide behind vague understanding. Every time you struggle to explain something, you've found a gap in your knowledge. You don't need to be a world expert - just one step ahead of who you're teaching. --- Here's how all 6 steps work together: 1. Choose a real project 2. Build consistently 3. Learn just-in-time 4. Get feedback 5. Iterate 6. Teach others Then loop back. Each cycle compounds your skills. Do this for a year, you'll be skilled. --- There are three fears that hold people back: 1) Fear of judgment - ignore opinions from people not in the arena. 2) Fear of failure - you will fail. That's how learning works. 3) Fear of commitment - you don't need forever. Just commit to the next cycle. --- There's no secret to mastery. No shortcut. But there is a path. Stop waiting for the perfect moment. Choose your project. Start building. --- Detailed article with research data and stats: https://anticodeguy.substack.com/p/iterative-learning-the-feedback-loop?r=1m5hbt

Step 4: Share Publicly and Get Real Feedback Fourth step – share your project publicly, get feedback. Feedback is the key ste
Step 4: Share Publicly and Get Real Feedback Fourth step – share your project publicly, get feedback. Feedback is the key step. After building part of the project, even incomplete, there’s a term MVP (Minimum Viable Product) – a product with the minimum set of functions for use. It’s imperfect, without all the planned functions, but acceptable enough to try, touch, and give feedback. This is important, the most effective way to advance as a person. You get real data from the real world, not fantasies. Fantasies let you down, the brain protects you, deceives you that you’re doing everything right. You can imagine how great everything is, but real light will show something different. Don’t delay with feedback, no matter how uncomfortable it is. I recommend reading Mark Manson’s book “The Subtle Art of Not Giving a F*ck” – it will help you not care about others’ opinions. Post online, build in public, get feedback, like I do. I write articles, posts, sometimes it’s cringe, but people like them, comment, the material resonates with someone. This gives information about where to move. If material doesn’t get feedback, that’s also information – you’re doing something wrong. Set up a feedback loop, a cycle of feedback with the external world and people, to understand how the project works.

Installed @jetbrains Fleet, trying to log in: getting a 415 error. Tried every possible solution for about an hour, still the
+1
Installed @jetbrains Fleet, trying to log in: getting a 415 error. Tried every possible solution for about an hour, still there. Guys, seriously? Okay, bye! Going to install Cursor.

The greatest leverage in modern business isn't capital or connections Read more how Your Experience Is Worth Million Dollars: How To Build A One-Person Knowledge Business Watch more videos like that on my YouTube @anticodeguy

Step 2: Start Building (And Keep Building Consistently) “For the things we have to learn before we can do them, we learn by d
Step 2: Start Building (And Keep Building Consistently)
“For the things we have to learn before we can do them, we learn by doing them, e.g. men become builders by building.”
— Aristotle (4th century BC, Greek philosopher): The next point – start building, begin implementing the project, and you’ll understand what to do. In the following steps I’ll write how the cycle works, but this step is unifying. After choosing the project, start building it, dedicate time to it, even if it’s small intervals, but to the project. The main thing is consistency, not intense bursts when you work 16 hours on a weekend. This seems productive, but then for a week you feel burnout, you don’t want to return to the project. It’s better to work one hour every day – the work is more productive. This has been proven by me and people who study productivity scientifically. Consistency is better than intense attempts. This is a marathon, not a sprint. Small regular efforts every day give a greater result, even if the time is less. The work is more productive, you try to fit more actions into the hour that move the project toward implementation. Research on the spacing effect shows that spreading practice over time yields dramatically better long-term retention than cramming everything into one session. Material studied in spaced, daily sessions is remembered for weeks or months longer than material crammed in one burst. In fact, spaced practice can roughly double long-term retention compared to the same total hours done all at once.

Okay, this is actually pretty dope: I connected Codex to my GitHub, fed it the repo, described the bug that users face, and a
Okay, this is actually pretty dope: I connected Codex to my GitHub, fed it the repo, described the bug that users face, and after a couple of minutes it made a suggestion of a possible solution. Now I'm waiting for the real dev while he reviews my PR. Will it fix the bug?

Most people spend years "learning" but never actually build anything. But there's a better way to learn any skill - backed by research showing 1.64x better mastery than traditional methods: --- The traditional education model is backwards. It says: study everything first, do later. Reality check: I took a programming course, learned theory, algorithms, and methods. Then faced a real task and had no idea what to do. --- Here's what actually works: Step 1 - Choose a project you'll actually build. Not a test project jus "for practice". A real thing you'll show to people. Something useful to someone. --- Why does it have to be real? Because you need feedback. Test projects keep you in a loop of self-admiration. No one gives feedback, and you lie to yourself. Your brain produces the desired result. --- My example: I'm building a personal brand from scratch. After months of creating content, I packaged everything into ANTIghostwriter - my content creation system. It forced me to master every tool, refine every process, document every step. --- Step 2 - Start building consistently. Aristotle said it 2,400 years ago:
"We learn by doing them."
One hour every day beats 16-hour weekend sprints. Consistency wins over intensity. This is a marathon, not a sprint. --- Studies show: the spacing effect shows distributed practice doubles long-term retention vs cramming. Surgical training study: residents with shorter, distributed sessions retained skills far better than one-time intensive training. --- Step 3 - Fill knowledge gaps as you encounter them. Don't look for information in advance. Start doing. Hit a wall. Then learn what you need. I used to search textbooks, but now there's ChatGPT. Ask it, get results, keep building. --- 80% of knowledge is free online. Creators publish most content for free, then package it into courses. You're paying for convenience, not the knowledge itself. Use this. Fill gaps just-in-time. --- Real-world proof this works: Medical residencies: "see one, do one, teach one" German dual education: classroom + paid apprenticeships École 42: no classes, no instructors, just project-based coding All project-driven. All highly effective. --- Why this framework destroys traditional learning: Traditional: study first, apply later This framework: do first, study only what you need, keep doing This way knowledge becomes part of your working understanding, not memorized facts for a test. --- Choose your project today. What skill do you want? What real thing could you build? Block one hour daily. And start building. Don't prepare more, don't plan anything. Just open it and create the first piece. --- These 3 steps will get you functional. They'll take you from zero to competent with real, applicable skills. There are 3 more multipliers: feedback loops, iterative improvement, and teaching others. Stay tuned. --- For now read the full article on learning by doing: https://anticodeguy.substack.com/p/the-only-learning-by-doing-framework?r=1m5hbt

You have a million-dollar product sitting in your head right now Read more how Your Experience Is Worth Million Dollars: How To Build A One-Person Knowledge Business Watch more videos like that on my YouTube @anticodeguy

Step 1: Choose a Project You’ll Actually Build First step. Choose a project that you’ll implement. A real project that you’ll show to people, not a test one, not for practice, but one that’s useful to someone. I don’t know another way to learn besides a real project. I learned programming from scratch by doing a task. I could have spent years reading books, theorizing, but without a real project, you won’t develop skills. The project must be real so you can get feedback. Otherwise you’re in a loop of self-admiration, showing the project to yourself, no one gives a fuckfeedback, and we know how to lie to ourselves. The brain produces the desired result. There’s no point doing a test project for yourself. It must be real, visible to people. The project doesn’t have to be as large-scale as my query system. Complex tasks accelerate learning – I learned the basics, and the rest of the tasks became simple, I cracked 80% of them like nuts. This helps. If you’re building a personal brand, the project could be an article, posts, a content creation system. Come up with a system you’ll use and share it. An article is also a project. Take advantage of the opportunity. Choose a project, the main thing is that it’s visible to people. Use the #BuildInPublic tag, share your findings.

... So there I am, sitting in front of the computer, surrounded by textbooks, looking at the task I need to complete, not understanding which side to approach it from. I start reading textbooks, doing some basics. But I run into the first problem: I need to install a software environment to access the database. I need to have access to the server to upload executable files. We wrote in PHP, JavaScript helped with queries. Remember, this was a time when the internet wasn’t developed enough to find an answer to every question. There was no Stack Overflow where you could copy-paste code. Everything had to be written almost from scratch, which is what we did. I had a more experienced colleague, and I wasn’t shy about asking him questions. He showed me what programs he uses, what to install. I followed his advice, copied his experience. He showed me the foundation for my product. In the admin panel with database access, there’s a query system, convenient and flexible, allowing any query. My task – make the same thing for our database, an analog of this system. I started doing it. I have a sample, tools, a colleague I can ask, books from which to draw information. Then everything moves forward in iterations. I need to understand where the code begins. First, make a page with a connection to the database. I go to the book, see how it’s done, from the very beginning – that’s how any program in PHP starts, I figure out what a connection is, how the database works, I read the SQL book, connect, study the structure, and so on step by step. The Final Release By the appointed deadline, in one and a half months, from under my hands comes a finished product – a query system that we publish for users. The boss is satisfied, users not so much, because it’s complicated for them. I had to train them: I came to users, showed them how to use it, wrote instructions, posted them. This is where the real learning happened. Not in the classroom where we discussed theory. Not in the textbooks I skimmed. But in the doing. In the building. In the struggling and figuring it out as I went.

... A One Task And a Pile of Books My task: create a query system for the database that would be convenient for a simple user, so they could compose a query and get results in the form of a dynamic table, generated from the database of students and applicants. I’m staring at the computer screen, having written down the task formulation in my notebook, not understanding what to do or how to solve it. I didn’t know what a query system was or what an ERP system was. We only started studying these two courses later. I wasn’t working alone – I had a colleague who had been writing this system for a long time. The logical question to him: where do I start? He understood that I had no experience and handed me a set of books: about PHP, a textbook on SQL, and a textbook on JavaScript. Three huge thick books, more voluminous than many literary works we read in school. Listening to my colleague, I started reading, quickly realizing that I wouldn’t finish the task today. I clarified the deadline. The manager understood that the task was new for me, but without a deadline, it would never get done. She set a deadline – one and a half months. Considering working time, this should be enough. I have a deadline, three huge textbooks, and zero understanding of what to do. To be continued.

Probably the most compact website I've ever done
Probably the most compact website I've ever done

The Zeigarnik effect is destroying your mental clarity and you don't even know it Read more about Mental Decluttering: 5 Proven Techniques to Reclaim Your Mental Bandwidth Watch more videos like that on my YouTube @anticodeguy

I learned programming in 6 weeks on a real job. University spent 2 years teaching me theory I never used. Here's how to learn any skill the way that actually works: --- School teaches you formulas and dates. But nobody explains why you're memorizing them. The system was built decades ago and can't keep up with how fast the world changes. By the time you graduate, you realize - none of this knowledge matters like you thought. --- Second year of university, my professor invited me to work as a programmer. My first task: build a database query system for users. I stared at the screen. Had no idea where to start. They handed me 3 massive textbooks and gave me 6 weeks. --- University taught me theory - how code works, algorithms, methods. But faced with a real task, I realized none of those methodologies helped. I didn't know what to do specifically. This is the problem with traditional education. It prepares you for tests, not actual work. --- So I started building. Read the books, installed the software, asked my coworker questions. He showed me an example - "Make something like this." I had a sample, tools, someone to ask, and books to reference. Then everything moved forward in iterations. --- Here's what the data shows: 77% of recent college graduates learned more in 6 months on the job than in 4 years of college. 68% felt their degree didn't provide the skills needed for their job. There's a massive gap between what schools teach and what work demands. --- And employers know it too. 75% of HR leaders say colleges aren't preparing people at all for workplace needs. Only 24% of recent grads felt they had all the skills needed for their current job. The system is broken. Everyone knows it - except the system refuses to change. --- By the deadline, I shipped a working product. Users started using it. I trained them, wrote instructions, refined the system based on feedback. This is how real learning happened. Not in classrooms discussing theory. But in building, struggling, and figuring it out as I went. --- 4 years later, when I graduated, I had real experience building information systems. I published my resume online and started receiving calls from companies with job offers. All I had to do was choose what I liked. Because I learned by doing, not just studying. --- The internet changed everything. For the first time in history, the barriers to learning almost completely disappeared. Tools, resources, information - it's all there. You have freedom to choose what skills to develop, learn at your own pace, and build real things that matter. --- So here's my question: Think back to your education - school, university, whatever you went through. What percentage of what you learned do you actually use in your daily work? If you're honest, the most valuable skills you have, you learned by doing. --- You don't need permission to start learning in a way that actually works. The traditional system had its time. That time has passed. In my next article, I'm sharing the exact framework I used - the specific steps that worked for me. There's a better way. --- Meanwhile, read the first article with the full origin story of mine about how I started my career in IT: https://anticodeguy.substack.com/p/why-learning-by-doing-beats-traditional?r=1m5hbt

I think I found my Ikigai
I think I found my Ikigai

“I hear and I forget. I see and I remember. I do and I understand.” — Confucius (c. 5th century BC, Chinese philosopher) I ca
“I hear and I forget. I see and I remember. I do and I understand.”
— Confucius (c. 5th century BC, Chinese philosopher) I can’t help but recall an example from my own life. I was invited to work when I was in my second year of university. Due to peculiarities in my thinking and the fact that I enjoyed computers, which I got early in life, I was interested in programming. In programming classes, I did well, which my teacher noticed. She invited me to work at the university’s information center, which she managed, as a programmer. Without thinking long, I agreed. In my student years, the alternative was working in the service industry, where they paid more, but programming work appealed to me more because it gave prospects and experience by the time I graduated from university – a critical factor for finding work. I agreed and came to work my first day as a programmer. The first task they gave me was very different from what I’d done before. At university, they explained how to solve a problem, gave methods and templates, and by applying them I got the expected answer. Here it was different. My boss gave me a task: write a system. We were writing an information system for the university to maintain a database of students and applicants – a custom ERP system where all information about students was stored. There were user screens for managing information that was filled in when entering the university. ...

Ever wonder why cleaning your room suddenly makes complex problems easier to solve? Read more about Mental Decluttering: 5 Proven Techniques to Reclaim Your Mental Bandwidth Watch more videos like that on my YouTube @anticodeguy

One-Time Sales If you’re selling something that doesn’t require ongoing updates or support – like a comprehensive ebook or a
One-Time Sales If you’re selling something that doesn’t require ongoing updates or support – like a comprehensive ebook or a template pack – then charging once makes sense. You create it, sell it, and the customer owns it forever. It’s simpler to execute, especially when you’re just starting. You don’t have to maintain a service or constantly create new content to justify a subscription. Digital artist Beeple sold a single NFT artwork for $69 million at Christie’s auction in 2021. That’s an extreme outlier, obviously, but it proves that one-time sales can still generate massive numbers under the right circumstances.

Most solopreneurs think earning $1M requires 100K followers. Wrong. It's just math - and you're probably closer than you think. Here are some monetization models for one-person business: --- The subscription model compounds. One-time sales don't. Lenny's Newsletter: 18K paying subscribers × $150/year = $2M+ annually. One person. No employees. Just valuable content. --- Pieter Levels proved it with data: Subscription business hits $2M by year 5. Same user growth with one-time sales hits only $183K. The compounding effect of recurring revenue is powerful. --- But one-time sales still work for certain products. Beeple sold a single NFT for $69 million at Christie's. Templates, online courses: create once, sell infinite. You can update info when needed, but it's mostly "passive" income. --- Hybrid approach is the smartest move $50 ebook as entry point. $200/month membership for ongoing value. $2,000 high-ticket program for serious clients. This way you're not leaving money on the table. --- Service-based model: 10 clients × $5,000/month = $600K/year. When you get to 15-20 clients, you're past $1M. It's not easy. But achievable in specialized fields like design, development, or strategic consulting. --- Match your pricing to value delivery. If your product requires ongoing attention - subscription pricing makes sense. Create once, works forever - one-time pricing is better. --- The real value is hidden behind the repeatable sales process. You're not waking up with $1M in your bank. You're executing the same loop over and over: Someone discovers → sees value → purchases → tells others. --- Let's break down one million one more time: $100 product × 10,000 sales = 30 sales/day for a year. Or 200/week. Suddenly it's feasible. Sure, it fluctuates: some days it's zero, some weeks 50. Sales events like Black Friday may bring hundreds in one day (soon btw). --- You're building a machine, a system. Marketing, selling, delivering, supporting. Early on it's clunky and manual. But over time it will be automated, outsourced, and efficient. Focus your time on highest-leverage activities only. --- Start with what you can deliver value on today. Build your repeatable system. Use the internet's scale to your advantage. Break down one million to digestible chunks, pick your path, and start working the numbers. --- The full article on the topic: https://anticodeguy.substack.com/p/how-to-earn-my-first-million-dollars-2df?r=1m5hbt

Anticodeguy - Statistics & analytics of Telegram channel @anticodeguy