add 2 new blogs

src/content/post/first_pr.md

@@ -0,0 +1,72 @@
+---
+publishDate: 2023-10-15T20:22:00-05:00
+title: A Guide to Crafting an Excellent First Pull Request on GitHub
+author: anonymous
+description: A Guide to Crafting an Excellent First Pull Request on GitHub
+image: /images/tools.jpg
+category: Education
+tags:
+    - git
+---
+
+## A Guide to Crafting an Excellent First Pull Request on GitHub
+
+GitHub, the world's leading platform for collaborative software development, is a hub of innovation and creativity. Making your first contribution through a Pull Request (PR) can be a thrilling experience. Whether you're a seasoned developer or just starting out, this guide will walk you through the steps to create an excellent first pull request on GitHub.
+
+### 1. **Select the Right Repository**
+
+Choosing the right repository is crucial. Opt for one that aligns with your interests and skill level. Look for repositories labeled as "beginner-friendly" or those with issues tagged as "good first issue". This ensures that you're entering a space where your contributions are not only welcome but valued.
+
+### 2. **Familiarize Yourself with the Project**
+
+Before you dive in, take some time to understand the project's structure, guidelines, and coding conventions. Read the README, contributing guidelines, and any available documentation. This will help you integrate your changes smoothly and adhere to the project's standards.
+
+### 3. **Setting up Your Local Environment**
+
+Clone the repository to your local machine using the `git clone` command. Create a new branch using a descriptive name related to the issue you're addressing. This isolates your changes and allows for easy tracking.
+
+```bash
+git clone <repository_url>
+git checkout -b <branch_name>
+```
+
+### 4. **Make Your Changes**
+
+This is where your creativity and coding skills come into play. Address the issue you selected, making sure to follow best practices and adhere to the project's coding style. Write clear and concise code, and remember to add comments for better readability.
+
+### 5. **Test Your Changes**
+
+Before creating a pull request, ensure that your code works as intended. Test it thoroughly to catch any potential bugs or issues. If the project has a testing suite, make sure to run it to verify that your changes pass all relevant tests.
+
+### 6. **Commit Your Changes**
+
+Break your work into small, logical commits. Each commit should represent a single, meaningful change. Write clear and descriptive commit messages that explain what each change does.
+
+```bash
+git add .
+git commit -m "Brief description of the change"
+```
+
+### 7. **Push Your Changes**
+
+Once you've made and committed your changes, push them to your forked repository on GitHub.
+
+```bash
+git push origin <branch_name>
+```
+
+### 8. **Create the Pull Request**
+
+Navigate to the original repository on GitHub and click on the "New pull request" button. Select your branch and write a clear and informative title and description for your pull request. Mention the issue number if applicable.
+
+### 9. **Engage in Discussion**
+
+Be prepared for feedback from the maintainers. They might ask for clarifications, request changes, or even merge your PR right away. Stay open to suggestions and be responsive to comments.
+
+### 10. **Celebrate Your Contribution**
+
+Congratulations! You've just made your first pull request on GitHub. Your code is now part of an open-source project, and you've become a contributor to the global developer community.
+
+### Conclusion
+
+Making your first pull request on GitHub is a significant milestone in your journey as a developer. It's an opportunity to learn, collaborate, and showcase your skills to the world. Remember, the key to a successful pull request lies in selecting the right repository, understanding the project, and following best practices in coding and collaboration. So go ahead, find a project that excites you, and start contributing! Happy coding!

src/content/post/not_one_vertical.md

@@ -0,0 +1,30 @@
+---
+publishDate: 2023-09-20T20:22:00-05:00
+title: Its not enough to be in one vertical anymore
+author: Bitkarrot
+description: Its not enough to be in one vertical anymore
+image: /images/do-more.jpg
+category: Opinion
+tags:
+    - skills
+---
+
+## Its not enough to be in one vertical anymore
+
+... to survive in a rapidly shifting economy, one must master multiple skills.
+
+The younger generation of self starters get it —
+
+> "Being a good Journalist is no longer just about being a good writer, its about being a good writer but also being a good Designer and a good Publisher, and that’s what all young journos are learning to do, and that’s really important to where we’re going in the future.” -Sam, The Daily Aus
+
+[![Work Better](http://img.youtube.com/vi/1k89sEWG0lQ/0.jpg)](https://youtu.be/1k89sEWG0lQ "Work Better")
+
+
+>“The whole news environment is experiencing the same challenge, and that’s to keep people engaged”
+
+
+The key point is that journalists must have a multidisciplinary skill set today.
+
+As with many other disciplines, what were once separate verticals or separate jobs yesterday are probably going to collapse into a single role today and tomorrow.
+
+The Interdisciplinary Artist, Developer, Creator, or Engineer will have a leading edge over those who don’t cultivate multiple skill sets.