Clubhouse, Pocket Casts, podcasting, audio, and more…

© 2007 Peter Skirko. All rights reserved.

The opinions stated here are my own, not those of my company.

This article crossed my Medium feed today, on the intention to sell Pocket Casts. In the responses, Tanner Campbell made the interesting point:

the medium makes the model impossible to scale without degrading the user experience

Before thinking further about scale, I want to briefly analyze the medium itself, as layers, as well as the content made in and for the medium.

To not bury the lede though, here’s my tl;dr. IMHO the medium is ultimately digital audio. Podcasting is content in this medium, albeit one near and dear to many people’s hearts. Scaling the medium itself, i.e., being creative with audio’s possibilities, is definitely achievable through innovation. Doing this without “degrading the user experience” is subjective, depending on what someone considers a degraded experience. Inserting ads into the audio stream is definitely not going to be the only game in town.

The lowest layer of the medium is digital audio. But even this layer is non-obvious, as audio can, with technology, be arranged into parallel streams of audio bytes. One stream or many? Who can read and write to which streams, that is, who can listen to which streams, and who can send audio back (e.g. through speaking, playing music, live microphone in a crowd or public place, triggering sound FX, etc.) to which channels? How do streams themselves interact (just separate? can they be merged? are there hierarchies of participation and experience?) Are the channels transient (a la Snap) or persisted? Will the stream be open, or DRM-protected? And so on.

Clubhouse got traction in part by innovating at this lowest layer, the audio itself, but there are many more intriguing combinations here to consider and possibly pursue.

The next layer up from audio is the set of complementary experiences created by related non-audio mediums that either “participate” with the audio intensely or just embellish it in some way. These too can be many. Consider text. Live transcription of the audio content, allowing people to “tweet” short text synchronized in time (a la SoundCloud), automatically publishing the transcript as blog posts for further discussion, etc. Heck, you can even convert text to audio using text-to-speech synthesis, allowing people to participate in the audio even if they can’t currently speak live (e.g., on a plane), or can’t speak at all (e.g., muteness, or pan-language discussions, as I can’t speak Portugese, Thai, Swedish, etc).

And text isn’t the only complementary medium. You can ask similar questions for visuals (photos, video, art, the almighty screenshot, etc) too.

The next layer up is the “app”, be it a mobile or web app. How does the app facilitate the audio, the complementary mediums, and the various participants? How much will it cost to design, build, maintain, evolve? Is the app “just an app” or is it a platform, and if the latter, who are the content creators on the platform — primarily podcasters, or a wider swath of participants (human, animal, virtual agents and digital intelligences, etc)?

You see where I’m going with this. There’s plenty of possibility in the audio and podcasting space, no doubt. It’s just the usual goblins lurking around the bend: business model, scale, technical sophistication, funding and cost, critical mass of adoption/usage, etc.

I also distinguish between these medium layers from the content created in and for it. There is a spectrum here from NPR to Joe Rogan. The content is how the medium is used: what is said or done, and for what purpose or end. Conversation? Community? Public Good? Profit? A “good business”? etc.

So back to the quote and my tl;dr. The medium is digital audio. Podcasting is content. Podcasting is near and dear to many people’s hearts, and part of that passion entails keeping podcasting available through certain approaches to Free, Open, etc. This is good and important, but overall, audio is a wide, wide space where a lot of experiences will unfold.

Scaling the medium, audio itself, is largely about being creative with audio’s possibilities, and realizing those possibilities in durable ways. Being a technologist, my answer here is ultimately innovation: the concerted effort to make things people want and use. Some of these ideas will be hard to make happen for time-varying technical reasons, others for business or capital reasons, others for lack of compelling content or being insufficiently differentiated, etc. Clubhouse is an example of this so-far-succeeding innovation, and Pocket Casts has an unclear future, but it’s the just a few chapters of this story, definitely not the last. Whether that happens from startups, or “Big Tech”, or public initiatives, etc., or all the above, is all TBD.

However, doing this without “degrading the user experience” is subjective, depending on what someone considers a degraded experience. Inserting ads into the audio stream is definitely not going to be the only game in town. Some experiences will be paid, others ad-supported, others funded publicly or through governments. I imagine there will be an ICO or NFT involved too… 🤷.

So there you have it. Just my personal thoughts.

Stratechery has a recent article on Clubhouse, which I’ll read soon, but I like to form my own opinions first.

5 principles for managing and optimizing your tech career

The opinions stated here are my own, not those of my company.

© 2021 Peter Skirko. All rights reserved.

Whether you already have a blossoming career in tech or are trying to “break into the industry”, congratulations, and get ready! A career in tech is both rewarding and perilous. Here’s why.

A tech career can be rewarding in many ways: the money (in the US at least), growth (IC to tech lead or manager to CTO), interesting problems (robot dogs!), and so on.

A tech career can also be perilous. Startups like to fire fast. From startups to Big Tech, you might work really long hours. Some technologies become obsolete or moribund (Perl, WPF). And while some technologies rise and rise (Javascript, Python), others will rise, peak, then slowly decline in terms of broad popularity (for iOS and Android developers, the “gold rush” is long gone). And age discrimination is real—for example, IBM directed its manager to “replace older workers with early career hires”. Gender pay disparities? Still present, year after year. And racial equity has a long, long road ahead.

So what’s a techie like you to do?

TL; DR – Here’s 5 principles for managing and optimizing your tech career:

1. Understand the tech industry and why you are in it.

2. Get the best job(s) you can. “Best” is defined by your goals and values.

3. Always be growing in your current job and company. Don’t stagnate.

4. Keep investing in core skills. For software engineers, Always Be Coding.

5. Focus on longevity. Statistically speaking, most of us won’t retire early. How are you going to last 40+ years?

Let’s dive into each principle in more detail.

1. Understand the tech industry and why you are in it.

Why does WhatsApp sell for $19B but consumer-robotics startup Anki has to wind down after raising $200M? For startup seekers, do you know what a cap table is and how it’s managed, or what a 409A is and how it affects your future taxes? Do you follow the political landscape, like how the EU wants to keep increasing regulations on Big Tech, or whether Bitcoin will ultimately be banned (or not) in some places?

These questions are just a sample. But in your tech career, I strongly recommend that you understand—read, follow, discuss, study, explore—the tech industry. Otherwise, you might not make the best decisions for your career, your family, and so on.

And while you cultivate your understanding of the tech industry, you need to understand why you are in it—your place in this world. Are you in tech because you absolutely love it? Are you here primarily for the good money or the chance of riches? Nobody can answer this question for you.

In some ways, a tech career is simple:

Your career as a finite state machine (or Markov chain, or Markov decision process…). © 2021 Peter Skirko. All rights reserved.

But of course, it’s not really as simple as that. Managing and optimizing this career takes active effort, which leads to the next principles.

2. Get the best job(s) you can. “Best” is defined by your goals and values.

I know what you’re thinking: easier said than done. And you’re right.

“Best” is defined by your goals and values, not mine or anyone else’s. It’s easy to forget this, but don’t, as this is the heart of being fulfilled.

Best can be: financial certainties or possibilities, growth or learning opportunities, work-life balance, flexibility (e.g., the “nomad” lifestyle), a really great culture, etc. With the rise of remote work, which has its own pros and cons, you are less restricted than ever by the companies in your local market. Define your own “best”.

Some people, many in fact, experience the feeling of Imposter Syndrome and may not believe they can get a better job. I don’t have any “quick fix” for this, other than to say, there are many people who can help and support you, from friends and family to people on the internet (like this post!), your confidence and skill can build over time, but IMHO it often takes years of discipline and hard work, and an ability to endure struggle and even rejection, to get better. But believing in yourself, and your potential future self, is a key ingredient.

Also, lots of people find the typical tech interview process unpleasant. From “coding” on dry erase boards to focusing on algorithms and data structure questions, the preparation is time-consuming and the experience itself is exhausting. But hard doesn’t mean impossible. With the right time horizon (for some people, years instead of months), and enough time to practice (which many people don’t have), this process can be tamed. Focus on the goal, and realize the interview process is a means, an investment, to get there.

3. Always be growing in your current job and company. Don’t stagnate.

A lot of tech career advice on the internet focuses on either breaking into the tech industry or switching jobs. This is fine and useful for many people, but many of you will stick with a company for a while, a few years perhaps, or maybe even a decade or more.

With the right company, this is great. Why? Because you can continue to learn and grow without having to pay the “tax” of the interview process: the preparation, taking days off to go to interviews, wasting lots of time on interviews that go nowhere, spreading yourself too thin, etc.

The only challenge is that most companies do not employ you to learn and grow. They employ you to get work done. This work can be tactical or strategic, it can be glamorous or grungy, it can be exciting or repetitive, but it is the work you are expected to do. Sometimes it actually helps you learn and grow, but often times it doesn’t. Don’t stagnate and don’t become complacent.

IMHO the only durable approach to this is creativity. You, dear reader, have to be creative in how you manage both your career and your day-to-day job, not just to get the work done, but to tie it into your needs to learn and grow and achieve longer term goals. Creativity is not just for artists and inventors. This topic, creative career management, is the one consistent, always-there opportunity for creativity that every tech worker has. Voila. Maybe you didn’t see yourself as a creative type, but you are. You have no choice!

Of course, the next question is: how exactly do you creatively manage job and career and optimize for learning, growing, and the rest? That’s a big topic, and a subtle one, and is a topic for another post, but Principle 4 below is the main step.

4. Keep investing in core skills. For software engineers, Always Be Coding.

Your value, and thus the strength of your career, is not defined by tenure, years of experience, “reputation”, or other vague or fluffy metrics. Those are ultimately tautological.

Your value is based on your realized skill: what you do, and how well you do it, and its impact on the world. For some, it is technical and collaborative skills; for others, it is managerial and leadership skills. But it is always about skill and the work you do, not surface appearances. I’m not saying you should get a “mad skillz” tattoo, but… consider it.

Skills are improved through work and practice. For software engineers, please read Always Be Coding. I still remember when this was published, because it so succinctly and astutely hit the nail on the head. For marketers, read Seth Godin’s blog and books. And so on.

As mentioned in Principle 3 above, your current job and work might not be improving your core skills. This is often the case. Creativity is still needed. Practice in small chunks, consistently, if you can.

5. Focus on longevity. Statistically speaking, most of us won’t retire early. How are you going to last 40+ years?

If you retire early, congratulations and please send me a digital postcard from the beach. But most of us won’t retire early. So how the heck are you going to last decades in tech?

Well, you gotta do all the above. Know the industry, get the best jobs, keep learning and growing, and keep focused on building your core value and skills.

Will that be enough? Again, this is a deep topic, and a subject for more posts.

The problem is that most people aren’t thinking 10 or 20 years ahead for their career. Sure, they are often saving for retirement, like investing in their 401k in the US, but they are assuming or hoping that they stay employed until retirement is possible. Look at what happened at IBM, though. Remember, age discrimination will compound every other type of discrimination, be it gender, racial, etc.

Hope is not a strategy. To quote Dune, “hope clouds observation“. If you stay employed until retirement, is it due to skill, inertia, luck?

Working in tech seems easy at first. Then wait til you hit 35. Then 40. And 50. The game changes. Are you ready? Physically, mentally, financially?

I don’t that to scare you. I say that to help you be prepared, to find others with similar horizons and challenges, etc.

Conclusion

So there you have it. 5 principles for managing and optimizing your tech career. For success, longevity, fulfillment, you name it. Literally, you name it: you figure out what you want to do, how realistic it is, and what it will take to get there.

Questions, comments? Comment below or ask me on Twitter @pskirko. Cheers.

If you are reading this elsewhere, you can also read it on my blog here.

Super Resolution now in Photoshop

Image borrowed from petapixel.com

Check out this article on petapixel.com: Adobe Photoshop’s ‘Super Resolution’ Made My Jaw Hit the Floor.

Super Resolution has launched in Photoshop. Actually, in Adobe Camera Raw. You can now effectively double an image’s resolution without blurriness. Which is truly, truly awesome.

I had been expecting this moment for a few years now. It was clear deep learning was a great fit for super-resolution, so it was only a matter of time before it reached mainstream availability in Photoshop.

This is a tremendous opportunity for millions of photographers (from pros to hobbyists to just everyday people) with lower-res photos. They can take those photos, upscale them, and either re-crop for online use, print larger, etc.

Congrats Adobe. This is such a helpful capability to have, and it will only get better.

I also posted this to LinkedIn; check it out here.

A guided tour of my blog

Hello and welcome to my blog. Here is a quick tour.

Who do I write for? My blog is not “popular” by any stretch of the imagination, and I’m cool with that. I mostly get a bunch of recruiters and a few other passers-by here. So, I write firstly for myself; then for my kids, as a testament of who I am and who I was; then, for all of you, whoever you might be.

Ideally, I would update this blog 2-3 times a week, consistently throughout the year. In practice, my updates are burst-y: (1) I make a bunch of edits over a few weeks, (2) then radio silence for a few months, (3) then back to (1).

About all those recruiters: I have nothing against recruiters as people, and some of them have been kind enough to tell me they liked what they read, but in general, when a recruiter is reading my website, they are just doing their job, which is recruiting. I send recruiters to my page tl;dr for Recruiters.

This blog is about both professional and personal interests. As for being a software developer, I started a career advice page, and my most popular article so far is Coding as a hobby? For me, non-work coding is a regimen, like going to the gym.

I have been trying to blog more about my creative hobbies, but that has been slow going so far. Check out Learning Adobe Illustrator by manually tracing: Jango Fett Pt. 1 or My first Processing sketch.

This blog is using a theme that I started by forking a standard theme. Check out the updates, such as Version 1.2 of Moderately Austere, a personal blog WordPress theme, has been released and Moderately Austere, or the Power of Fork–Exec.

Post Update

I recently updated my post on how to write good blog posts. You can read the updated version here.

In this new version, I get much closer to capturing the points I want to get across. I use these guidelines as I write new posts and edit older ones.

Happy reading!

Coding as a hobby? For me, non-work coding is a regimen, like going to the gym

Einstein FTW

The opinions stated here are my own, not those of my company.

tl;dr – Don’t feel pressured to treat coding as a hobby if you don’t actually find it fun and relaxing. If your goal is to get better at coding, just treat non-work coding as a regimen, like going to the gym.

Continue reading “Coding as a hobby? For me, non-work coding is a regimen, like going to the gym”