You can add location information to your Tweets, such as your city or precise location, from the web and via third-party applications. You always have the option to delete your Tweet location history. Learn more
Companies will learn a lot about themselves from having everyone work from home. Some (e.g. GitLab, obviously) will do fine. Others will be brought to their knees. The latter will have to make changes, and some of those changes will be permanent.
It will be like re-implementing a program in a new language. They'll discover big chunks of dead and duplicate code.
It might be a good idea, within companies that are large enough, to assign a specific person to study what can be learnt from the experience. It's an ill wind that blows no good.
They will save a lot of money and question the status quo.
This is a good analogy.
Call it the way it is. They'll find useless redundant people who are at work just to make up the body count...
Advice from experience: Don't follow most online advice on going async & that stuff. I believe another way has higher *chance* of success. Article on failure from async remote: https://www.linkedin.com/pulse/why-being-remote-company-doesnt-work-egypt-nono-ghannam/ … My ~9mo of experience & years' experience of team:https://dev.to/hossameldeen/let-s-make-remote-work-mainstream-remote-work-for-synchronous-verbal-communication-based-teams-1fee …
Disclaimer: The remote-unfitness article I've linked to, its title doesn't say it's failed because of async. But in my interpretation, it was because of async. The comment & replies here may be useful as well: https://www.linkedin.com/feed/update/urn:li:ugcPost:6634773971982258176?commentUrn=urn%3Ali%3Acomment%3A%28ugcPost%3A6634773971982258176%2C6634985027530698752%29 … And yes, has nuisance, but tweet limit.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.
