Aside from making it easy to generate k8s manifests, this could also be a great learning tool. If you allowed this to generate multiple resources that are linked, it could be a great illustration of how different resources fit together.
945 karma · joined February 12, 2011
[ my public key: https://keybase.io/niksko; my proof: https://keybase.io/niksko/sigs/4_K48wgjxKBXyJFpmjrvHFlKOAJVWwd3S-VbG3-S6Ng ]
Aside from making it easy to generate k8s manifests, this could also be a great learning tool. If you allowed this to generate multiple resources that are linked, it could be a great illustration of how different resources fit together.
Excited about this, though you do wonder whether it'll suffer the same fate as Cloudformation: the Cloudformation team finds out about new feature launches the same time that the general public does. If the Kubernetes operator lags behind, you're going to have to fall back to something else if you need cutting edge features.
You can claim that a very senior Facebook employee is contributing to a _platform_ or _product_ that is a net negative to society. But at the same time, the work they're doing directly from an engineering perspective is probably technically on the cutting edge, and they're likely mentoring and growing a large number of other engineers at the same time.
Contributing to technical excellence and growing younger engineers is a positive, which is why they do their job. Don't dehumanize the people working at large corporations. They're not the ones steering the products in democracy-breaking directions.
If yes, Kubernetes might make sense for you, if your company is large enough that a PaaS like Heroku is prohibitively expensive.
If no, you don't want Kubernetes.
https://twitter.com/kelseyhightower/status/93525292372179353...
The optional here is probably just allowing for individual freedom. My company also had 'optional' WFH, then 'recommended' WFH, followed by total office shutdown on Tuesday.
I'm not sure you could attract top tier tech talent if you forbade working from home. It's a perk that I really enjoy because it's very convenient, and if I don't feel like going in to the office for whatever reason I don't have to. If I interviewed at a company that forbade working from home (or had very strict rules around it) I'd have to really think twice about whether I would work there. To me, it speaks to a culture of valuing employees based on whether they're merely seen to be working, rather than their actual work output.
If you need to make some scribbles to describe a project, markdown will do. All of the things in this article are valid, but they're really don't apply to barebones documentation.
If you need some more formatting and bells and whistles, then you graduate to something that supports macros and a is a more fully fledged tool (eg. Hugo). These tools solve these problems, while (generally) keeping the user-friendliness of markdown. At least if you build some sort of complex behemoth of a publishing system with macros and custom styling and all sorts of things, if somebody needs to make a small content change, you using markdown will be a saving grace.
Remote: No experience, but open to it
Willing to relocate: No
Technologies: Kubernetes, Istio, Golang, Python, AWS
Résumé/CV: https://resume.skouf.com
Email: hello@skouf.com
Interested in building internal tooling and infrastructure platforms that help devs go faster. Also a passionate teacher and mentor of Junior developers.
I'm also thankful to be able to work with passionate, enthusiastic graduates as part of my day job. Seeing them learn, grow and progress into great developers is incredibly rewarding - much more so than the rest of my work.
Firstly, I made sure that the script told you what it would do before doing it.
Secondly, my instructions are two lines. Curl to a file, then run it through bash. A compromise, but if you mistrust the script, you can inspect it yourself before running it.
If you're constantly fixing the things causing you to get pages, why are there still many more than one per day? Just prioritisation of other work over fixes?
We have a similar system, though we have one person on after hours support doing normal work during the day, and one person during the day who doesn't do normal work. That person works on remediating the issues that cause people to get paged. Leads to a pretty low number of pages.
The question you should be asking is: why am I being paged so often?
Are they legitimate things that you need to respond to? If so, you should be fixing these issues so that they don't happen again. If anyone gets a page, we make it a high priority to fix whatever caused it. We are a team of 7, and we dedicate one person a week to field questions relating to our platform as well as to fix up these issues that wake us up.
If they're not legitimate things that you need to be woken up for, why are you being woken up? If this is the case, you need to make sure everyone is on the same page regarding what constitutes something you need to be paged for after hours.
An example is databases. We offer Postgres (via an operator that provisions an RDS instance). AWS lets you choose whatever you want, and frankly at our scale and level of complexity, there is simply no reason to choose one SQL db over another other than bikeshedding. So being able to enforce Postgres, and as a result, provide a better, more managed provisioning experience (with security by default and less footguns) and training and support just for one DB type is incredibly powerful.
As Kelsey Hightower has often said, Kubernetes is a platform for building platforms. Just deploying a Kubernetes cluster, giving devs access and calling it a day is rarely the right answer. Think of it as a way to effectively provide a Heroku alternative inside your company, without starting from scratch or paying Heroku prices
Yes, quality is everyone's responsibility. But without an advocate with the right title and respect, it becomes secondary or even tertiary (behind velocity and features)
Usually the discussions around these things aren't in good faith. Sometimes they're actually in poor faith from BOTH sides. Interpret this as 'people are fallible and bad at discoursing respectfully' rather than 'people don't want to discuss these sensitive topics'