Right, who doesn't want to template hundreds of lines of code in a language that uses whitespace for logic and was never made neither for templating nor complex long documents(YAML)? What could possibly go wrong ("error missing xxx at line 728, but it might be a problem elsewhere").
Sure the full extend of Kubernetes is complicated and managing it might be a pain, but if you don’t go bonkers is not that hard to use it as a developer.
Remote: Indifferent
Willing to relocate: not at the moment, but open to discuss depending on the job
Technologies: backend/systems engineer generalist. At the moment I work with Go, Kubernetes and Linux. I’m interested in C, Rust and Python as well. Would work in any programming language.
CV: Upon request via LinkedIn or email. I have a outdated one here [1] without much information about my current employer.
Email: fred.rbittencourt [at] gmail [dot] com
I like petunias! Now what? How does that help anyone?
I'm certain your opinion on petunias and your possible distaste for orchids will be welcomed in a flower-news type orange site. :-)
1. A library exists to abstract over the bytes-into-sockets layer, meaning I don't need to deal with it; or
2. A library probably exists to abstract over the bytes-into-sockets layer, but I've chosen to ignore it either because I'm truly ignorant of it, or for intellectual stimulation.
(Note that in category 2 I count things like "not using protobuf/thrift/etc. for IPC.)
When are these things not true? Genuinely curious! I'm guessing interfacing with existing obscure third parties, or using obscure language environments, but what are examples of that? And what other usages are there?
E.g.: Learn the basics Transport Layer protocols (TCP/UDP) if you work with HTTP