This is the most important lesson of options. It's never just a coin flip. You have an unimaginably huge number of factors riding against your success. It's not even remotely close to a 50/50 win/lose scenario. There are a million ways to lose, and just a few narrow ways to win. You literally have better odds going to the roulette table and placing a bet on red.
E.g. If I am net long in my portfolio and I fear some headwinds I can buy a put or two for the peace of mind. Now those puts should be always considered as worthless, and it is just the price to pay for the peace of mind.
Similarly you sell options. Trading options on the other hand is just pure gambling. Even if you get the direction right you likely won't get the timing right (or the volatility).
edit: typo
I enjoy using it and playing with it, but so many use cases can be addressed with something simpler - either just Docker / Swarm / AWS ECS etc. alternatives or just going for VMs with well defined CI/CD processes that let you tear down the infrastructure and set it up again easily.
What very interests me are the concepts K8s build on that are not usually recognized - to me K8s seems a lot like a JVM, just that it operates on infrastructural (and not runtime) level.
I enjoy experimenting with these concepts when applied back in the runtime world - it is for instance interesting to run 100s of servers with JVM and let them load/execute new dependencies and code at runtime (JVM is very well suited for that).
This is area that is not yet explored and would probably deserve more attention as it allows for distributed rapid computing that is infrastructure/platform independent (the downside is that it requires (just) JVM and the isolation is not perfect).