I don't know why this is getting voted into the ground. This advice would seem to be a way to keep motivated while interviewing, keeping sharp through actual coding, and getting up to speed with any changes in general software engineering in the last 4 years. Even if the coding projects go nowhere, motivation is king.

I didn't downvote. But, while working on a side project might well be a good idea to polish up skills, build a portfolio, etc., trying to bootstrap a revenue producing business--assuming that isn't an actual goal--is likely to be a big distraction from both coding and job-hunting.

Agreed, but I'd guess it wouldn't get downvotes if it focused just on brushing up skills and making a portfolio piece rather than mentioning revenue and extending runway.

You can't bank on a new project having any significant financial success, or much traction at all really, especially if it's your first rodeo. Making money is mostly about validation, talking to potential customers, and iterating on ideas, not coding. While they are great skills to learn, it's not a particularly efficient way of beefing up an engineering resume.

I do think it's good advice though to build some stuff while interviewing. I'd focus on small projects that can be built and shipped in a month or so, and do a few of these alongside interviews. Also be sure to put effort into nice landing pages--people judge by appearances.

"Revenue generating indie project" is easier said than done. If that's what the person would really like to do? Sure. But otherwise it's probably a distraction given that revenue producing means it will probably be as much about marketing and selling as developing.

As someone who can't get hired, you can't really apply to and get rejected from positions 8 hours a day, that would be soul crushing. So I plod along on my projects and walk the line just on the other side of soul destroying levels of rejection ;)

I don’t think it’s a distraction because it can be a portfolio project to demonstrate competence in a new area.

Even if it doesn’t make revenue, it’s still a years worth of xp on a resume.

I think there’s pretty much zero chance of getting a programming job with a four year gap and no meaningful projects. But add in lots of commits showing off good design and coding decisions and it’s easy for a company to understand value and hire.

I think it may be possible you live in some kind of js bubble - I have never heard of those things and it wouldn't be something I'd advise anyone to do.