All data entered in to Google sheets becomes property of Google. Cross referencing the data in your sheets with the data it collects from its other various spy programs is probably trivial for Google.
You're just skipping the app and handing it directly to the ad company.
Thanks for including transgender as an option but users should be able to choose both male/female/non-binary and transgender/cisgender. I identified myself as transgender in the survey but I would have preferred to ID as transgender woman.
Do a simple app in each one and see which one you like best. Something like a todo API or something like ls, cat, or grep. Doesn't have to be perfect or anything just enough for you to get a feel for the language. Preferably something with dependencies outside the stdlib since managing dependancies is something you'll have to do anyway so you may as well see how it is before you get a bunch of them.
k8s is ready. If your company is just starting up it's probably not ready for k8s.
Unless you're a PaaS company with a large SRE or Ops team off the bat you likely own't have the resources to maintain a k8s cluster. It's a great piece of tech but it's quite complex and has a decent amount of overhead. So unless you happen to have an expert already on your team or your already have a bunch of services it's probably not worth the effort.
There is a "standard" REST interface described in the paper on REST. There are a lot of rules/guidelines for a RESTful API but many API's don't follow them and tend to be a mix of REST and JSON RPC.
> I feel like it requires a full-time devops engineer to create and manage all of it.
It does.
Kubernetes is a great piece of tech but it is pretty complicated and does add a fair amount of overhead on top of whatever operational concerns you application already has. If you don't have anyone that knows how to build and manage a cluster going to production with it would be extremely risky IMO.
I would recommend trying GKE, Google's managed k8s service, in staging/dev before even considering it as a serious path forward. If you are married to AWS or just don't want to use GCP then kops would be your best bet. I have friends working with EKS, AWS' managed k8s service, and it doesn't sound anywhere near as ready as GKE or as flexible as doing it yourself, frankly it sounds like a real pain. I haven't used k8s on Azure but I have heard that it's pretty good.
I also don't generally recommend deploying a new application as decomposed services either. Unless you have done this a bunch of time it will probably save you a bunch of time to just do it as a monolith and deploy it to standard cloud VM's or on-prem servers. Also be aware that Docker and by extension k8s are not the best way to run stateful applications. It can be done but it is definitely more work to get a k8s based DB working the same way as a non-k8s DB in terms of data retention. I imagine a complex application will need some kind of data store so even if you go with k8s you may still end up with non-k8s instances for you data.
k8s is great but it's overhead con easily outweigh it's benefits if you don't have a someone who can manage it. Start simple if you can and work from there.
> They are OCD. Not only do they need to know the how, but they need to understand why...and they won't stop until they have figured out the why. This helps in many situations from understanding standards, debugging odd bugs, selecting a good stack.
This isn't Obsessive Compulsive Disorder it's being thorough or knowledgable. No need to further the misuse of this term here.
You're just skipping the app and handing it directly to the ad company.