I disagree with the people who think you are overthinking it. If you are planning to do something this big you’d better have a plan.

How many hours on camera is this going to take? How much off-camera think time do you expect this to take? I’d imagine if I was coding something this big I’d make at least one major wrong turn that I’d want to if not have to redo.

I think you should try a mini-project that is not part of the series so you can test your setup before you make something that you want to promote. You want to design things so that you get an interesting series even if you quit early.

I’m a little skeptical of the turn to video in the last ten years. I mean, 10 years ago if I got stuck in a video game I could find the answer in a FAQ in less than a minute. Today I have to find the right video in a collection of 60 one hour videos and then seek to the right point in the video. From the viewpoint of a literate person this is a huge step backwards but I’m left with the feeling we’re on the path to Fahrenheit 451.

Who has time to watch it? Is a recruiter going to watch a video that is longer than Game of Thrones?

Myself as a photographer I’ve found that I want to share my works in progress and show people a bit of my behind the scenes work but I’ve found people don’t have time for anything less than the final polished works. People have never been rude to me the way they are to the Midjourney artists who always post the nine images they got without any filtering but I know the engagement isn’t here.

I believe polishing will be needed, but that doesn't exclude the creation of also unpolished worked.

From all the feedback gathered I will:

  1. Live stream the unpolished work, this will help creating a sense of community and people would be able to be part of the short feedback loop
  2. Collect the most interesting parts from point 1 and create polished videos
  3. Write articles for whom prefers this media

People have incredibly short attention spans these days. If your video isn't 20 second shorts with large text and jump cuts you will lose the viewer.

Video is a terrible medium in general.

You're not Tsoding/T3/Primeagen and you're better off spending your time elsewhere. Note-- their audiences are primarily young junior developers or developers to be.

And (not criticism) why is how React works a showcase of your skill?

For reference, my Github is set to private and has a single repository pointing people to my personal site. My personal site has 8 sentences on it. It says who I am and what I've built (software products). I don't blog. I don't share code.

What you need is to be able to demonstrate what you are capable of. If you have it in you, it's even better to demonstrate you are not another code monkey that is more interested in 1s and 0s than humans.

My suggestion (biased, from what I've done) is to build one or more products (ex: a SaaS product, etc).

In the best case your product brings in enough money you never need to work for someone else. In the worst case you demonstrate the ability to build a product geared towards regular human beings.

The main problem with building products is the idea, the spark, honestly I can't see at the moment a product that people need, or even less, a product that I would need

I got tired of configuring emacs by hand for use with Erlang. I had lookup the specific incantation that needed to go into the configuration file every single time. Yes, it only takes a couple minutes and it's not something I do often, but now it's just a simple script away.

https://github.com/dlachausse/erlmacs

Another example: like a lot of people I anxiously wait for certain days to come or need a reminder of just how close we are getting to certain holidays and family birthdays. So I built a quick and dirty app in SwiftUI to countdown the days until a specified date. (It's free with no ads or IAPs, since I built it for my own needs and don't care to monetize it.)

https://apps.apple.com/us/app/countdownula/id6479545149

Make a cronjob monitoring service. Make a "privacy focused analytics" platform. Make a session replay service. Make a "javascript error collection" service. Make a user feedback widget as a service.

It doesn't matter what you make. Pick something that has been done before and do it on your own.

If you are hell bent on live streaming-- live streaming that would be far more interesting than watching someone rebuild react.

Code is just your understanding of the problem and its solution. What I found count more is the ability to express it in a more natural language. Talking to your teammate, talking to your manager/client and getting that understanding across. And that means being aware of more than the technical space.

Video editing: OBS and DaVinci Resolve. OBS to record and Resolve if you really need to edit.

I posit that for technical content like this, most of the time you do not need to edit heavily.

Second is that your mindset on this for someone starting out is all wrong. You're already overthinking it and therefore increasing the impedance for yourself. Look at the first few dozens of videos for any long running channel and they are almost always just someone sharing and doing so consistently even with miniscule viewer counts.

I follow a carpenter on YT (Scott Brown) and he had a great clip from his 100th episode where he talks about how you get better at things: you just do it, reflect, and repeat. Do this enough times and your 10th cycle looks nothing like your first. Your 20th looks nothing like your 10th because you learn with every attempt.

So with that said, I encourage you to not overthink it and just start making content. Every day, there is someone trying to learn React and JS and that person is trying to find the right voice to learn from. That's why there can be hundreds of thousands of videos and recipe posts on how to make fried chicken; everyone has an affinity for a different voice.

So with that said, challenge yourself to creating quality content once a day, even if it's short. Your first week, you'll struggle just to learn the tooling and workflow. Your second week you'll have nailed a pretty good process and focus on improving your content and defining your voice. The audience will come as long as you are consistent.

For professional reasons, I think written form is better (so GitHub project plus blog writeup). I think rather than your proposed approach, just build and explore something fun and topical. How about building an app using AI tools and you review the tools and their output? Compare it to a human and give your commentary.

I agree that written form is better, but it doesn't have any time constraints, this is why I was thinking more of live coding, or why not both? In the end, I will need to do the coding part in both cases, so why not stream it?

My problem with building an app is that I honestly don't know what app to build, and recreating React sounds fun to me

I didn't find Github helpful either in the last 2-3 years. Culture has shifted and now it's about jumping leetcode like platforms and scoring highly on them. Then bullshitting your way into the interview.

If you are strictly tied to front-end, you may want to look out for different options. The front-end market is by far the worst struck and is super tight. I also, most importantly, don't think it's going to be better anytime soon and it's going to get much worse from here.

Although if you made a series of videos like "Re-creating redux", "Re-creating react-router", etc that could go a long way, yes.

Don't make up rules. Don't tie one hand behind your back. This isn't a circus act.

If I were you, I'd put this energy into learning something new, and your video content can show your progress and show off your ability to pick up new skills.

I think by creating a React-like framework what I will showcase is a deep understanding of the inner workings of the browser ( for optimization), the inner workings of React, and a good knowledge of languages and tools used to create this framework.

If it’s the prior, this is a fun project.

If it’s the latter, this is going to be a low effort activity. Employers aren’t going to watch it during your application. Further, Your target audience (people learning react) isn’t going to have much overlap with hiring managers.

Yes I do agree that managers and target audience don't overlap, but also I don't think it's people learning React, but more people curious about inner workings of React

Interviews at most tech companies are broken.

They are run by developers who are usually poor communicators which means they cannot tell you what they are looking for etc.

What you are trying to do will not help you at all.

At 11 years of experience if you are not getting direct invitations to join teams without interviews you have done the biggest mistake so far: you haven't created a network.

Your goal should be very simple. Make a list of director of engineering from top companies, see if they have a GitHub, check if they have a open source project and then contribute to that.

All you need in your GitHub is a hyped up version of your skills.

Do not do interviews, that is key.

What do you think are the causes for the first three things you wrote about?

Do you have an email address or a contact method?

It's because to find true signals of a senior engineer needs longer than 35 mins spent on a problem and you need to pair that with a developer who is trained in the art of interviewing so that they can extract the biggest things one needs to test: overall architectural principles, thinking through things, how one protects their code from mistakes etc.

But companies are not willing to spend time doing this because HR is basically not trained even today to deal with real technical thinking.

Unless there are a bunch of devs moving into HR, things will not get better.

Companies don't care that much either. Most companies pretend they need much more talent than they actually require.