7 ms·
Ask HN: I got laid off and I want to showcase my skills, any suggestion?
I got recently laid off (the first time in my life ), and I have worked for around 11 years without being more than 2 days unemployed; I'm currently doing rounds of interviews and for the first time in my life, I have an extreme amount of free time.
I can imagine people would recommend me to use this free time to follow my passions, get some rest, play videogames or do anything that is not working; but I'm not the kind of person that likes any of those things, I like to do something constructive, and I would like if this something can help me now or in future with my job search.
I saw many job posts asking for a Github account to see what contributions I have done to open source, and unfortunately, my contributions amount to none, the companies I have worked for do not publish open source code, and with 2 hours of commute + 9 hours being in the office when I'm home I don't feel like I want to open my personal computer.
With this in mind, I thought "Why not do a video series where I show my front-end skills". This will kill two birds with one stone, first I will get some contributions to dummy projects on Github and second I can show my reasoning on video.
The first problem is that I don't have video editing knowledge, and I feel that will eat the majority of the time, resulting in a project that is less focused on what I'm aiming for.
To avoid the video editing problem, I plan to do live coding, I believe thousands of developers did this before me, and I want to do a topic that is different than usual, with this in mind my topic of choice is to live code a web framework, my framework of choice is React.
I plan to go through these milestones:
1. Rendering JSX directly into the DOM: get a js compiled through babel and just make it work
2. Create a shadow dom
3. Optimise the shadow dom
4. Support all react hooks
5. Further optimisations
6. Re-create redux
7. Suspense ( Lazy loading )
8. Re-create react-router
9. Using babel API create a different output for jsx files ( different syntax )
10. Create browser extensions for developers
Note: I chose these milestones to make the video series help people understand how React works on the inside
And following these rules:
1. No peeking on React source code
2. No stack overflow
3. No copilot/chatGTP/any AI
4. Looking at React documentation is OK
The idea is to retro-engineer React, I know this looks like it contradicts the point of helping people understand the inner workings of React, but I want this video series to have some challenges ( and external help will remove that ), and the final product must be compatible with a subset of React capabilities so with it being compatible it must have similar inner workings, so even if not identical I believe they will be similar enough to help people understand how React works.
Now that I laid out all my thoughts, I ask you for some advice:
1. What platform is best to start? ( I was thinking youtube )
2. How to get the first views? ( My feeling is that I would be live-streaming to literally no one for months )
3. Any other advice that I could not think of asking?
- CharlieDigital 2y agoYou are making this too hard; don't overthink it. 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.
- maury91 2y agoThanks for the input, I like your proposed approach of "don't overthink it and just start making content", that is exactly what I will do. 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