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
guides
- What we talk about when we talk about 'root cause'
- The case for using Rust in MLOps
- Using code as documentation to save time and share context
- Publishing your work increases your luck
-
Pest-Driven Development: Learning, Iterating and Project Planning
Write a more complicated test later. Or refactor the test later. When you're in the moment, you want a test that works. Avoid hard coded values in completed tests, but use them when you're making sure your test doesn't break the very time you write it. A failing test is the starting point of the last decision you made, not the final product. Even if the imaginary people who are going to make fun of your code and call you stupid (ignore this if you're not relating, but if you are read this or watch it) are looking at your public github repo, they're not going to your test suites first. That would be insane. So you can be clunky at first.
- Formatters, linters, and compilers: Oh my
- Two years into this career and already frustrated and burnt out (rant)
- Treat accessibility issues as bugs, not feature requests · GitHub
What are some alternatives?
krell - Simple ClojureScript React Native Tooling
viewi - Unique and efficient front-end framework for PHP
https-basic-auth-go - A template for using HTTP Basic Authentication in Go
azure-dev - A developer CLI that reduces the time it takes for you to get started on Azure. The Azure Developer CLI (azd) provides a set of developer-friendly commands that map to key stages in your workflow - code, build, deploy, monitor, repeat.
virtualcoffee.io - Public site for Virtual Coffee
azfunc-openapi-on-root - This provides sample codes to show Swagger UI on root (/), instead of /api/swagger/ui
AzurePolicyTestFramework - A command line tool to test Azure Policy relying on Terraform + Golang
gobyexample - Go by Example
bom - A utility to generate SPDX-compliant Bill of Materials manifests
dev-community - Azure Developer Community
github-commit-visualizer - Visualise your dev work in graphical form with this GitHub Visualizer
iot-with-dapr-actors - Example of how you can build IoT solutions that have custom device gateways that are using Dapr Actors to represent devices in the field.