stories
alpha-versioning
| stories | alpha-versioning | |
|---|---|---|
| 14 | 1 | |
| - | 0 | |
| - | - | |
| - | 10.0 | |
| - | over 3 years ago | |
| TypeScript | ||
| - | GNU General Public License v3.0 or later |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
stories
-
Finish Your Projects
> Tangentially, I'm curious if you could speak to what it's like creating content as a third party author? Are you given prompts regarding the tone or content of your work?
Happy to share! The first piece I wrote for GitHub's ReadME Project was called "Publishing your work increases your luck" (https://github.com/readme/guides/publishing-your-work) and I was able to write it as a result of an interview I did with them previously.
Before I wrote that first piece, I reached out to the ReadME Project and told them that I had wanted to tell the story of my past year of overcoming fear and embracing putting myself out there. They agreed that that fit in their "developer stories" section and did an interview of me, which they published here: https://github.com/readme/stories/aaron-francis.
After that they reached out and said "sometimes we have our developer stories have a corresponding guide, do you want to write one" and so that's where the Publishing guide came from. I wrote it all for them and then they have a full on team of editors, proofreaders, illustrators, etc to help push it over the finish line. Before I wrote it I gave them an idea / outline of what I was gonna say, to get the green light. Their editing has been very light, more flow than content. Like... move this sentence up; you repeated yourself there. That kinda thing.
The only time I had a piece really torn apart was this one https://handsontable.com/blog/modularizing-to-improve-the-de... and it was because my voice just didn't fit their blog at all. What you see on the site there is about 35% of what I originally wrote before it was completely toned down. It happens though! It's their blog, so it's gotta fit their voice. (Coincidentally that was the last piece I wrote for them. Ha!)
- Putting the African open source community on the map
- Out of the Slums and into Open Source
- Raising the bar for open source standards
- Sometimes They Say Yes
- When I reflect on what motivated me, it felt like I was contributing to the commons and advancing human knowledge. I felt like once I write this code, no one else will ever have to write it again.
-
Cambio a rubro IT a los 29 años
I didn’t start programming until I was 30.,,
- Marcy Sutton - Making accessibility in tech the rule, not the exception
- Hoppscotch’s maintainer builds open solutions for all
alpha-versioning
-
Finish Your Projects
One way to make sure (some) projects get finished is to not use semantic versioning, 1.0.0, 27.8.3, and so on, since integers can be incremented longer than the average lifespan, and instead use something like alpha-versioning [1] which starts at 0.0.0-0 and ends at 1.0.0-0, that is, reaching 1.0 is actually the death of the project, its tombstone saying non perfectus sed perfectibilis non amplius (Latin for gravitas: not perfect, but perfectible no more).
At the other end, having goals which extend well beyond the average lifespan is what could be considered as the root of wisdom.
[1] https://github.com/ly3xqhl8g9/alpha-versioning#answers
What are some alternatives?
krell - Simple ClojureScript React Native Tooling
https-basic-auth-go - A template for using HTTP Basic Authentication in Go
guides