Suggestions
Eugene Yaroslavtsev
Software Engineer at Meetsmore
Highlights
I've been reflecting on where my time goes and what really drives me. It's become clear: I'm at my best when I'm knee-deep in code. There's something uniquely satisfying about writing a function, seeing it run, and iterating in real-time. That immediate feedback loop? It's addictive.
All these meetings, specs, and market analyses? They're just distractions. They don't fuel me like coding does. My motivation skyrockets when I'm building something I'm genuinely proud of, something I can't wait to show off to peers I respect.
Maybe it's time to restructure my days. Maximize time spent on what I love - actual development. Sure, Facebook had it right with "code wins arguments," but it goes deeper. Code wins motivation. It wins progress. It wins innovation.
So here's my new philosophy: Minimize the fluff, maximize the build. If I'm not sure about the target market or product direction, I'll code a prototype and let the results speak. Worst case? I pivot fast and learn something. Best case? I've already got a working product while others are still debating specs.
In the end, it's about aligning my time with my passion. Because when I'm engrossed in coding, seeing my ideas come to life in real-time, that's when I'm not just productive - I'm fulfilled.
And isn't that the whole point?
Meta's account suspension system poses a compelling case study in "fuzzy correctness" scalability. Recent events underscore the challenge of balancing automated security measures with real-world identity complexities.
- My own FB account faced a hard suspension last month due to a false-positive UAT check.
- This month, a comedian's livelihood on Instagram was jeopardized by an erroneous ban for impersonation.
[UPDATE: the above person's Instagram account has now been unlocked. Thank you to whoever it was that made that happen ❤️ ]
Standard support channels failed to provide a resolution in both instances, highlighting the critical impact on individuals' livelihoods.
Troublingly, an informal internal network has become the go-to solution, as seen in a recent incident where a recovery effort was initiated through a shared Slack channel by an ex-Uber employee. While commendable, relying on such ad-hoc interventions by employees like Sandeep Paruchuri is not a sustainable or fair approach.
This human-driven exception handling system underscores the need for a more robust and equitable resolution process.
Vivek Trehan Guocheng Xie Qing Xu
Asking for your help in raising this issue to the relevant teams. Let me know if you require additional details.
