Contributing to Griptape: a modular open source framework

how does it feel when you get the appreciation of your code you contributed in Open source projects like Cal.com, Inc. 🚀🚀 The mistake I used to do in open source contribution is - Randomly picked one issue and started solving it without any knowledge of the code base. 🤒 - My suggestion is to please give some major time to understand the code base before you jump to resolve any issue. give your time to Docs📑, trust me it helps in long run✅🚀🚀

😊 Exciting Announcement 🎉 🎊   I've Created My First Gem - "swagger_autogenerate" I'm thrilled to announce the release of my first Ruby gem 😍 , called "swagger_autogenerate"! This gem is designed to automatically generate YAML-based API documentation (swagger) directly from your RSpec test cases 🎉.  As developers, we all know how important it is to have up-to-date and accurate API documentation. However, manually maintaining this documentation can be time-consuming and error-prone😩. That's where my new gem comes in 💪 . With "swagger_autogenerate" 😎 , you can streamline the documentation process by leveraging the power of your existing RSpec test suite. The gem analyzes your test cases and automatically generates a Swagger/OpenAPI-compliant YAML file that describes your API's endpoints, request/response structures, and more. This not only saves you valuable time and effort but also ensures that your documentation stays in sync with your actual implementation, reducing the risk of inconsistencies and outdated information. I'm excited to share this tool with the Ruby community 🤟 and see how it can help developers like you improve the documentation and maintainability of your API-driven applications. If you're interested in trying out "swagger_autogenerate", please feel free to check out the gem on RubyGems.org or explore the project on GitHub. I'm always open to feedback, suggestions, and contributions, so don't hesitate to reach out 💝 . gem url: https://lnkd.in/dcBGGCaK Github repo: https://lnkd.in/dEE-4QvW

The Challenge of Maintaining Open Source Projects: Why Your Project Might Not Be Used in the Future We usually kick off (or get involved in) open source projects because we have a need and believe our problem, in an abstract form, could also solve issues for others. We’re driven by endorphins (or whatever kind of motivation) and start cranking out code like there’s no tomorrow. However, it doesn’t take long to realize that just focusing on the code isn’t sustainable. We need proper documentation to help people use and chip in on the project. After months of working "solo", a few folks might show interest – that’s when the repository transitions into a true open source project. ...full text link in the comments!

For the past 7+ years, those of us at Tidelift have been hard at work trying to make open source work better for everyone, especially those that create + maintain open source projects and the enterprise organizations that benefit from these maintainers' work. Today, a new chapter begins. 📙 Tidelift has signed a definitive agreement to be acquired by Sonar, the leading provider of code quality and security solutions. For Tidelift and Sonar customers, this will be a powerful combination. Both organizations have deep open source roots, a developer-first focus, and a shared interest in proactively improving the quality and security of code. With the addition of capabilities from Tidelift, Sonar will be able to help its customers analyze, improve, and secure all code, including code written by developers, AI-generated code, and open source libraries. There will be a lot more to say on this in the weeks and months ahead, but in the meantime, I'd encourage you to go read the press release on the Sonar website, and then you can check out our CEO Donald Fischer's blog post, both linked in the comments.

Two mistakes many developers make with side projects: 1. Don't add README 2. Don't deploy them to internet Recruiters don't understand your code, and won't pull it from GitHub and run it locally. Explain the domain in the README. Make a demo publicly available. Don't just code; communicate. Let your project be a story, not just a repository

Two mistakes many developers make with side projects: 1. Don't add README 2. Don't deploy them to the internet Recruiters don't understand your code, and won't pull it from GitHub and run it locally. Explain the domain in the README. Make a demo publicly available. Don't just code; communicate. Let your project be a story, not just a repository.

Ever wondered how to handle system-native integers like a boss? 😎 Here's a little snippet I recently shared on GitHub that helps you manage nint across both 64-bit and 32-bit systems. 🔥 Why this matters: Seamless support for both 32-bit and 64-bit systems. Effortless array indexing using nint and pointers. Plus, who doesn’t love a neat native type trick like this? 👉 Curious to explore the full code? Head over to [https://lnkd.in/dEMT2YMB] and dive into the details! 😄 Happy coding, and let me know what you think! ✨ P.S. If you’re also obsessed with system-level optimization, hit me up! Let's geek out together. 🚀

🚀 Exciting News! 🚀 I’ve just published my first npm package: 🎉 DirKit – a powerful CLI tool for effortlessly managing directory structures! 📅 This project has been on my radar for a while, but I officially kicked things off at the start of this month. The past few days were all about getting core functionalities in place. I know there are bugs and improvements that will be needed – this is my first npm package, and I'm learning a ton along the way! 😅 What is DirKit? 🤔 DirKit helps developers: 🗂️ Visualize folder hierarchies 📁 Effortlessly handle directory structures (working on it currently) 🔄 Export directory trees for easy reference (future scope) This is just the beginning – I’m excited to roll out more robust features soon! 🛠️ What I’ve Learned Through this ongoing journey, I’ve picked up some crucial skills: - 📝 File Handling in JS/TS: Handling files and directories in Node.js was a learning curve! - 📦 Publishing to npm: Finally, I’ve learned how to push packages to npm and make them available to the world. - 🔧 JavaScript/TypeScript Classes: Still grasping the ins and outs of classes in JS/TS – something I’m diving deeper into. 🌟 It's been an amazing experience so far, and I’m eager to improve DirKit with your support and feedback! 🔍 Try It Out Now! https://lnkd.in/gfRG7cg7 If you have ideas, bugs, or just want to say hello 👋 – drop a comment below! Currently, it is not open to contribution. After i create a base then contribution will be open Let’s collaborate in future and make DirKit even more powerful together! 🚀 #npm #CLItools #OpenSource #DirKit #DevLife #SoftwareDevelopment #TechCommunity #npm

Tomorrow (13th August) I will share my vision on documentation during the meetup of PHPAmersfoort. I think many development teams are doing it wrong and can improve. I will tell you how to write less documentation, but get more. Curious? Join me: https://lnkd.in/eM7vjW3g

Just submitted «Scaling IaC: OpenTofu, Terragrunt & GitHub Actions» proposal to the #OSSummit. If you have use-cases you'd like me to cover in the presentation, reply 👇. P.S> There is less than 24 hours left to submit your proposals ⏰ #iac #terragrunt #terraform #opentofu #github