Stories

Ask HN: I got laid off and I want to showcase my skills, any suggestion?

Article news.ycombinator.com

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?
Discussion 35 comments · 30 points · maury91 · 2024-05-18
Open on HN
Loading the discussion…

Domain filters

Stories from these domains are hidden from every list. Subdomains match too: blocking substack.com also hides danluu.substack.com. Type a domain, or paste a link to block its site, and press Enter.

New collection

Delete this collection?

About YAVCHN

YAVCHN is a reader for Hacker News and Lobsters, with articles and discussions in separate windows or Classic pages.

Created by Paul Parks and built with PUDL.

YAVCHN source code on GitHub

Privacy policy · Terms of use

Help

Keyboard

j / k
Move down and up the story list. The arrow keys scroll whatever has focus.
Enter
Read the marked story in the article reader.
[ / ]
Read the story above or below in the list, in the same article reader. Back returns to the story you came from.
p
Pin or unpin the marked story, which keeps it in Pinned.
n / N
Move to the next or previous top-level comment in the window in front.
c
Collapse or expand that comment.
f
Hide or show the story list.
Esc
Close a menu or this help.
Access key m
Go to the menu bar. Most browsers take it with Alt on Windows and Linux, and Safari with Control and Option.
?
Show this help.

Windows

Each story opens in a window holding its article above its discussion; drag the bar between them to share the room differently. A window can be moved by its title bar, resized from any edge, snapped to a half or a corner by dragging it there, maximised, or minimised to the bar at the foot of the page. Use Window > New reader window to open an empty reader, or Story > Open in new reader window to open another reader for the current article. Docked readers keep their articles when you select another story from the sidebar. Minimized readers can be restored and reused for their site. A window's Previous and Next buttons read up and down the list in the same window.

A link in a comment or an article to another Hacker News or Lobsters thread opens that thread in a window too. A link to a single HN comment opens the comment above its replies.

While a story's window is in front, the Story and Discussion menus in the menu bar hold its commands: pinning, Previous and Next story, sorting, collapsing every thread, jumping to the first new comment. Each window also remembers where you were in its article and discussion, so a reload, or Back to a story that Next took you past, finds your place again. Closing a window forgets it.

The whole arrangement lives in the address, so a bookmark or a shared link brings it back, and Back undoes the last change. Moving between Hacker News, Lobsters, their lists, Pinned and Find changes only the list, and leaves the windows open.

The list

The pin at the start of a row keeps the story in Pinned, and the cross at its end hides it. Pinned can be narrowed by words in the title, site or author, by source, and to the stories you haven't opened yet, and ordered by when you pinned them, by points or by comments; the filters are part of the address, so a filtered view can be bookmarked. Scroll past the end of the list to load more. Domain filters, in the View menu, hide every story from a site.

Collections are named lists of stories. Story > Add to collection files the story in front into one or more of them, and the Collections feed shows them all or one at a time; the menu that chooses collections also creates, renames, and deletes them. A note is your own text on a story. Choose Add note in a story's toolbar to write one; it saves as you type. Rows with a note carry the note mark, and the Notes feed lists every noted story and searches the text of your notes.

Browsing view

View > Windowed and View > Classic select the browsing view and save your default in this browser. Window view reuses a reader for each feed. Classic view opens stories and applets as pages. Open as a page is a one-off action that does not change your saved default. Use the Windowed selector to return an article to a window. Direct page links always open as pages.

Applets

The Applets menu in the menu bar holds three tools, each a window of its own. Replies to me takes your Hacker News user name and lists the replies to your last thirty comments and stories, checking again every three minutes while it is open, and marking what is new since you last marked them read. Look up a user opens a profile on Hacker News or Lobsters, with their submissions and recent comments, as a commenter's name in any discussion does; the bar at the top of a profile looks up someone else in the same window, and Back returns to the one before. Who is hiring? filters the posts of HN's monthly hiring threads by the words you type.

They read only what the sites publish to everyone, so none of them asks for a login, and your user name stays in this browser anonymously and is included in retained applet state when signed in.

Find

Find takes any link and lists every time it was submitted to Hacker News and Lobsters, so you can read each discussion of it.

About

YAVCHN never sees your Hacker News or Lobsters login. The discussion is fetched from each site's public API; to vote or reply, follow the link above the discussion, or the arrow beside a comment, to the source's own site. Without a YAVCHN account, your data stays in this browser. When signed in, pins, collections, notes, blocked domains, and retained reading state are stored with your account and synchronized across devices. Hidden stories and layout stay in this browser. The privacy policy has the details.

Open source: github.com/paulmooreparks/yavchn. Built with PUDL.