Edemy
Kanalga Telegram’da o‘tish
Ethiopian Technology Academy Discussion group -> @edemy_et
Ko'proq ko'rsatish5 162
Obunachilar
Ma'lumot yo'q24 soatlar
+567 kun
+6030 kun
Ma'lumot yuklanmoqda...
O'xshash kanallar
Taglar buluti
Kirish va chiqish esdaliklari
---
---
---
---
---
---
Obunachilarni jalb qilish
Sentabr '26
Sentabr '26
+5
0 kanalda
Avgust '26
+165
6 kanalda
Get PRO
Iyul '26
+101
2 kanalda
Get PRO
Iyun '26
+83
2 kanalda
Get PRO
May '26
+109
3 kanalda
Get PRO
Aprel '26
+119
6 kanalda
Get PRO
Mart '26
+113
2 kanalda
Get PRO
Fevral '26
+102
6 kanalda
Get PRO
Yanvar '26
+91
35 kanalda
Get PRO
Dekabr '25
+103
7 kanalda
Get PRO
Noyabr '25
+96
1 kanalda
Get PRO
Oktabr '25
+182
4 kanalda
Get PRO
Sentabr '25
+173
6 kanalda
Get PRO
Avgust '25
+201
4 kanalda
Get PRO
Iyul '25
+117
2 kanalda
Get PRO
Iyun '25
+221
3 kanalda
Get PRO
May '25
+213
7 kanalda
Get PRO
Aprel '25
+143
9 kanalda
Get PRO
Mart '25
+144
2 kanalda
Get PRO
Fevral '25
+694
7 kanalda
Get PRO
Yanvar '25
+209
5 kanalda
Get PRO
Dekabr '24
+177
5 kanalda
Get PRO
Noyabr '24
+225
5 kanalda
Get PRO
Oktabr '24
+424
5 kanalda
Get PRO
Sentabr '24
+366
10 kanalda
Get PRO
Avgust '24
+2 116
1 kanalda
| Sana | Obunachilarni jalb qilish | Esdaliklar | Kanallar | |
| 02 Sentabr | +3 | |||
| 01 Sentabr | +2 |
Kanal postlari
“I’ll start when I feel more ready.”
“I’ll start when I know enough.”
“Maybe I’m not ready yet. I’ll wait until I feel more confident.”
We say these things all the time. But the truth is, experience doesn’t come before you start. It comes because you start.
You learn by trying, making mistakes, solving problems, and trying again.
There may never be a “perfect” time.
Start where you are, use what you have, and learn along the way.
The right time isn’t someday. It’s when you decide to begin.
@edemy251
| 2 |  It’s already Monday!
I don’t know what happened to Saturday and Sunday… they looked like they were on fast-forward.
Anyway, back to work.
This week, I’ll continue a task I started on Sunday, start working on the design for a new project I’ve been wanting to begin, and of course, keep working on client projects.
New week, new tasks, new progress.
Have a productive week! Start by planning, work on the high-priority tasks first, and focus on making progress one task at a time.
Don’t overthink it, just make it count.
Happy Monday!
@edemy251 | 734 |
| 3 | It was awesome catching up with you all! 🙌 Thank you everyone for joining us.
And a big thank you to Biran and Mekbib for sharing their amazing experience, knowledge, and value with us. Really appreciate you both! ❤️
@edemy251 | 818 |
| 4 | We’ll start in 4 minutes! You can drop any questions or topics you’d like us to address during the session.
@edemy251 | 1 004 |
| 5 | Tech jobs aren't necessarily difficult because every concept is extremely difficult.
They're difficult because becoming good requires discipline, consistency, patience, and continuous learning.
And the learning never really stops. There’s always a new technology, framework, tool, or concept to learn.
The hard part isn’t learning something once. It’s staying curious and consistent for years.
Talent can give you a head start, but consistency compounds.
Sometimes, the difference isn’t who is smarter. It’s who keeps learning and keeps going.
@edemy251 | 1 129 |
| 6 | If you’re working as a freelancer, don’t think only about the next project. Think long term.
Treat your freelancing journey like you’re building a small agency.
Most of the time, you’re not just writing code. You’re finding clients, selling your skills, managing the project, communicating with the client, testing the product, fixing problems, and making sure everything gets delivered.
You’re already learning many of the skills needed to run a business.
And don’t focus only on getting new clients. Build long-term relationships with the clients you already have.
Do good work. Communicate well. Build trust.
A happy client can come back with another project, recommend you to someone else, or even become a long-term partner.
And who knows?
One day, that freelance journey might become your agency, your company, or even your startup.
Don’t just freelance for the next payment. Build something that can grow beyond you.
@edemy251 | 1 296 |
| 7 | Hey everyone!
I know I haven’t been very active on the channel lately, and it’s been a while since we had a live session. I’m sure you may have some questions, ideas, or topics you’d like to discuss.
I’m free this Sunday at 2:00 PM, so we can have a live session and catch up. 😊
Feel free to bring any questions or topics you’d like us to talk about. Looking forward to seeing you all! 🙌
@edemy251 | 1 093 |
| 8 | https://youtu.be/w8SHWwDehS0?si=z59HRrN0WtTjItiE | 1 379 |
| 9 | 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 | 1 374 |
| 10 | 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 | 1 797 |
| 11 | 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 | 2 316 |
| 12 | Rich people use social media to sell, broke people use social media to scroll.
ሞተናል ወገን 😅 | 1 770 |
| 13 | 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 | 3 149 |
| 14 |  I think Tele wanted to surprise me today. They finally decided to spare me. 😂
@edemy251 | 2 510 |
| 15 | 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 | 2 772 |
| 16 | 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 | 2 533 |
| 17 |  Which could have be an email 🙈😁
@edemy251 | 2 195 |
| 18 | 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 | 2 230 |
| 19 | 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 | 2 493 |
| 20 | Shipping an app to the App Store is a lesson in patience 🙈.
Meanwhile, publishing on Google Play is surprisingly simple and straightforward.
@edemy251 | 2 248 |
