docs VS se-unlocked

This year, I learned how to create an issue for an open-source when there is no template for the first time.

As I was exploring this podcast's open-source contributions, I found an issue that piqued my interest. This issue, related to episode 47, focused on how to enhance the transcripts of the episodes. The author needed help improving the clarity and understanding of these transcripts.

Hey, great list of awesome podcasts. I’m the host of Software Engineering Unlocked https://www.se-unlocked.com.

The episodes focus on the experience of my guests with software engineering practices such as testing, or code review, their journey to advance their career and often also on how developers build their successful business.

Would love if you give it a listen and see if you like my show.

For my last PR, I contributed to the se-unlocked repo which manages the transcripts for the Software Engineering Unlocked podcast.

During Hacktoberfest 2021, I was browsing and looking for an open source to contribute to. I only had a little time at that time. So, I limited my search to accessibility and documentation issues. And that was when I found an accessibility issue. It was on Michaela Greiler's Software Engineering Unlocked Podcast repository.

For part three, I decided to take on a different kind of issue - to improve transcript for a podcast episode. The process was similar to what I had done for my previous PRs. I forked the project and created a branch for the issue. However, since the work involved editing a markdown file, I decided to use GitHub's built-in editor to work on it instead. The improvement process involved listening to the episode while reading through the existing transcript. I would pause as needed and fix any issues which I notice. These mostly involved a few missing words, missing pronunciation, incorrect pronunciation, and some incorrect words. For example, git pull was transcribed as git poll, O'Reilly as a Raleigh, abstraction as obstruction. Though I was quite surprised by how accurate the auto generated transcript was. The only places where it would mess up was when there was a slight overlap in conversation, or when terms specific to software development, or names of publishers were being said. Throughout this process, I learned a bunch about transcribing - what may be ignored (phrases such as um), when to be exact, how and when to transcribe laughs, background music, etc. And once I was finished with the changes, I created a PR.

This time, I contribute to a repo from Software Engineering Unlock,a podcast for discussing topic about software engineering. They need some help to go over automatically generated transcript to correct them to improve accessibility, so I participated in the issue for one of the episodes and made a pull request.

Software Engineering Unlocked Podcast

Due to the above, the transcriptions were not exactly "accurate". To pick up an issue, all I had to do was create an issue with information about which episode I wanted to transcribe.