It really shows how AI is going to change the entire industry.

Let's imagine tomorrow a Product Manager at LinkedIn wants to introduce this as an official functionality? They're going to have to run it by management or their pod (or find the PM in charge of that area if its not them), finish existing project, wait for resources to be ready, have legal/marketing/compliance involved, get it developed, go through all the other red tape, etc.

I don't know exactly how LinkedIn works internally, but I'm sure some of this is accurate.

So maybe, MAYBE they'll have it in a couple of months? But someone can build it in a few hours, even if they're not super good at this stuff.

It changes everything about how we think about products and SaaS software.

> But someone can build it in a few hours, even if they're not super good at this stuff.

Note that the end result is not the same as what LinkedIn would have built. Perhaps in some ways better and in some ways worse.

E.g. personally I am not comfortable bulk uploading personal data of myself and my network to a third party server.

Yup. But my point is you can build this yourself, FOR yourself. So if you're not comfortable with using this one, you can build one on your own that you can trust (because you built it yourself).

Thats the whole point. In an AI world, you're no longer bound by the limits of what 3rd parties do or don't do, plus or minus some datasets (like in this case, the job postings).

Yep! I agree to the principle - I also would not trust a random third-party app with my personal details. Though as noted in my other comment, this app is mostly client-side (including the CSV and ZIP extraction), except of course for the JSearch calls to find jobs by company name, and the CSV export if you choose to use that.

  > personally I am not comfortable bulk uploading personal data of myself and my network to a third party server.
The subject of this show HN is completely client-side.

It changes nothing, what you describe has always been the case even before AI. There are things people can build in a weekend that take weeks or even months at a larger company. Large companies have a way of slowing everything down, for reasons that have nothing to do with coding.

Correct, but the amount of people who can do it has drastically increased, and the amount of time it takes for most people to build these things has drastically decreased.

It has not drastically increased. One could even argue it has decreased. Ultimately, the productivity gains will perish to bureaucracy.

This is exactly where I think we're heading as well. This project took about 2 hours.

Primarily because LinkedIn has to bother with complying with their privacy policies and other T&Cs, and your site has none of that.

Why should I take all of my data and give it to you, a rando on the internet? Is it being stored? Will it be shared? Sold? Maybe, as there's nothing that says you won't.

Looks neat, but strong pass because of the above.

Correct. But you can build this thing on your own, for yourself. LinkedIn didn't, and you don't trust this third party. So if you had the problem its trying to solve, you could just spend the 2-3 hours and build it for yourself, even if you don't have all the necessary skills to do so.

That's the whole point.

And in the process you develop another skill you can add to your LinkedIn profile.

Those are totally fair points but what I agreed with here was that people will create _personal_ software to solve a particular itch for themselves, which is what I did here for my friends. I just decided to throw it on HN as I have some API credits remaining :)

Not sure it changes EVERYTHING as the issue of sales and marketing still favours LinkedIn. Sales/Marketing is very expensive and sometimes even difficult to predict. Building is not everything.

Right, the point Im trying to make is that if someone has a requirement, they can build it on their own, for themselves, at much lower cost (because they don't need sales and marketing for themselves).

It was always possible (hire software devs to do it), but the bar and cost is much, MUCH lower.

Sure, no doubt about it.

This feature already exists and has existed for like 10 years (I know because I built the original implementation of it)

[deleted]