Mate, I’m not sure you’re making a convincing argument for remote cooperation here. When OP said sometimes, that is clearly the majority of cases in your book but I do read that differently.
Be kind and think of the other people in the conversation. If you want remote to work then act in a way that shows it does work.
Either case, best of luck in pushing for remote work! Cheers
I grew up online and there are people I’ve never met in person whom I can work with no problem. I have never had the need to see someone in person for work myself, but the click isn’t there for everyone.
I dislike generational thinking and this argument seems to play on those lines; I have seen some people working better remote and some working better partially in person regardless of their generation or background. Younger people are more fluent in working remotely but not everyone wants that full-time and sometimes it doesn’t work out too well either. Often working in the office is the worst so let’s make/keep remote the default.
My personal opinion is that we should do everything online which can be online and that people who need to work in person should do their best to cater for working online. It helps with climate and can help work/life balance.
Any form of communication gap is a shared gap. Both sides have to cater to make the conversation work. If OP needs face-to-face then that must be taken into account. If you want that conversation to happen you’d better care for their needs as much as they’ll care for yours. OP may have extensive experience in working with people and may have seen this need on their own end and likely on the other end too. Perhaps even only on the other end. On the spectrum of cooperation I’m sure there will be cases where it helps and perhaps even be necessary. I believe it’s a small subset of situations.
By all means, try to stay constructive and learn from others. Whatever they have learned in the past likely applies to our new ways in another form. I would like it if we could keep improving remote.
I don’t think Xerox invented the computer mouse. It was first drawn out by Douglass Engelbart and presented to the public in the 1968 presentation “Augmenting the Human Intellect” (you can watch it on the present day, it was recorded).
It was my understanding (which I did not verify) that this was picked up by Xerox and others and that windowing systems evolved from there on with Xerox leading towards Desktop Publishing.
This must be from another timeline. Sorry for the inconvenience, please skip.
User focused applications running on my own internet accessible infrastructure fully based on open standards and interoperable with the Fediverse… Yes please
I’m looking forward to play with this.
You could find out about the way we do it at https://github.com/madnificent/docker-ember but I would not if I were you.
The real risk, today at least, does not seem utterly huge. Jumping in this rabbit hole of containers is another topic in itself. I suggest continuing your learning as you do now and maybe revisit this later. You will learn faster that way.
Feel free to check what we did on the link above and ask questions later or whenever you feel ready for this topic.
You shouldn’t eat candy given to you by strangers. If you’re in a large group and someone knows the candy, maybe. Code is food for your computer. Be wary. Our large Open Source group of friends has learned about many kinds of candy and shouts loudly when some in the group becomes ill. You don’t want to become ill. Some risk exists, but with a large group it is generally ok. Don’t install packages as root, don’t install what you don’t need.
I run my frontend builds through Docker (also during development). By isolating access to the host system to the files/folders necessary for development I’ve shielded off the majority of current realistic attacks I’ve seen as NPM based exploits. I’m certain the approach can be replicated for other frameworks, but we use Ember and docker-ember. I doubt it runs as smoothly on a non-Linux OS.
Water also needs a substantial amount of energy to evaporate, hence it will sip some heat from the environment around it when it evaporates. Combined with the good thermal conductivity of steel, the bridge cools off.
You get a similar effect when walking out of a hot shower. The hot water evaporates and cools you down.
Mercedes’s stars have been on springs for decades indeed. You can easily push them over (but make sure you put it back nicely). I think Rolls Royce’s Spirit of Ecstasy pops back into the hood but I don’t know how that works on impact.
I write my notes in org-mode. It’s supported in many editors in a basic form, letting you add code snippets etc in an unobtrusive way. Using a well thought out format helps you in the long run.
I use this in Emacs, through which it lets me refer to emails, execute code snippets, attach related files, fetch content on/from remote servers, send off the debug session as an html email, … Support will depend on your editor but even as raw text it works.
I don’t use something specific to make non-code repeatable as you suggest here, but you could embed a test language in an org code block.
The syntax is straight-forward and exports to multiple external formats exist (eg: html).
Nice script. What is the reason to toggle the brightness?
Kubernetetes is crazy complex when comparing to docker-compose. It is built to solve scaling problems us self-hosters don’t have.
First learn a few docker commands, set some environment variables, mount some volumes, publish a port. Then learn docker-compose.
Tutorials are plenty, if those from docker.com still exist they’re likely still sufficient.
Emacs: “What if your Operating System and your text editor had a child.”
I am waiting for federation to land. Would love to give it a spin and see how smooth that works across instances.
https://browse.feddit.de/ has helped me discover some good subs
Looks good to me.
docker-ember largely automates such a setup with specific mounts for linking node modules from other folders, being able to bind to localhost for when you run the backend on your own machine, and exposing ports for livereload. May include other secret sauce. Some of that is closely tied to EmberJS.
I’m a fan of using tools you understand. What you show here is comprehensible and sufficient for now👌