Connects Strava in Discord and reposts athlete and club activities into Discord channels, including time, distance, pace, map and weather. Open-source at https://github.com/dblock/discord-strava.
I am sorry you had this experience. No approach, closed or open, will ever substitute better leaders that aren’t taking advantage of you. Your experience is likely and sadly very common.
Joey who opened https://github.com/artsy/README/issues/427 is one of the best 10x engineers I’ve ever had the privilege to work with. If it’s important to him to rename all branches from “master” to “joey” I’d add my plus 1.
We failed early. Had a wonderful demo day. Tons of sign ups. It started getting a bit long. Someone decided to shorten each session (max 2 minutes) and choose which ones were worth demoing. So you basically asked for permission to demo. Sign ups stopped. Nobody wanted to demo anymore. Demo day died and took a year to restart properly.
In general, establish “how”. Everything is in writing and GitHub workflow. When someone says “can I?” the answer is “why are you asking and haven’t done it (submit PR) yet”? This moves permission to a public discussion.
Think in terms of must have, should have, nice to have, not allow/disallow.
Managers already have the power to veto, so they don’t need to approve, allow or disallow. Managers need to say that to everyone all the time - “you have an idea, why haven’t you done it yet?”.
Everyone needs to do things very visibly and over communicate to enable gentle redirects and avoiding getting to veto.
Losing control is hard. Communications team wanted to review and control the engineering blog. I said hard no multiple times with every new comms leader. Asked them to comment on PRs.
Don’t fix problems that don’t exist. If someone wants a knob that looks like permission, ask them what problem they are trying to solve.
tl;dr The README became possible because Artsy is open-source by default, and someone just decided one day to create a repo and some content, and didn't need permission to do so. It's also the repo that most new hires read before they even apply to the job, and they don't need permission to make changes either. GitHub workflow is how everything gets done.
As someone who works on an open-source fork of the open-source software mentioned in the post, I am now exclusively referring to the open-source version of it as Apache (APLv2) -licensed. Maybe that's how we fix this confusion?
This is extremely shortsighted. Educated people are a lot harder to exploit. One of these students might one day lead the kind of change we’ve seen in numerous examples through history.
I grew up in the USSR. There were multiple layers of the system. I was somewhere in the middle with my father being a well known poetry translator and grandfather writing propaganda. We listened to the BBC and Voice of America without reprimand, because of our status. Neighbors would face serious consequences for this. At 12 I was sent to the US to understand how capitalism is harmful. I think North Korea is making the same bet of creating a system in which some know all the truth and still work for the regime.