Ivan Obeso Aguera
621 posts




The “EU” imposed this crazy fine not just on @X, but also on me personally, which is even more insane! Therefore, it would seem appropriate to apply our response not just to the EU, but also to the individuals who took this action against me.

In our view @X doesn’t comply with the DSA in key transparency areas. It misleads users, fails to provide adequate ad repository and blocks access to data for researchers. It’s the first time we issue preliminary findings under the Digital Services Act. 👇 europa.eu/!CGPVCV

Sometimes when I look back at my early years in tech, I cringe a bit. I used to walk around with that quiet engineer ego… thinking I knew more than I actually did, arguing on PRs just to sound smart, over-engineering random stuff cause I wanted to “prove” I was the clever one in the room. But the funny thing is… the people who actually grow into staff level never behave like that. Real seniority is almost the opposite of ego. It’s like that basketball analogy you posted. In tech, the “uncoachable engineer” looks like: – arguing with every code review instead of trying to understand the context – assuming their solution is the best without reading history or constraints – avoiding basic fundamentals because they think they’re “past that stage” – talking more than they listen – optimizing for cleverness instead of long-term value The shift happens when you realise staff engineering is not about being the smartest coder… it’s about being the calmest learner. The people I saw actually grow this year focused on very boring but powerful habits: – asking dumb questions early instead of hiding confusion – reading design docs deeply before proposing anything – treating every senior dev as a free mentor instead of competition – learning fundamentals (OS, distributed systems, networks) without shame – shipping small things consistently instead of chasing some genius moment – unblocking teammates even when the problem is not glamorous – choosing clarity over cleverness in every PR – knowing when to drop an idea because it doesn’t serve the team What took me years to understand: Your ego is the biggest blocker to becoming staff. Not your skills. Not the difficulty of the problems. Not the company politics. Just your ego. The moment you stop performing intelligence and start absorbing knowledge, everything compounds. The moment you stop trying to win arguments and start trying to understand systems, everything becomes easier. And the moment you stop coding to impress and start coding to provide value, people suddenly trust you with bigger responsibilities. Real staff engineers are basically “advanced beginners” who never stopped learning. If I had to summarise what I learnt this year: Drop the ego, stay curious, make things simpler, help others win, and your career will quietly take off in a way you won’t even realise until months later. It’s never about being the star of the park. It’s about becoming the person the whole team relies on.





Es la primera vez que Chatllipití me dice que me devuelve algo MAÑANA O_______o






















