I thought it might primarily be journalists, but a lot of people need to transcribe audio: academics, language students, podcasters, oral historians, secretaries, video caption writers… the list goes on.Īt first it was exciting, to see page views grow and receive nice messages from people finding it useful. And yet, it turns out there is a huge market for that. It’s a text editor with a built-in audio player, and keyboard shortcuts for playback and time stamps. The concept for oTranscribe sounds super basic without context. And so, with relatively little involvement from me, oTranscribe continued to grow organically. The app was built to be be resilient: it’s open source, (still) hosted on GitHub pages, and has no server side components.
But oTranscribe wasn’t quite done with me. As far as I was concerned, I was done with oTranscribe. In a matter of months I had a new job developing interactive graphics for the Wall Street Journal, much of that thanks to oTranscribe. I launched oTranscribe in October 2013 and shared it with friends and at local meetup groups, including Hacks/Hackers London. I built it because I needed it in my day job, but also because I knew it might help to raise my own profile – my six-month search for a new job had not been going well. One was a web app to help me transcribe audio interviews called oTranscribe. I found the best way to motivate myself was to attempt projects, little apps, most of which went nowhere. In autumn of 2013, I was working full-time as a reporter but also teaching myself to code. The 😃 and 😰 of a successful side project
0 kommentar(er)
