Edemy

Chase your obsession. I’ve learned that the things I become obsessed with learning are often the things that push my life forward. When something truly interests me, I don’t mind asking questions, researching for hours, trying again after failing, or staying up late trying to figure it out. People might call it obsession. But sometimes, obsession is simply deep curiosity + consistency. Chase what keeps you curious. Chase what makes you want to get better. Chase the things you can’t stop thinking about. Because when you spend enough time getting better at something you genuinely care about, what looks like luck to other people is often years of obsession they never saw. @edemy251

Story time. Most of the time on this channel, I tell people to read client reviews carefully before accepting a contract. Read what freelancers say about the client, and just as importantly, read what the client says about freelancers. If I see a pattern of bad reviews, I usually move on. But one client completely challenged the way I looked at reviews. A while back, I received an invitation for a job that was a perfect fit for my niche. The client was looking for a long-term engineer, and everything about the opportunity looked exactly like what I had been hoping for. Then I opened the reviews. Some freelancers described the client as one of the best they had ever worked with. Others shared experiences that were very different. I remember just staring at my screen, wondering... "Should I accept this or not?" I kept going back and forth. The positive reviews made me excited. The other reviews made me hesitate. Then I had one thought. "Maybe this client is simply honest. Maybe the freelancers just didn't deliver the quality of work the client expected." And maybe when someone doesn't meet expectations, the client writes an honest review instead of sugar-coating it. I decided to trust my instincts. I accepted the contract. But the truth is... Those reviews never left my mind. Every task felt like a test. Every pull request. Every bug fix. Every message I sent. I wasn't just trying to do a good job. I was trying to prove to myself that I had made the right decision. My perfectionism completely took over. No matter how much I got done, it never felt like enough. I would finish a task and immediately start thinking about everything I could have done better. I was constantly worried that I wasn't delivering enough value. I remember one weekend when we ran into a difficult issue. I spent all of Saturday and Sunday trying to solve it. I barely slept. I was still sitting at my desk when the sun came up. Looking back, I realize I wasn't just working hard. The reviews I had read before accepting the contract had created pressure in my own mind. Pressure that the client never actually put on me. Then one day, I received a message from the client. It said something like: "It seems you've settled in well, and you're doing an amazing job on the team. As a thank you, we've sent you a bonus." I still remember how that felt. The bonus was nice. But it was the message that meant the most. It woke me up from that cycle of self-doubt. For the first time, I stopped questioning every little thing I did. I started trusting myself more. Since then, I've worked on many different projects with this client. I've learned more than I expected. I've received more recognition over the years. I've been given opportunities to work on challenging projects. And I've come to understand why the reviews were so mixed. This client has standards. If you do great work, communicate well, and genuinely care about what you're build, it gets noticed. Your work is appreciated. You're rewarded. But if something doesn't go well, honest feedback is given. There isn't any pretending. And honestly, I respect that. My biggest takeaway? Always read reviews. They're valuable. They can help you spot red flags and avoid bad situations. But don't let someone else's experience become your future before you've even started. Every working relationship is different. At the same time, don't blindly accept a contract just because you hope your experience will be different. Read carefully. Look for patterns. Trust your judgment. Ask questions when something feels off. Then, if you decide to take the opportunity, stop letting the reviews live rent-free in your head. Focus on doing your best work. Sometimes, the contract you're most unsure about becomes the one that helps you grow the most and even changes your life. @edemy251

Btw, if you have time to scroll through social media, you probably have time to upload something too. It’s better to be the one creating content than spending all your time consuming it. Your brain adapts to what you repeatedly do. Feed it ideas, creativity, and learning not endless content that adds nothing to your life. So, be the creator, not just the consumer. Don’t let your daily screen time be mostly watching other people live. @edemy251

Rich people use social media to sell, broke people use social media to scroll. ሞተናል ወገን 😅

People ask me if vibe coding alone is enough to build software. Based on the current state of AI, my answer is: it depends on what you're building. For small apps, prototypes, internal tools, AI can be incredibly productive. Tools like Claude Code can generate working features much faster when you know the architecture and can give clear instructions. But enterprise software is a different game. Writing code is only a small part of building a real product. Someone still has to review the AI's work, catch hidden bugs, think about security, optimize performance, write tests, design scalable systems, and maintain the code for years. AI is making software development faster. The developers who understand architecture, debugging, and system design will get the most value from AI. Those who rely only on vibe coding will eventually hit a wall when projects become more complex. @edemy251

I think Tele wanted to surprise me today. They finally decided to spare me. 😂 @edemy251

Ever solved a bug in your dream... then woke up and forgot the solution? 😅 It sounds funny, but there's actually some science behind it. While you sleep, your brain doesn't stop working. It keeps processing information, making connections, and sometimes even finds patterns or solutions you couldn't see while you were awake. That's why people occasionally wake up with a great idea. The problem? If you don't write it down immediately, your brain can quickly let it disappear. During the transition from sleep to being fully awake, dream memories are often fragile and fade within minutes. So now I'm sitting here trying to remember the "genius" solution my sleeping brain came up with. 😂 @edemy251

The Euro champions vs. the Copa América champions... It's finally happening. ⚽ This is going to be one amazing game, and I'll be happy no matter who wins. 🏆 @edemy251

Which could have be an email 🙈😁 @edemy251

Getting an opportunity is only the beginning. What happens after that is what really shapes your career. I've seen people land great opportunities but struggle to keep them. Not because they lacked technical skills, but because they lacked consistency, communication, accountability, and the willingness to keep learning. Skills can get people to notice you. Your attitude, reliability, and commitment are what make people trust you with bigger responsibilities. Keep improving your technical skills, but don't ignore the habits that make others want to work with you. In the long run, those habits often make the biggest difference. @edemy251

The biggest difference between developers getting great results from AI and those constantly fighting it isn't the model. It's how well they understand the problem they're solving. The real skill is understanding a problem, understanding the codebase, and communicating that context clearly to AI. The better you can describe what the code should do, why it should work that way, and what must stay unchanged, the better the output will be. Blindly asking AI to build or fix things without understanding the code might work for small tasks, but it doesn't scale to real-world projects. As projects grow, someone still needs to understand the system and make the engineering decisions. You can only do that if you understand the system yourself. That's why software engineering fundamentals matter more than ever. The value is shifting toward technical judgment, problem solving, and knowing how to guide AI not just generating code. @edemy251

Shipping an app to the App Store is a lesson in patience 🙈. Meanwhile, publishing on Google Play is surprisingly simple and straightforward. @edemy251

AI is your copilot, not your replacement. The pilot still needs to know how to fly. @edemy251

People often call it luck. But many of those "lucky" moments are the result of years of learning, failing, improving, and staying consistent behind the scenes. The opportunity may come unexpectedly, but being ready for it is what makes the difference. @edemy251

We were trying to escape a 9-5, but we accidentally ended up building a 24/7😊

Don't be afraid to talk about money, expectations, timelines, or agreements. A lot of people wait for the other person to bring these things up first. If they don't, they avoid the conversation altogether. But professionalism isn't waiting for someone else to set the standard. If a contract is needed, mention it. If expectations are unclear, ask. If pricing hasn't been discussed, bring it up. If something should be documented, put it in writing. Clear communication isn't awkward. It shows respect for both sides. In business, people often take their cues from you. The boundaries you set, the questions you ask, and the standards you maintain teach others how to work with you and what to expect from you. The conversations that feel uncomfortable at the beginning are often the ones that prevent bigger problems later. @edemy251

Taking Notes! 😂 @edemy251

Grant me discipline over desire, consistency over comfort, and purpose over pleasure.🙏 @pocodes

Today I was thinking about how much my personality has shaped my life. People often say I overthink things or get too obsessed. They're probably right. But when I look back, those traits are the reason I learned many of the things I know today. I remember seeing senior engineers build things that seemed impossible to me. Instead of moving on, I kept thinking about how they did it. I'd spend hours researching, testing things, and trying again until I understood. That's how I've approached most things in life. I don't usually wait for someone to show me the way. If I want something, I start looking for a path to get there. One thing I've learned is that nobody can want your dreams more than you do. People can support you, but you have to do the work. And the people around you matter. Some will encourage your growth. Others will make you think smaller than you should. The traits that some people see as flaws overthinking and perfectionism have helped me learn, grow, and keep going when things got difficult. @edemy251