Hacker News new | ask | show | jobs
by philsnow 2414 days ago
from https://real.dev/docs

> Can I share my code?

> We strongly recommend against sharing your code publicly. It will ruin the fun for everyone.

s/the fun for everyone/our business model/ ?

Once people catch on that solving these problems can lead to landing actual jobs, there's a certain kind of person who will share complete solutions, either widely or with some in-group they're in.

Once that happens, the companies you're partnering with will (okay, "might") start noticing quality issues with the candidates you're sourcing.

I don't have an answer to this problem. I don't understand the mind of the kind of person who shares interview problem solutions.

3 comments

Thanks for the comment. Yes and no.

On the job seeking perspective, what you said is right. Typically what people do is signing an NDA, but even with that, the question/solution still sometimes leak on the Internet.

On the learning scenario, it's sorta true, but mostly sharing the solution would ruin the motivation, at least for me personally. If I know there's a solution sitting there, I wouldn't be interested in repeating it again.

I know it's sorta silly... But my mind works best when I only focus on the problem, and how to solve it. As long as I know there's a solution, I couldn't stop myself looking at it whenever I was stuck at any tiny bit.

The home page really needs a better, terse description of what this actually is.

Right below "What is Real Dev?" or below the video, which would probably explains things, but which I'm not interested in watching.

The three paragraphs below only give a rough idea that has to be pieced together.

Thanks for the feedback!

The homepage is actually sorta old. I'll update it.

The homepage text gets cut off on the left side on iPhone SE.
I think for alot of people the immediate reason for paying for this service would be that they can put the resulting code on github as an example of small completed project.
That's actually... interesting. I haven't thought about it this way. I guess you mean people want it to be part their portfolio, which actually makes a lot of sense. I don't have the best answer yet, but I guess one thing is that, we could host the source code on our site and have some sort of portfolio page here.
Yeah, the main reason I would pay for this would be to put the project in my portfolio. I have my own portfolio page though; I wouldn’t be interested in hosting it on a third-party site. Even if it was just something I would link to from my site, I would be concerned that potential employers would see it was “just a tutorial” and write me off as not having the experience in question. That said I don’t often get asked for source code during interviews these days, so probably the ability to host the minified code for a demo would be enough.
The first part makes perfect sense.

> That said I don’t often get asked for source code during interviews these days, so probably the ability to host the minified code for a demo would be enough.

I'm a little bit confused about this piece. Are you suggesting we host the minified code on our site + the demo? Because in the first part, I thought you wouldn't want that because employer should see this as a tutorial thing if they see anything on a third party website other than your own website?

This.

I'm building a really in-depth fullstack project at the moment that I can use as a both a showcase and a playground for exploring how technologies fit in a real, production-grade application.

It's definitely very valuable to be able to demonstrate you can do something that's very complete.

The thing I like about the approach is that it functions like an ecosystem of different projects, so it becomes much more worthwhile investing in finding more ways to extend it. If I want to learn a new backend technology I have a completely working front-end ready to go. If I want to learn a new type of database, I've got a front end, business logic and repositories all done, I just need to figure out the data access and hosting the db. If I want to learn how to do Multi-Region Active-Active deployment I've got a full application I can adapt to that. Doing each of these projects unlocks the ability and worthwhileness of doing more.

I've just started this approach this year but I wish I did it so much sooner.

Another classic example of Goodhart's law