ohhh we now got copy image 🫡🫡🫡 i don need to screenshot anymore . awesome
❤5
Yeah absolutely. I’ve felt impostor syndrome so heavy that quitting felt like the logical option. Not dramatic quitting… quiet quitting in my head. The kind where you start thinking, “Maybe I’m not built for this. Maybe everyone else is just smarter.”
But here’s the truth I learned the hard way: impostor syndrome doesn’t show up when you’re fake it shows up when you’re growing. Beginners are loud with confidence. The doubt comes when you finally understand how big the mountain really is.
There were times I shipped things while feeling completely unqualified. And then people used them. Trusted them. Paid for them. That messed with my head in the best way because the evidence started to contradict the fear.
I didn’t beat impostor syndrome by “believing in myself.” I beat it by doing the work even while feeling like a fraud. Consistency silenced the noise.
So yeah, I’ve wanted to quit because of it. More than once. But every level I reached only happened because I kept moving while doubting.
But here’s the truth I learned the hard way: impostor syndrome doesn’t show up when you’re fake it shows up when you’re growing. Beginners are loud with confidence. The doubt comes when you finally understand how big the mountain really is.
There were times I shipped things while feeling completely unqualified. And then people used them. Trusted them. Paid for them. That messed with my head in the best way because the evidence started to contradict the fear.
I didn’t beat impostor syndrome by “believing in myself.” I beat it by doing the work even while feeling like a fraud. Consistency silenced the noise.
So yeah, I’ve wanted to quit because of it. More than once. But every level I reached only happened because I kept moving while doubting.
❤17
My journey in tech has been anything but smooth. It started with curiosity and big dreams, but the early phase was mostly confusion, inconsistency, and selfdoubt. I jumped between tutorials, frameworks, and ideas thinking i was “exploring,” but honestly, i was just avoiding committing to one path. that cost me time.
The biggest struggle early on wasn’t even code it was discipline. I would have weeks of extreme motivation, then disappear for days. i compared myself to people who were far ahead and used that as a reason to feel behind instead of using it as fuel.
My first real milestone was building something that actually worked and that other people used. that changed everything. it showed me that I didn’t need to be perfect to be valuable. Shipping small projects gave me confidence that no tutorial ever did.
The biggest struggle early on wasn’t even code it was discipline. I would have weeks of extreme motivation, then disappear for days. i compared myself to people who were far ahead and used that as a reason to feel behind instead of using it as fuel.
My first real milestone was building something that actually worked and that other people used. that changed everything. it showed me that I didn’t need to be perfect to be valuable. Shipping small projects gave me confidence that no tutorial ever did.
❤8
The Software Guy
My journey in tech has been anything but smooth. It started with curiosity and big dreams, but the early phase was mostly confusion, inconsistency, and selfdoubt. I jumped between tutorials, frameworks, and ideas thinking i was “exploring,” but honestly, i…
Mistakes?a loooot. overcomplicating things. chasing trends instead of fundamentals. waiting too long to share my work because I thought it wasn’t “good enough.” also thinking I needed permission before calling myself a developer. I didn’t.
🤝3❤1
The Software Guy
Photo
For anyone starting in backend development, my strongest advice is to commit to one language and ecosystem for several months instead of jumping between technologies. Focus on mastering the fundamentals early: how HTTP works, how to design APIs, how to use a relational database like PostgreSQL, and how to deploy a real application to production. Begin building from the first week start with simple projects that include authentication, CRUD operations, and basic security practices such as password hashing and input validation. Avoid the trap of over-consuming tutorials without shipping real projects. In parallel, learn sql properly before relying heavily on ORMs, and get comfortable with Linux, environment variables, and Docker for deployment. As for resources, official documentation should always be your foundation Node.js and TypeScript docs for JavaScript backends, the official Go Tour and Go by example for Golang, or FastAPI documentation for Python. Supplement these with high-quality educators such as The Net Ninja, Hussein Nasser, and Fireship for backend concepts, and combine everything with consistent, real world project building. Consistency, practical implementation, and early exposure to deployment will accelerate growth far more than passive learning
❤7💯1
hmm...... i think you have been in my channel for too long😄. but yeah i used to workout soo hard that i lost more than 17kg in just 8 month . maybe i will talk about how i did that in another post or reply ........ and i got some transformation photos but im sure you guys would make fun of me if i share lmfao so NOO!😁
😁3❤1🔥1
Woww😂😂😂 i think there are too much rich people here . Yo take it easy it aint worth it 😂😂