This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2018-01-18
Channels
- # architecture (25)
- # beginners (57)
- # boot (3)
- # cider (38)
- # clara (6)
- # cljsrn (6)
- # clojure (54)
- # clojure-china (4)
- # clojure-greece (1)
- # clojure-italy (3)
- # clojure-romania (1)
- # clojure-russia (7)
- # clojure-spec (68)
- # clojure-uk (46)
- # clojurescript (73)
- # community-development (2)
- # core-async (7)
- # cursive (17)
- # datomic (143)
- # duct (2)
- # emacs (12)
- # events (5)
- # figwheel (3)
- # fulcro (15)
- # hoplon (19)
- # jobs (12)
- # jobs-discuss (85)
- # nginx (3)
- # off-topic (111)
- # onyx (7)
- # other-languages (1)
- # re-frame (30)
- # reagent (19)
- # remote-jobs (1)
- # ring (7)
- # rum (1)
- # shadow-cljs (18)
- # spacemacs (4)
- # specter (4)
- # sql (24)
- # test-check (1)
- # unrepl (10)
- # vim (6)
- # yada (1)
https://blog.expensify.com/2018/01/08/scaling-sqlite-to-4m-qps-on-a-single-server/ boring tech is the best
bash q: this wrapper
my_rebase(){
git rebase "@"
}
doesn't pass its arguments to the wrapped function.
normally "@"
works, so I guess git is doing something funny. any hint?is https://clojurians-log.clojureverse.org/ still working? it seems to stop sometime November. Is there another archive?
LOL, tried to throw an exception to test something, but then the throwing failed and I got a different exception!
(throw "Test exception. To be removed.") ;; ClassCastException :-D
I'm working on this: https://github.com/bpiel/guildsman
I took the official TF JNI bindings and made some small modifications, partially helped by the TF-scala project
I took A LOT of inspiration from this guy: https://github.com/eaplatanios/tensorflow_scala
that's a tricky question to answer. I intended to get an alpha out in Nov. I'm really trying to release something before the Jan is up. But, I also presented some working demos in Oct at Conj: https://www.youtube.com/watch?v=8_HOB62rpvw
anything specific you're trying to do? I could attempt to answer whether or not it'd be easy/hard/possible
OH also, if you're open to writing c++ and contributing to TF directly, note this: https://github.com/bpiel/guildsman#you-can-help
that links to part of the readme describing how you can help guildsman by making specific types of contributions to TF
also.. if you want to bring this conversation ON-topic somewhere (now or ever), there's #tensorflow
ok.. I've got to catch a train to work. Let me know if you have any questions/thoughts/etc
@pablore @bpiel: there's also 1. mxnet and 2. jcuda if you're willing to deviate from TF a bit
well i know c++ and am interested in digging into ai stuff but machine learning seems to have a very steep learning curve and i dont have much time to devote to it yet 😞
@jgh I think the steepness of the learning curve depends on the individuals comfort level with the related math
However, I can say that making the contributions to TF I mentioned earlier does NOT require much knowledge of math/ml
Am I the only one who find it really difficult to find gigsin Clojure coming from different technologies. Over the years I worked with ruby, python, golang, angular, react at a seniority level and before jumping to each of those I was not familiar with the tech in question. I feel like people hiring in the clojure community put unnecessary barriers. I may be wrong so I'm curious of the reasoning why no one is willing to hire a professional familiar with other stacks who's really interested in Clojure. Basically the only community where I apply to job I get answer such as "You don't fit the profile" we're looking for - it is really a turn off
@lewix anecdotally I’ve seen a fair number of hires and none of them knew clojure before coming on board (current job is 100% clojure, jvm clj on the backend and cljs browser frontend) - but we rarely need to add more people; I can’t answer for any of the people that failed to hire you of course
@noisesmith where they white? just curious
(seems like a good discussion for #jobs-discuss BTW -- since we've been talking about exactly this recently)
two years ago it really frustrated me so i gave up on clojure and went to work with something else. Recently i tried again and same thing.
@lewix yes, we are in one of the whitest cities in the country which could be a factor
The only feedback they gave was 'don't fit the profile', with no details on what that profile might be?
@fellshard right
A lot of companies hiring for Clojure seem to not have bandwidth / budget / time to train new-to-Clojure folks so that narrows the field a lot. Some companies are willing to hire new-to-Clojure folks and train them, but it's a smaller pool.
@fellshard: Legal/HR probably won't allow them to say anything
And you've also got to realize that the desire to do Clojure is high and widespread so candidates completely outstrip available positions.
Even when we were hiring for other tech roles, because folks knew we did Clojure, we got a lot of people applying to those other roles who really wanted to get into the Clojure work instead...
@seancorfield that is a good point but I wish they said that they found better candidates as opposed to say I do not fit the profile.
I received an answer very quickly less than a day and still the same thing - you do not fit the profile
That's just "HR speak" in my experience -- companies are often very limited in what they can tell unsuccessful candidates (assuming they tell them anything and don't just ghost them).
Hiring / job searching is an area I have very little experience in, so a great deal of what I hear is hearsay. That said, being turned down without any feedback at all is... aggravating, to say the least.
We have a JIRA workflow that both HR and hiring teams use -- and that ensures there's a "contact unsuccessful candidate" step for every candidate.
our team did hiring at my last job. company was big enough to have big HR department. we didn't handle rejects, HR did. so there wouldn't be any meaningful feedback from that
@fellshard: Anything the company tells you is grounds for discriminatino lawsuit on your part -- therefore, in a really shitty game theory way, the company is best off not telling you anything.
They gain absolutely nothing by telling you why you get rejected, but open themselves up to all types of shitty lawsuits.
Ah, 'murica, home of the frivolous lawsuit... 😞
(Not saying that you are a litigious jerk, but that such people exists, and legal/HR is covering their own ass.)
I won't look for clojure opportunities anymore. I value my time more than anything, and it's not worth it. I think I'll keep on playing on the side with it though 😛
do what you need. but i can't imagine the two places that you have applied for clojure jobs give you an accurate snapshot of the clojure jobs available as a whole
Actually, have you tried making a few commits to cider (or some other open source project) ?
I bet if you can say something like: "cider is the most popular clojure emacs dev setup; I contributed the following features to cider"
For better or worse, OSS contrib does seem to be a vital factor in Clojure discussions
in the stack overflow survey recently, vim users outperformed emacs users in job interviews. i don't put much stock in how good someone is as a programmer based on what languages they use. except forth. those people are geniuses
I'm not sure if this debate is going anywhere productive, but when someone tells me they have made elisp contribs, my thought process is: 1. this person understands scheme / recursion / lambdas / ... CHECK 2. this person cares enough about their craft to build their own tools ... CHECK 3. this person cares enough about their tools to use a dynamically scoped pile of shit .... CHECK 4. this person has the confidence / courage to build new things rather than a cookie-cutter view of the world as it is .... CHECK but maybe I'm reading too much into programming elisp
> 3. this person cares enough about their tools to use a dynamically scoped pile of shit .... CHECK hahaha perfect
I'll remind everyone once again that a lot of good programmers cannot contribute to OSS, either because of restrictions imposed by their employee, or because their lifestyle doesn't allow time to work on software-as-a-hobby outside office hours (for reasons that are perfectly valid). Leaning on "candidate has OSS experience" may bias you against better candidates that don't/can't.
(remember: you just talked about irrational and unfair discrimination above!)
afaik, "has open source contribution" is neither a protected class nor something determined at birth, it's more akin to discriminating on skills
@qqq Demographic analysis shows that a lot of protected classes do not contribute to OSS so, yeah, it's a good indicator of discriminating against protected classes.
(and it's partly because the OSS community is often harsh on such folks)
@seancorfield does that take into account that protected classes often dont participate at all in the tech industry?
Not saying it should be that way, but rather simply that it is, again for better or worse.
The percentages in OSS show that even proportionally those folks are way under-represented in OSS so, yes, it takes that into account.
Heh, if you're genuinely interested, I can probably point you to all sorts of intersectional material on the topic...
Differing incentives. In a sense, OSS contribution is a luxury afforded by having time and energy to spare.
@seancorfield: genuine, non rhetoric question: do you know any legal precedence for situations where "we want OSSS contrib" has been prosecuted as "discrimnation vs protected class" ?
@qqq See above comments about how hard that would be to prove as discrimination...
@seancorfield i think that would be an educational read if you have material at hand, otherwise i can probably use the googles
...besides, it's not what I actually said: I said that by favoring OSS contributions you are likely to bias yourself against good people who can't participate, without even knowing it.
And it may not be active discrimination, but rather accidental or unintentional; conflating the two categories would not be helpful to the industry, either.
@jgh Here's a reasonable place to start https://adainitiative.org/2014/01/24/guest-post-whats-wrong-with-meritocracy-in-open-source-software/
(I'm hoping folks are familiar with the Ada Initiative?)
Yup, other organizations carry on their work.