Kelkonosemmel

4 ms·

1.
by Kelkonosemmel 3y ago
Yepp. I think a robot who can easily follow your commands should be doable in 10-20 years. I plan to buy a farm when I have the money and I'm pretty sure while I will/want to do a lot of hands on renovation and sculpting (park, et
2.
by Kelkonosemmel 3y ago
Huh? I'm upgrading k8s for years now, had very rarely issues. Independent of it if you really have big workloads it's the right thing anyway to have a good team behind it. Nonetheless if you use gke for example I and no complicate
3.
by Kelkonosemmel 3y ago
How to add prompt knowledge into research? By having papers about it. Shouldn't be the tooling around it good enough that a few prompt papers don't overload the system?
4.
by Kelkonosemmel 3y ago
I love GitHub actions and think gitlab is okay. I found actions easier to use
5.
by Kelkonosemmel 3y ago
Global load balancer and traffic shifting is a real thing. But my preferred way is in place as it's easy: upgrade one Ctrl plane node after the other, than upgrade every node or create a new one and move your workload. The power of k8s
6.
by Kelkonosemmel 3y ago
GKE does Auto upgrade and enforces them. You can't get a really old k8s version on gke
7.
by Kelkonosemmel 3y ago
That's the big advantage of kubernetes: You need to keep updating it! No legacy 10 year old garbage in the corner just because managers don't understand that this is shit. And for me it's the perfect excuse NOT having those g
8.
by Kelkonosemmel 3y ago
I communicate on purpose that code review is never the 99% mark It's the time to get feedback and improve. The problem is: if people are stuck and don't learn the code review phase will always stay as a long thing. The whole team
9.
by Kelkonosemmel 3y ago
I rarely think about it but not for more freedom. For making more money for 5 years or so to retire earlier. But than I think about the bigger social gap and dislike the idea again.