Sourcing.io
sourcing.io
Sourcing.io
1–10 of 59 posts
Re: Sourcing.io
#2Engineers are valuable for what they can learn (skills and about the problems they are solving) not for what they know at a particular point in time.
A myopic way to look at hiring.
Edit:
You should care about the delta of an engineer's career and knowledge. That says a lot more about how they'll perform now and in the future.
These days companies prove themselves to engineers. I'd rather see something like a more descriptive and meaningful glassdoor so that I can know what companies are worth my time.
Tags/attributes like:
"$company is in the 67% percentile for employee freedom in your job type [Software Engineer]"
"$company practices open allocation."
"$company is known for fast-firing. They are also known for paying XX% above average for your job type [Software Engineer]"
I don't want some bullshit tag-based skill endorsement clone of LinkedIn profiles. I hate LinkedIn for a reason. I definitely don't need to be even more discoverable by recruiters - my website is a fucking curse on that front as it is. I leave it up because I do get valuable conversations going because of it.
I'm more interested in sites that could further balance the lopsided information power dynamic between employers and employees.
I want to know if there's a chance of a fit between me and the company before I even email somebody.
A company is more likely to be able to recruit me the more substantive information I have about what it's like to work for them. Shut the fuck up about perks, tell me about how you empower your employees to perform their best and entrust them to do the job as it needs to be done.
Things like sourcing.io don't just hurt engineers, they hurt the companies that recruit like this (technology checklisting) too.
-
Making it even easier for lazy recruiters to be shitty is a bullshit thing to do. May the spam of a thousand recruiters looking for "Senior Java developers" flood your inbox and decimate your sanity MacCaw.
Re: Sourcing.io
#3I don't understand. They say "we find you developers from our database of 4 million devs" but later say that they find them from YOUR github/fb/linkedin/twitter connections? So is this a sort of web scraping tool?
Re: Sourcing.io
#4I don't understand. They say "we find you developers from our database of 4 million devs" but later say that they find them from YOUR github/fb/linkedin/twitter connections? So is this a sort of web scraping tool?
yes
Re: Sourcing.io
#5So how does one know if they are in your database?
Re: Sourcing.io
#6I don't understand. They say "we find you developers from our database of 4 million devs" but later say that they find them from YOUR github/fb/linkedin/twitter connections? So is this a sort of web scraping tool?
Time for the damn GitHub to introduce more privacy, instead of putting all you ever do in a PUBLIC activity feed, with no opt out.
Re: Sourcing.io
#7Engineers are valuable for what they can learn (skills and about the problems they are solving) not for what they know at a particular point in time. A myopic way to look at hiring. Edit: You should care about the delta of an engineer's career and knowledge. That says a lot more about how they'll perform now and in the future. These days companies prove themselves to engineers. I'd rather see something like a more de…
> Engineers are valuable for what they can learn
This statement is also myopic and bordering on cliche. While true, there are a lot of times want to hire for a specific skill set. For instance, if there's a problem that needs solving right now, or a team that needs a new lead (assuming you must bring on outside leads), or a whole number of scenarios.
> You should care about the delta of an engineer's career and knowledge
This is, often times, a great indication of how competent an engineer will be.
Re: Sourcing.io
#8Not honest to say its 'our database' when you are just scraping/searching github and stuff.
But I looked at the https://help.github.com/articles/github-terms-of-service and I don't think it says you can't scrape to a database, although at least one clause about reselling or whatever causes a question.
Its cool if they are honest in their marketing and actually add something to github search, which I am pretty sure they do, because github search isn't very good.
Anyway seems very useful but don't really like the marketing.
Re: Sourcing.io
#9Engineers are valuable for what they can learn (skills and about the problems they are solving) not for what they know at a particular point in time. A myopic way to look at hiring. Edit: You should care about the delta of an engineer's career and knowledge. That says a lot more about how they'll perform now and in the future. These days companies prove themselves to engineers. I'd rather see something like a more de…
I used to say this as well, as someone who has done C# (5yrs), Perl(2yrs), and Python(5yrs) work. But the truth is that there is a training/ramp-up period during that learning period.
When I made the switch from C# to Python it probably took me a year or two before I became as good at Python as I was at C#. This is also true for a lot of the developers I currently work with who are using Python for the first time.
There is something to be said about being a master of a language, libraries, and tooling around a certain platform and getting there isn't a quick 1-2 week crash course in the language. Sure you can figure out the syntax and make things work, but if you are truly an expert in 1 language, you wont be comparable in another for at least a year while you use the language and learn the ins-and-outs.
People never ask me language questions at work, "how do I do a for loop", but I get daily questions on how virtualenvs work, python packaging, and what libraries to use.
Re: Sourcing.io
#10won't this just enable recruiters to spam developers?