I've built ETH watchtower, a real-time heuristics scanning tool checking contracts, addresses and transactions. The published version is a PoC and cut down since the full version is way too expensive for me to run together with the frontend for public use. If anyone is interested in building with me, hosting full low latency ethereum nodes or help out with the project feel free to reach out.
Senior DevOps, Infrastructure/Platform Engineer, Cloud Architect, and Security
Engineer with 20+ years of experience designing, automating, and
scaling mission-critical systems across data centers, cloud
platforms, and edge environments.
Open to interesting DevOps/SRE, cloud infrastructure, cybersecurity or platform engineering positions as well as contract and consulting work in or around Ho
Chi Minh City, Vietnam - or remote worldwide, especially within the IaaS, PaaS, Startups, AI/ML, Security, Web3/DeFi, FinTech or Cloud sectors.
What is he supposed to do? I'm absolutely sure he's still looking, trying his best to find a job or a permanent solution to his situation. But there's no reason to complain and whine about things he can't change.
Life is shit sometimes, when he is out, he'll be out. Or he'll find some way of generating income, and then he gets another chance.
I've been in similar situations myself, and there is absolutely no reason to get stuck up regardless how stressful and painful it is, you can only do your best and that's it.
> I'm absolutely sure he's still looking, trying his best to find a job or a permanent solution to his situation. But there's no reason to complain and whine about things he can't change.
I'm baffled by these responses. The reason we're calling him out is because he literally says he is not looking, at least for another job, in his blog post. It's not about wanting him to be stressed and anxious, it's about trying to understand how he plans to not have a job in 2025 and just continuing on doing more of the same, when in previous years he said he started with 80k, and now he's starting with 0.
The worst thing about the whole kubernetes-cult and the like is that IaC and CM was supposed to help us reduce configuration, to make it less prone to failure and easier to manage.
But the truth is that we ran service based architecture, network meshes and containers with bash just fine before cloud everything, usually with less effort than it is to do literally anything today. Sure you had to know how to set up network bonding and how to tune your systems.
Very, very few people and businesses _needs_ kubernetes or it's cousins. Most just need a decent system administrator.
I agree with you, but can offer a counterpoint. A system administrator might setup a server in a certain way, and if they leave the replacement has a hard time discovering what they did.
With IaC, all decisions are templated in the code and the replacement has full insight into the state of the machine.
Good for you, my bash on balls was unfortunately not able to solve service based meshtainer architecture :(
I remember how kernel module params for ALG/bonding/teaming had to be figured out for each fancy NIC/driver, it was fun, but definitely not great. Of course this is mostly solved if you pay the cloud premium.
Most businesses need a product guy/gal, a website, then a developer, then later one VM or Heroku or something. And maybe if there's at least a few customers, yeah, it makes sense to think about ops (as in business ops), and then eventually sure, engineering needs to scale to solve the challenges, and that might mean getting a sysadmin.
As I hope decent system administrator... turns out I find running minimal kubernetes setup (k3s is great there) more sensible and cheaper than managing the server in classic way.
Congratulations, OP learned about "we expect loyalty and effort from you, but you won't get any from us", which is 99.5% of all companies out there. I hope OP does well on their own and don't have to work in this kind of disingenuous places in the future.
