85 karma · joined July 10, 2013
It seems to me like the author is arguing that the you don't need a CTO, you need a technical co-founder, AKA a founding engineer, and that they should be given double-digit equity. Am I reading this wrong?
For a time-sensitive and critical update to core functionality, the director of operations should have been aware of the mean time to deployment for the software and put together a team to fast track it, instead of entering it into the normal development pipeline with a high priority.
Good luck! It's a lot.
In the mean-time, here’s a lunch and learn video I made to show it to work people.
It was a very fun project and I learned a lot about electricity, batteries and the pitfalls of aliexpress.
https://ised-isde.canada.ca/site/spectrum-management-telecom...
Looks like you’re charged about CAD.04 per MHz per population of the licensed area. Didn’t dive too deep but it might be viable for a small town to put something together, if they’re unhappy with the big providers.
Without any sort of detail about what brand or what it was used for and why it was a bad experience, it’s really not adding anything to the conversation. It’s just a blanket judgement on a technology that has a great deal of variation and options and uses.
If I want to feel more awake I ask Siri to change the colours of the bulbs to white. If I went to go to bed earlier I ask Siri for the colour tan and to dim the lights by 30%.
At this point I can’t imagine not having control over the colour or brightness of my lights. These things are essential for a good sleep.
Just make sure you’re not slowly recreating bad, homebrew versions of all of the nice things that Kubernetes does in an attempt to turn a simple deployment into a production ready deployment.
The problem is duplication of functionality within the cluster and increased complexity in the configuration of deployments. I want to configure a certificate acquisition process once, and plug those certificates into pods using a generic process based on annotations. I don’t want to configure it 6 times because each operator does things slightly differently. Each CRD introduces new complexity to the cluster. More opportunities for things to break. More stuff to read and learn about.
I think CRDs should be used to extend the platform functionality, not as a tool to simplify deployments. It feels a little like reworking the plumbing in your house to make the sink easier to install instead of using a wrench.
Edit: maybe we could shift left and ask the app developers to add certificate acquisition directly into the app source.