GitHub Community
The ReadME Project is up for discussion! #55584
Replies: 3 comments 1 reply
This comment was marked as off-topic.
This comment was marked as off-topic.
-
|
Where do you think we should explore in the coming months? Hey 👋👋👋👋 Here are some of the topics you could expound on... ✍️ DevOps and Site Reliability Engineering (SRE): Focus on the operations side of things by exploring DevOps practices, SRE methodologies, and how they contribute to building scalable and reliable software systems. ✍️ Serverless computing : Shed light on the serverless paradigm, its advantages, and practical use cases. Discuss the major serverless platforms, architectural patterns, and best practices. ✍️ Progressive web applications (PWAs): Explore the concept of PWAs, their benefits, and how they are transforming web development. Showcase successful PWA implementations and provide guidance on building PWAs effectively. ✍️ Microservices architecture: Delve into the world of microservices and discuss its benefits, challenges, and best practices. Explore popular frameworks and tools used in building and deploying microservices. ✍️ Data engineering and analytics: Explore the realm of data engineering, data pipelines, and analytics. Discuss different data processing frameworks, data lakes, real-time analytics, and the impact of data-driven decision making. |
Beta Was this translation helpful? Give feedback.
-
|
Thanks for sharing, @KambonoJeff! 👍 One place to keep an eye out for our stories in this general realm is the DevOps topic on The ReadME Project. Many of these are realms I've been watching for the last several years, so I'll definitely keep them in mind. On the DevOps/SRE end of things, I wonder - did you catch my featured article about GitOps earlier this year? And for the above suggested topics, do you happen to have any favorite open source projects that you like to pay attention to? |
Beta Was this translation helpful? Give feedback.
-
Hey folks! 👋
@mikethemelanson, senior editor with GitHub’s The ReadME Project, here to let you know that we just published our May edition (including two featured articles by yours truly), and we wanted to give you the highlights and invite your thoughts and feedback!
This is our first post here on GitHub’s Community Discussions, but we expect many more to come. The ReadME Project is a GitHub platform dedicated to highlighting the best from the open source software community and we want to hear directly from you about the topics you want us to report on, questions you have, and folks within the software development community that you would like to learn from. If you want to find more of our posts here, just look for us using The ReadME Project label.
In May’s first feature story, I explored the idea of contributor relations in open source by looking at the story of the open source project that closed itself down entirely to code contributions, from features all the way to bug fixes. I not only spoke to Ben Johnson (@benbjohnson), the maintainer of that project, but also open source advocate Julia Ferraioli (@juliaferraioli), developer Shawn Wang (@sw-yx), Prometheus maintainer Bartek Plotka (@bwplotka), and Roberto Ierusalimschy (@roberto-ieru), one of the creators of Lua, to find out how open source isn’t one size fits all.
@benbjohnson on why he chose to close his project to code contributions:
”Even small contributions typically required hours of my time to properly test and validate them. I am grateful for community involvement and when folks report bugs or suggest features. I do not wish to come off as anything but welcoming, however, I've made the decision to keep this project closed to contribution for my own mental health and long-term viability of the project.”Next, I met Paul Chiou (@oikos99), a developer pursuing his Ph.D in computer science who builds software to automatically detect and fix keyboard accessibility issues. The thing is, Paul is paralyzed from the neck down and can't use a physical keyboard - instead, he designed and built custom hardware and software to act as his mouse. When Paul wants to do something like use a computer, or perhaps play some Dota 2, he gets creative. Beyond creativity, Paul is working to make the world more accessible for everyone.
Paul on accessibility as a developer:
“I believe every software developer has the obligation to make the software they create accessible. Just like software testing is important, and no developer would deploy their products without testing for bugs, I believe the same should be applied to accessibility bugs.”We also dive into TypeScript tooling, building software with generative AI, and using GitHub Copilot for MLOps, TDD, and more - check it out!
❓We’re always looking for new topics to write about, and we want to hear from YOU. Where do you think we should explore in the coming months? Do you want to hear more about how to use GitHub Copilot? How about GitHub Actions? Or are there certain programming languages or paradigms you’d like to hear more about? Or perhaps it’s time to dive into the back end and get into the operations side of things? Where should The ReadME Project team explore next?
To get the latest stories, articles, and best-practices from The ReadME Project delivered directly to your inbox, subscribe to The ReadME Project newsletter.
Beta Was this translation helpful? Give feedback.
All reactions