Kyle Cordes – Page 2

Design your content for effective video

This post is part of a series on demonstrating competence and expertise on video:

Technical setup
Process
Content (this post)
Promotion (coming sometime)

Your goal is results, not Minutes Watched

YouTube is full of videos that take 10+ minutes to deliver 30 seconds of information. Why? Because this content is on channels that make money by showing ads. They need each video to be at least 10 minutes, and more minutes watched means more ad revenue.

But that’s not the context I’m writing about. This post series is about demonstrating expertise and competence on video:

A small-scale, mostly-one-take video production process

This post is part of a series on demonstrating competence and expertise on video:

Technical setup
Process (this post)
Content
Promotion

Create an outline

Outline your video in some detail, and make that outline visible (either on your screen, or printed on paper) during your video recording. Not too much detail, though; the outline shouldn’t take long, perhaps just a few minutes.

Then iterate on the outline, and get feedback from others if the video is important or if you are new to this kind of content. Rearranging text in an outline is tremendously easier than re-recording or video editing, so make the most of this stage.

Audio-video setup for meetings and videos

This post is part of a series on demonstrating competence and expertise on video:

Technical setup (this post)
Process
Content
Promotion

So you want to show expertise and competence on video…

Recording a technical talk? Creating a video about a management tool, to be used as an advertisement for consulting services? Working on the perfect conference talk for an online conference, hoping to gain another 1000 Twitter followers among the community using a library you work on?

These are all cases where demonstrating competence and expertise in a video, to an audience who can leave with one click at any moment, pays off. Here are tips I have found around the web and from my experience.

Coding together – continuous technical community

I was thinking today, observing how our multiple teams (spread across many customer projects) at Oasis Digital and Expium collaborate. There is an interesting pattern of collaboration that spans the very different types of work at these two firms I’m involved in.

For background, the work at Expium is all about Atlassian products, and the work at Oasis Digital often touches Angular in some way, in conjunction with other full-stack technologies, because we are most well-known for Angular. I don’t think today’s thought really depends to any specific technology, but I’ll tell it from a software development point of view.

We have been using Angular for about as long as it is possible to do so. We started back in the Alpha sequence and have built a great amount of code for many customers since then. We’ve trained thousands of developers. And personally, I have written a lot of Angular code, including code used in teaching Angular Boot Camp, which means it is example code, very heavily scrutinized and polished.

Full stack Angular – live coding – talk notes

I spoke (and live-coded) at the Advanced Angular Lunch in St. Louis, August 2019. The talk description:

Watch or heckle as Kyle from Oasis Digital live codes a full-stack Nx + Angular + Node + Nest + GraphQL project, with concurrent explanation and Q&A along the way. Mistakes will be made, and perhaps corrected. Lessons will be learned, but perhaps forgotten. You (might) see the productivity possible with “full stack Angular” – but this is real live coding so anything could happen.

Continue reading “Full stack Angular – live coding – talk notes”

Maximum productivity when you are the bottleneck

Scenarios that make you scarce

Software development productivity is the ratio of desirable high-quality software to money spent. With this meaning, productivity is aligned with quality and effectiveness: it only counts creating “the right software” and encompasses creating “the software right”. Productivity is more important than efficiency (the lack of waste), as occasionally a bit of inefficiency pays off.

In the quest for some combination of these values, project management methodologies or practitioners generally assume that members of a team have approximately similar scarcity/availability/cost. But sometimes, you may find yourself more scarce than a group you are working with:

You are leading at a high “fan-out” – one person leading a team of many.
You are leading a team expected (for good reasons or bad) to expand or turn over significantly.
You are much more senior than the rest of your team.
You are in an expensive city or country, other team members are in a less expensive locale.
You are a “hired gun” consultant, brought in at great cost, expected to “move the needle”.
You are a professional developer responsible for mentoring, teaching, and getting results from a group of interns.
You have a communication advantage with the customers of a product or project; perhaps you speak the customer’s language more fluently than others on your team.
You are the only team member with extensive and relevant experience to the problem at hand.