This is actually a side-project of a side-project, so I wanted to have a go at building the algo myself for a bit of fun/learning. I’m using Ruby under the hood...

Lately, I have been coming across a lot of really cool crypto projects that seem to get very little coverage in the ProductHunt community. They have a crypto topic but I think we are getting to a point where there is so much going on in the crypto space it might justify a daily list of it's own.

No analysis yet. Just getting the ball rolling with feeds from selected blogs and youtube channels.

I'm hoping that, over time, the community will weed out the good articles from the bad.

I created Gains Supply because I'm interested in bodybuilding and I'd genuinely like to start a community that features and discusses helpful articles and products in that niche. I Hope posting it here doesn't come across too spammy, just looking for early users.

Feels a bit on the spammy side since there is no user activity to curate the list. Catch-22.

There should be a red 'Close' button in the bottom right-hand corner of your screen. I'll add the option to use ESC as well.

I have one (red close button). Flutter on first use seems like a faster workflow than the normal, right click, inspect element, look at the chrome elements, find the tag. Great Job!

The purpose of this bookmarklet is to provide a streamlined method of getting the selector without having to go into the source or use chrome tools.

There is also the problem of using ids. For example in Flutter I may want to auto tweet out the top post in a list of posts on a blog. If the posts have individual ids, and the CSS selector includes them, every time Flutter tries to scrape new content it will get the same post. I want the unique selector for the page element. i.e. the first post in the list.

I use Selector Gadget too and I was recommending users of Flutter use it to get selectors. However, I'm trying to make the process of getting a unique selector for any element so simple it won't put anyone off. This bookmarklet avoids the need to deselect things and once an element is selected it's just a case of CMD/CTRL + C.

You're right. However, the purpose of this bookmarklet is to provide a streamlined method of getting the selector without having to go into the source. Using 'inspect element' is easy for me and you but for some people its enough to put them off trying to get the selector.

Good for you! :)

Do you have any advice?

Programming is way easier than real engineering. Keep that in mind as you study and prepare. ;)

That's an interesting statement. Why do you think programming is easier than 'real' engineering?

Thanks for your answer.

Out of interest, were you working in a manufacturing position when you wrote the software for your business or did you spot the opportunity from the outside?

I noticed the opportunity from within, and I jumped ship and went for it. But that was a different time because I was young, no kids or typical bloated American overhead.

That's cool. Unfortunately, I do have overheads, not kids, but enough to prevent me jumping straight out of work into a startup business.