So a while back I was cold-emailed by a recruiter at source{d} (the makers of this library). He wrote that after analyzing my Github profile, he has a great opportunity for me in Country A. I responded back by sending him my private phone number and showing interest in talking to him about this opportunity on the phone.
Usually At this point, serious recruiters will do call you. But instead, he wrote that before going any further, he would like to ask me "a couple of quick questions" and requested if I could email him back my answers.
The kind of questions I was supposed to answer were pretty amusing: for example, one of the questions involved telling "If I live near Country A."
But he could easily find this out by looking at the country code of the phone number I just gave him in the previous email. My location is also public on my Github profile, so he could have easily found out that I live in Country B. which is around an hour away from Country A. The rest of the questions were also showing the recruiter's minimal knowledge of my actual Github profile.
At this point it was pretty evident that I was corresponding with a bot. They were running different set of algorithms against different set of people, trying to analyze the results.
Hey Toni, Founder of source{d} here. First of all my apologies for the bad experience. This should have not happened. We're a team of developers ourselves (no recruiters) working on making sure that these kind of situations don't happen to any developer (we started this because we were fed up with the bad practices in recruitment). We're definitely not a bot, I can promise you this. Every email gets read by a developer themselves (our team: http://sourced.tech/about) and personally answered. If you send me an email ([email protected]) I'll personally figure out what happened here.
This is actually a really cool idea, like I'm kind of obsessed with the idea of using custom attributes / aspect oriented programming using C#. I don't expect to ever be contacted by a recruiter for purely that fact... but if they saw my code... they might. That's cool.
On the other hand, i'm more of a consumer of open source software than a producer. I tried submitting a pull request once, it got rejected, and I decided it wasn't worth the time.
Yep is a very similar approach, I'm not familiar with gitgo, but we started to work on go-git before gitgo was published, so this is the reason why we have our own project instead of collaborating on a existing one.
Hi Gustav! It is, all though these days we're named source{d}. We're working on some very cool visualisations to release later this year that allow you to dig in on all of the insights we've learned from your code. Right now there is no way yet, we're completely emerged on focusing on improving our backend (and doing some very cool stuff around deep learning to analyse your code). I'll keep you posted once we release.
What are the chances someone could use this to build a tool to provide structured output for git commands.
SVN had the --xml flag for pretty much every command, allowing for 100% parseable output, with git ( in particular git log) there is no 100% solution - the best you can do is use --pretty=format and create delimiters you hope aren't used in the commit message (or author names/emails, etc) itself.
The output doesn't have to be XML. JSON or even escaped CSV would be fine.
Golang is the new Java. Google designed it for legions of corporate systems coders. It is ultimately destined to be seen as the enterprise language that it is [twenty years ago all the cool kids loved Java]. Google policy is no map function for you, it's just more palatable to bake it into the language than an HR document...it's still pure policy steeped in pointy haired logic.
Don't get me wrong, it's better than it could be: at least it doesn't have something equivalent to UML diagrams. But it's still a corporate policy. It just feels refreshing because...wait for it...it brings garbage collection to C++ programmers. And where have we heard that before?
When learning a new language for a real problem, I'll go back to things I've written before and rewrite them in the new language.
The core logic is already figured out, so the exercise helps me match up constructs and try to apply the new language idiomatically. Then I can go back to my original problem with more ideas about how to use the new language effectively.
That kinda sorta makes sense given the feeling that "cgo is not go" (http://dave.cheney.net/2016/01/18/cgo-is-not-go). Without cgo no FFI, without FFI you have to reimplement whatever you need in the host language.
Go's lexical scoping and first class function/method's owe a lot to JS for leading the way IMHO. That said, it's "object" system is almost the complete reverse. JS is methods with data, Go is data with methods. It's an interesting contrast.
I once had a cold-call recruiter tell me Go was worthless. I asked the recruiter to never call me again and hung up.
People whom are both disrespectful and unable to see where their hockey puck sports analogies will be later on have marginal utility and are likely liabilities... don't get involved with those sorts.
[+] [-] toni|10 years ago|reply
Usually At this point, serious recruiters will do call you. But instead, he wrote that before going any further, he would like to ask me "a couple of quick questions" and requested if I could email him back my answers.
The kind of questions I was supposed to answer were pretty amusing: for example, one of the questions involved telling "If I live near Country A."
But he could easily find this out by looking at the country code of the phone number I just gave him in the previous email. My location is also public on my Github profile, so he could have easily found out that I live in Country B. which is around an hour away from Country A. The rest of the questions were also showing the recruiter's minimal knowledge of my actual Github profile.
At this point it was pretty evident that I was corresponding with a bot. They were running different set of algorithms against different set of people, trying to analyze the results.
[+] [-] eisokant|10 years ago|reply
[+] [-] swalsh|10 years ago|reply
On the other hand, i'm more of a consumer of open source software than a producer. I tried submitting a pull request once, it got rejected, and I decided it wasn't worth the time.
[+] [-] patrickg|10 years ago|reply
Edit: this is the backend used in https://ctanmirror.speedata.de/ a "travel back in time" archive of CTAN (back to 2013-03-17, IIRC)
[+] [-] goda90|10 years ago|reply
[+] [-] jerf|10 years ago|reply
[+] [-] mrdrozdov|10 years ago|reply
[+] [-] mcuadros|10 years ago|reply
[+] [-] Gurrewe|10 years ago|reply
Is there a way to see what information sourced has about yourself?
[+] [-] eisokant|10 years ago|reply
[+] [-] stephenr|10 years ago|reply
SVN had the --xml flag for pretty much every command, allowing for 100% parseable output, with git ( in particular git log) there is no 100% solution - the best you can do is use --pretty=format and create delimiters you hope aren't used in the commit message (or author names/emails, etc) itself.
The output doesn't have to be XML. JSON or even escaped CSV would be fine.
[+] [-] xiaq|10 years ago|reply
[+] [-] brudgers|10 years ago|reply
Don't get me wrong, it's better than it could be: at least it doesn't have something equivalent to UML diagrams. But it's still a corporate policy. It just feels refreshing because...wait for it...it brings garbage collection to C++ programmers. And where have we heard that before?
[+] [-] thebouv|10 years ago|reply
When learning a new language for a real problem, I'll go back to things I've written before and rewrite them in the new language.
The core logic is already figured out, so the exercise helps me match up constructs and try to apply the new language idiomatically. Then I can go back to my original problem with more ideas about how to use the new language effectively.
Plus, it's fun.
[+] [-] masklinn|10 years ago|reply
[+] [-] insertnickname|10 years ago|reply
[+] [-] donatj|10 years ago|reply
[+] [-] dh997|10 years ago|reply
People whom are both disrespectful and unable to see where their hockey puck sports analogies will be later on have marginal utility and are likely liabilities... don't get involved with those sorts.
[+] [-] shazow|10 years ago|reply
https://src.sourcegraph.com/go-git
This one is a fork of gogs' git implementation that I worked on briefly.
[+] [-] zwerdlds|10 years ago|reply
[deleted]