1
point
lazzurs
Joined 62 karma
- lazzurs parentA physical keyboard like a Treo/Palm Pre, enough storage to store all my photos and say GrapheneOS and I would be in.
- Sir Leon Bagrit covered this topic in the first BBC Reith Lecture and it’s worth a read/listen if you’re interested in this topic.
https://archive.org/details/ageofautomation0000sirl/mode/1up
- What sort of people get O-1 visas? I assume it is people with multiple degrees and have decades of experience in a specific field?
I am good at what I do, have done public speaking at major conferences on what I do but no degree and so assume that i've no chance of ever getting into the USA. Currently a UK citizen living in Ireland.
- A man has died, that is sad.
Under his watch he did not move the church to fully acknowledge or deal with the historical and widespread abuses the organization he led was involved with. He had opportunity to be the leader to bring the organization around and he did not. Let's all hope his replacement will.
- Location: Ireland
Remote: Yes
Willing to relocate: Yes, for something interesting
Technologies: Terraform, Ansible, Docker, Kubernetes, AWS, Azure, Jenkins, ArgoCD, Tekton, DevOps/SRE/Platform Engineering, Linux
Résumé/CV: https://www.linkedin.com/in/lazzurs
Email: rob@lazzurs.ie
- Importing from the state would be good.
Doing this with resources is going to be the easy path. Translating the state representation of re-usable modules I expect is going to be more difficult but necessary for the migration path to be useful. A lot of power in Terraform is being able to stack re-usable components, say an internal module representing a service on top of a public module that provides sensible defaults like the terraform-aws-modules collection which then sits on top of resources.
If you can get this to a place where an existing deployment of Terraform modules can be imported into SI as a collection of re-usable templates and then users can easily deploy n+1 of those templates the same way they would do with Terraform I think you will have an easy migration path.
If not importing from the state at least some way of automatically importing those re-usable components and allowing the deployment of n+1 of a reusable component would be helpful to migration from existing patterns.
- 5 points
- I've been an early user of Infracost and I cannot recommend it enough. It being in the CI/CD system is good but it being in the IDE is excellent. Cost is an important architecture concern and yet it's one of the most opaque things to deal with. This IDE plugin for Infracost fixes cost being opaque.
Excellent work, thanks for this.
- This is lovely and all but seems rather pointless.
If we are so close this is something that’s required then it’s already too late and very likely we are all under the influence of SuperAI and don’t know it. So much of the advanced technology we have today was around for so long before it was general knowledge it’s hard to believe this wouldn’t be the case with SuperAI.
Or it’s not close at all and so back to my original point of…this is pointless.
I do hope I’m entirely wrong.
- I have an EcoTank and it is great and I would recommend it to anyone but there is a small catch of the maintenance box which is where ink goes when cleaning is being done inside the printer. If you don't print often you are more likely to use the maintenance box.
I have not looked at how easy it would be to clean out, reuse and reset the box but I suspect it is possible.