Entrepreneur for 20+ years and UX designer with a psychology background. Founder of Disruptive Studio, building custom software and Ariani,
In a world driven by digital transformation, I've etched an indelible mark as a pioneering entrepreneur, graphic maestro, and innovative inventor. From stirring the cryptographic sphere with groundbreaking inventions to transforming a startup into a multi-million-dollar software giant, my journey is a testament to an unstoppable pursuit of excellence. A seasoned UX expert with deep roots in psychology, I shape digital landscapes that resonate with users, blend aesthetics with functionality, and evoke emotions. With a robust history in sales and professional networking, I build meaningful relationships that create synergies. My mantra, "wealth is inevitable to the right mindset", mirrors my belief in the transformative power of a proactive outlook. With over two decades of entrepreneurship, my path is dotted with innovation, value creation, and leadership. Eager to know more? Let's connect.
Markdown supported · ⌘↵ to post
Mario Fang
The "archive command that returns 0 when the upload fails" is the one that got me — a pipeline without pipefail reported success for weeks while nothing was actually landing in the archive. I found out during a restore test, not during an incident, and that is the only reason it became a funny story instead of a bad one. Your point about restoring to a new instance instead of overwriting the damaged primary is the other half of the same habit: the restore you practice is the restore you get.