Rule #1 #1
Get it out of email.
Certified AWS Cloud Architect, Professional; an Operations Engineer.
Get it out of email.
Being away from a project costs more the longer you are away from it. Mind bit-rot.
There isn’t any way to describe it to someone who hasn’t lived it. Now it’s a thing. Zero to one.
When the ‘pawn’ reaches the other side, the pawn becomes whatever it wants.
The most important piece of gear for remote work is a headset. Without it, good comms are always a struggle. Comms are important. Not just for the headset wearer…but those who listen.
Very interesting the more you look into it.
https://www.schneier.com/blog/archives/2011/05/bin_laden_maint.html https://www.schneier.com/blog/archives/2013/10/air_gaps.html
Remote work increases the labor pool. Get ready to COMPETE.
Meta-content allows the audience to experience a new set of emotions. The emotions shared by the content-consumer and the meta-content-consumer are: higher order, more natural, and more realistic.
This is impossible with legacy content.
There is not much to say on the technical front. A few things to note are cloud expansion, coupled with office contraction. Add in a desire for freedom and innovation will happen.
Switching between multiple customers requires, by definition, context switching.
Context switching is the ‘movement between two unrelated tasks.’
Movement between two unrelated tasks is defined as a set of more than one ‘todo list items that crosses between functional domains’.
A todo-list item that crosses between functional domains are two separate todo-list items that are between two customers, two distinctly different IT technologies, two different tool-sets, or some combination thereof.
I’ve heard this, and worked through it, and felt the same way, and consider it part of ‘general purpose’ developer workflow now.
In remembrance.
This is simply missing the “10x” factor. Describing how two applications talk and the path between them is trivial. We don’t crawl anymore.
In all fairness to them, packer is good: https://www.packer.io/intro/why.html