This is very interesting, when I was a kid I didn’t think with words but with “abstract” ideas. When I realized every other kid used language for thinking I tried to do it myself and not only I was able to do it, but it never stopped after that. Now I probably think 90% with language, but I’ve been trying to practice other forms of thought recently.
One of the most challenging things I find in life is explaining to a non-programmer how I visualise code. Because I don't really know how I do it; it is simultaneously grammatical and architectural, and a lot of the processes that guide me are really emotional or almost visceral. Code sometimes does not feel right.
I haven’t tried svelte which is highly popular here but I tried vue 3 and composables really clicked with me. The composition API gets along really well with the reactive System and I love it.
I am afraid of getting started, I have read playbooks before and they look understandable but the idea of setting up the tools scares me. I’m starting to think this is PTSD from how hard installing anything was back then and now trying anything new is hard even if the entry level for everything has been lowered significantly.
Ansible has a very low barrier to entry in terms of dependencies that need to be installed into the machines you want to manage: they need to have python 2.6+ or python 3.5+, and you need to be able to connect to the machines over ssh.
One way to get started could be to initially ignore ansible playbooks, just install ansible onto your control machine. Write an inventory file with one or more hostnames of machines you want to manage. See if you can get ansible to connect with ssh and "ping" all the machines. Once you're comfortable with executing one-off commands through ansible, the jump to ansible-playbook will be smaller.
> Ansible has a very low barrier to entry in terms of dependencies that need to be installed into the machines you want to manage: they need to have python 2.6+ or python 3.5+, and you need to be able to connect to the machines over ssh.
I understand what you're saying but do understand that to other people these can be concepts that they arn't familiar with or might actively struggle with
That said - were there any obstacles you faced when you started with Ansible?
What could have been better (tooling/docs/training/etc) to get you upto speed better/faster?
This is after one day of interacting with Ansible. I did have previous experience with Linux and setting up Circle.ci projects and Dockerfile. There are not many concepts to grok. I just cloned a playbook on GitHub and tried to rewrite it to fit my needs, reading documentation over the part I did not understand well. No book or video tutorials were needed.
docker swarm is a good alternative for you then, comes out of the box with docker and you only need to add a few lines to your docker compose files to make them swarm compatible
it has, I haven't used an index but for oculus it works pretty well, Im always surprised as how well it remembers the area. Also pretty handy to recenter yourself, you just extend your arms in all directions and if you are near the edge you will see the boundaries. On the quest 2 you can even see through when you poke your head out of the limits and you can see everything around you.
There's an excellent "beta" / experimental feature on the Quest2 that you can double-tap on the side of the headset and it'll turn on pass through mode. This has been immensely helpful to me for recentering myself.
