It must have been somewhen 2009 that I had my first account with Twitter, Inc. I was not really sure what to do about it. How can you have a serious conversation or share useful information when you are limited to just 140 characters? Somehow this service still felt relevant.
Over the years, it became increasingly valuable. It enabled me to follow amazing people, to read enriching discussions, and to benefit a lot from the shared knowledge, opinions, and all the useful pointers to stunning resources on the Internet. Not only for me personally, but also on a professional level. At some point in time, I came to the conclusion to close all other social media handles – namely orkut, StudiVZ, Facebook, LinkedIn, Xing – as compared to Twitter, the output was close to zero and I wanted to focus on what became helpful to me.
Yet, my own contribution to the dialogue remained little. I tweeted about new additions to my online presences, took part in a few conversations, and mostly re-tweeted quite some stuff that I either considered worth getting the required attention or which I just appreciated to being pointed at.
All the time I did not feel that comfortable of the fact that I am the actual product, as its service remained free of charge. Is a “Like” already way too personal, so they’d be able to precisely profile me?
I highly value everything that the Twitter staff has done to make the platform the way it came to be … was.
Now is time to move on. The Fediverse is in every dimension much more close to what I was originally looking for. And I have found my way to get there.
So long, Twitter – Inc. and its community … thanks for the amazing ride, you definitely made history!
A few days ago we just got yet another reason to leave centralized, a-social networks behind. You probably do not want crazy billionaires serial innovators to reinnovate your virtual neighborhood without mercy. Aside of that there are the secret timeline algorithms, of which is little known beside that they primarily amplify hatred and biased, extremist opinions for the sake of maximizing impressions, users’ interactions, and platform revenue. At the same time one’s own personal timeline is being polluted and tampered with all kinds of paid advertisement whilst the underlying personal data of each and every user is generously sold in all directions.
But wasn’t this all suppose to be just about “… connecting with friends and the world around you”?
Exactly. But for that we have the Fediverse and when it comes to microblogging there is Mastodon. As you probably have already heard about those, let’s directly dive into organizing your Twitter exodus step by step.
Last week GitHub and its parent company Microsoft announced“GitHub Copilot – their/your new AI pair programmer”. E.g. The New Stack, The Verge or CNBC have reported extensively about it. And there is a lot of buzz around this new service, especially within the Open Source and Free Software world. Not only by its developers, but also among its supporting lawyers and legal experts, although the actual news is not that ground breaking, because it is not the first of its kind. Similar ML-/AI-based offers like Tabnine, Kite, CodeGuru, and IntelliCode are already out there, which have also been trained with public code.
Copilot currently is in “technical preview” and planned to be offered as commercial version according to GitHub.
The core of it appears to be OpenAI Codex, a descendant of the famous GPT-3 for natural language processing. According to its homepage it “[…] has been trained on a selection of English language and source code from publicly available sources, including code in public repositories on GitHub”.Update 2021/07/08: GitHub Support appears to have confirmed that all public code at GitHub was used as training data.
Great, in what amazing times we are living in! Sounds like with Copilot you do not need your human co-programmers any longer, who assisted you during the good old times in form of pair-programming or code review. Lucky you and especially your employer. On top you will save precious time because it will help you to directly fix a bug, write typical functions or even “[…] learn how to use a new framework without spending most of your time spelunking through the docs or searching the web”. Not to forget about copying & pasting useful code fragments from Stackoverflow or other publicly available sources like GitHub.
At the same time, two essential questions arise, in case you care a bit about authorship:
Did the training of the AI infringe any copyright of the original authors who actually wrote the code that was used as training data?
Will you violate any copyright by including Copilot’s code suggestions in your source code?
Let’s not talk about another aspect that GitHub mentions in their FAQs – personal data: “[…] In some cases, the model will suggest what appears to be personal data – email addresses, phone numbers, access keys, etc. […]”
The results of the Open Source Impact Study tasked by the European Commission have been widely discussed mainly because of its numbers. Though being announced just now, the study identified for the year 2018 a contribution of 0.4% to the GDP worth EUR 63 billion by FOSS, if measured by the increase in commits. 10% more contributors would even raise the GDP of the European Union by 0.6% (EUR 95 billion). The overall cost-benefit ratio is estimated with at least 1:4.
But it gets even more interesting, when looking into the results of the accompanying survey covering about 900 stakeholders (mainly companies) from all around Europe.
For them, incentives for using and investing in Open Source have been, sorted by relevance:
finding technical solutions
avoiding vendor lock-in
carrying forward the state of the art of technology
As benefits they have seen:
support of open standards and interoperability
access to source code
independence from proprietary providers of software
Within the participants the cost-benefit ratio has been estimated even with 1:10.
The current circumstances also forced conferences (those gatherings with really large audiences) completely into cyberspace. Some sticked with traditional approaches to stream talks via off-the-shelf videoconferencing applications and built upon the integrated very limited interaction features offered by these poor proprietary tools. Others have gone complete new ways and brought fascinating and well working concepts on how to still successfully connect the crowds to enable lively conversations and facilitate the exchange of knowledge and experiences in a distant environment.
Let’s start with rc3 and its virtual conference venue in form of rc3 world, implemented with Work Adventure. In a pixel-2D-adventure-style you could walk around the area and as soon as you are approaching other characters, a live audio and video stream with those humans or other live forms controlling the character would open. Limited to 4-5 persons at a time, it allowed you to talk directly with each other – face to face. Due to the limitation of participants you were still able to have a working conversation.
Somehow you needed to get used to having an unexpected and sudden interaction with one and another – on live video, but still it brought back the heavily missed opportunity to get in personal touch with other participants who are sharing possibly similar interests.
The FOSDEM 2021, the worlds biggest conference on Free and Open Source Software usually taking place in Bruxelles, had for me a very convincing overall concept. The organizers and infrastructure artists have done a tremendous job that allowed for the most impressive conference experience so far and for long. Naturally and purely based on Free Software, at its core matrix, element, and Jitsi.
How did it work and what was so great about it?
Presentations of specific areas of interest had been summarized in virtual rooms with a fixed agenda, like in most physical conferences. Participants logged into a chat infrastructure which represented the rooms by group conversations. You would simply join the room(s) that you are interested in and could start texting with each other and the speakers like on IRC. Talks had been recorded beforehand and where automatically started – by the computer (systemd) – at their scheduled time. Its audio and video were streamed right above your chat window. When the talk ended, the Q&As were streamed live for a fixed amount of time within that room until the next talk started auto-playing according to schedule. During that first part of the Q&A session of a talk, moderators where clarifying upvoted questions and comments from the chat and interacting realtime with the presenters. Those interested could then continue discussing with the speakers and further extend their conversation by switching to a separate room. So per talk you had a dedicated room for the second part of the Q&A that would open shortly after and even allowed anyone there to interact live via audio and video.
In sum that meant that you could check the schedule for topics you are interested in, connect at the announced time and be sure to really listen to that talk instead of watching tech staff doing mic checks or heavily delayed earlier talks whilst being unsure about if and when the one you came for would actually start.
In addition the highly valued Q&A and following backstage (and off the record) conversations could still take place without interrupting or being interrupted by the subsequent talk.
Just impressive and so useful! Thanks a lot to all who made this happen and work that well! These concepts are now here to stay, even when conferences will hopefully resume soon back in the physical world.
I guess we all have meanwhile learned more or less successful how to work from home (or the beach). The all-remote company GitLab Inc. has an helpful and extensive guide on how they are implementing this within their global organization – without a single office. It was inspiring to me especially during the first lockdown of the pandemic, although I thought I had already gained quite some experience during 1.5 yrs working remotely. The subsequent recommendations probably contain also advice originated from GitLab, but are enriched with my personal flavor and learnings. I hope it is useful and shall at least serve as a reminder to myself. I fear there are still some months left to professionalize this even further …
Intentionally start and end your work day. For example by a specific ritual, e.g. start with a morning walk, shower, … and end at least by closing your work related applications and their connections when you are done. Otherwise private and work life might mix too much and there won’t be any time for recreation and clearing your mind.
“Never assume the motives of others are, to them, less noble than yours are to you.” [according to J.P. Barlow] Not only a helpful advice in remote work, but especially in an isolated environment like home, certain inquiries by your colleagues might appear out of context. If the other person then even catches you in the wrong moment or mood, to have an open, impartial, and collaborative conversation will be a challenge, at least for yourself. Assume that their personal motivation for approaching you is by default meant well and make sure to appreciate it.
Do not demonize doing private stuff for and within breaks. While working from home you will most probably be more focused and accordingly exhaust more quickly. Taking a break for doing something completely different like sports, laundry, or just going to the grocery store might at first glance appear improperly. In the end it will spur your creativity and with a refreshed mind you will be more efficient within the same timeframe than forcing you to continue working just for the sake of being on duty.
Optimize for asynchronous communication. The frequency of conference (“sync”) calls naturally increases in a remote setting, schedules will overlap, and participants might not always be that focused as they are during in-person meetings. Allow others to follow up offline, at a later point in time, and help to continue where you last left off so that everyones valuable time is invested well. In addition you might want to record important conversations and at least keep detailed minutes that assist to easily catch up. Moreover prefer group conversations over direct messages, as there are always others for whom this is or will become relevant as well.
Accept external disturbances during meetings. It is just inevitable to be interrupted in your home environment. Kids, the postman ringing, or unstable infrastructure. Appreciate such unintended breaks, do the best out of it, welcome the young generation or resort the discussion as you anyhow cannot change it. And hey, those interruptions are not that much different to a beamer suddenly breaking down or colleagues bursting into a double-booked conference room?
Plan your week and set your priorities pro-actively. Otherwise your work stream will be dictated by allegedly “urgent” concerns popping in and by natural distractions due to your home environment. Better define beforehand what is really important for you to work on. It will be much more easier to resume after uncontrolled interruptions and you always have an overview of where you currently are and what needs to be done next.
Electronic mail and communication platforms like Teams, Slack, etc. are asynchronous communication channels. This might come as surprise for some. Do neither feel obliged to immediately reply nor expect a prompt reply. If there is urgency, a direct call is still well suited for instant follow-up and without wasting time by interpreting probably ambiguous text-based chats. In case of conflict, clarify your “service-level agreement” and how to reach you best in case of emergency.
Prefer video calls over voice calls. If infrastructure allows, switch on your camera. It will still bring you much closer to your colleagues and add an additional sense for improved interpersonal communication.
Fight screen fatigue. Do everything you can to not make you or your counterparts stare on the screen all day long. E.g. when you need to do something creative, better choose pen and paper. While doing a break, do not read the mails or news again on your screen. Better take a walk, enjoy some fresh air, and wide angle view. When you give a training/workshop/lesson, frequently enable participants to turn away from the conference session to do some self-responsible tasks. In general reduce frequency and duration of meetings to a minimum.
In case you want to look from a statistical perspective on home office, Atlasssian Inc. has analyzed the first months after people started to work primarily from home. The company is offering popular workflow solutions that are mainly used within software development, e.g. ever heard of Jira? Their study is a useful sample of remote work from within the software industry. Surprisingly employees still kept working although they are not at the office any longer. The author is even slightly worried of our work-life balance: “Proof our work-life balance is in danger (but there’s still hope)” by Arik Friedman.
Reports have become rare in which drivers were misled by their car’s navigation system and accidentally slipped into a river, expecting a not yet build bridge or desperately ended up on a steep mountain trail, non-suited for anything wider than a goat. In sum you would feel save to assume that nowadays route-based guidance has improved significantly and at the same time humans have learned to not always trust the machines. Most not all.