Orestis Palampougioukis

@Im_BluePhantom @KevinNaughtonJr Yeah, that’s mostly survivor bias talking. For every success story of taking a huge risk and succeeding, there are countless unheard stories of failure.

You didn't make the worst decision. You made the SCARIEST decision. Staying at Google is safe. But safe ≠ fulfilling. Every founder, creator, and builder has this "wtf did I do" moment. The grass isn't greener. It's just different grass that YOU chose. You're not failing. You're learning what you actually want. Most people never get brave enough to find out.

6 months ago i made the worst decision of my life

Are you clear on the difference between == vs === in programming? Loose: == compares values after type coercion (e.g., "5" == 5 is true). Strict: === checks value AND type (e.g., "5" === 5 is false). Unless there is a very specific need for loose comparison, stick with === for cleaner, bug-free code.

So, let's aim to be great developers who balance technical complexity with practicality. Don't over-engineer. Focus on what truly matters: delivering results and satisfying customers.

As a growing software engineer, remember: It's better to have one successful, albeit messy, project than a thousand perfect but unreleased ones. Success isn't just about code quality; it's about delivering value.

Thread 🧵: The Real Measure of Success in Software Development As developers, we often get caught up in writing "perfect code." But let's not forget that the ultimate goal is customer satisfaction, not layers of abstraction and the fanciest pattern. I recently read a LinkedIn post that took me many years back, to my second job as a developer. The product was thriving, even though the codebase was a tangled mess of spaghetti code written by non-coders.

New to coding? Don’t fall into the endless tutorials trap. Once you understand HTML/CSS basics, start building something real, like a clean one-pager portfolio. 💡Remember to use semantic tags where it makes sense, like

and