This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
- # adventofcode (419)
- # aleph (8)
- # aws (6)
- # beginners (148)
- # boot (9)
- # cider (24)
- # cljs-dev (37)
- # cljsjs (8)
- # clojure (134)
- # clojure-android (6)
- # clojure-brasil (15)
- # clojure-dev (8)
- # clojure-dusseldorf (2)
- # clojure-greece (67)
- # clojure-italy (8)
- # clojure-japan (3)
- # clojure-russia (3)
- # clojure-spec (8)
- # clojure-uk (13)
- # clojurescript (54)
- # clojurex (6)
- # cursive (5)
- # data-science (12)
- # datomic (15)
- # defnpodcast (11)
- # emacs (25)
- # fulcro (95)
- # graphql (3)
- # lein-figwheel (1)
- # leiningen (27)
- # luminus (1)
- # lumo (6)
- # mount (2)
- # off-topic (112)
- # om (3)
- # onyx (24)
- # perun (3)
- # re-frame (20)
- # reagent (1)
- # reitit (2)
- # ring-swagger (13)
- # rum (10)
- # shadow-cljs (45)
- # spacemacs (24)
- # sql (2)
- # unrepl (78)
- # yada (1)
has any tech company managed to hire by saying: for your CV list your 20 open source commits you're most proud of for your interview, we'll just ask you abut the commits
naively, it seems the whole interview process is inefficient -- companies ask algorithms questions; candidates prep for interview questions;
in a alternative world, candidates just take the time they would have otherwise used, contribute to open source projects --- and companies just hire from open source project commit list for relevant positions
who would you rather hire, candidate with 'react' on cv or candidate who made a commit to react? candidate with 'mysql' on cv or candidate who contributed to a popular mysql documentation
I didn’t mean literally, but I have to believe that back in the day, when Red Hat hired people like Alan Cox and Uli Drepper, it wasn’t as if someone had them do a bubble sort on the whiteboard. It should have been clear from their well-known contributions to the kernel and the GNU compiler, respectively.
I was reading about how this algorithms thing is really new, ever since Google became the hotness. Apparently before that it was Microsoft's interview process that was copied.
https://danluu.com/wat/ > Back when Microsoft was ascendant, we copied their interview process and asked brain-teaser interview questions. Now that Google is ascendant, we copy their interview process and ask algorithms questions. If you look around at trendy companies that are younger than Google, most of them basically copy their ranking/leveling system, with some minor tweaks. The good news is that, unlike many companies people previously copied, Google has put a lot of thought into most of their processes and made data driven decisions. The bad news is that Google is unique in a number of ways, which means that their reasoning often doesn’t generalize, and that people often cargo cult practices long after they’ve become deprecated at Google. That whole article is really interesting, the length is an attestation to how much you will learn 😄
ahh, interesting. Not a fan of brain teasers as interview questions, unless your job is to write brain teaser books 😛
Today I saw that they announced "data class" for python. I was curious because I remember that they announced the same for java a few months.
So I went searching for "what is data class", then I find: It's a hype from kotlin-lang(2011) that add one more syntax to declare a class.
And it's avalible on clojure since
clojure 1.2 - (2010).
Not sure about
But in kotlin/python/java, it's a class with "dummy" getters/settes. Almost like beans, but with a newer/hype syntax.
Don ’t think so: there was a feature that didn’t make it into C# 7 known as record types that imitated the Kotlin syntax. https://github.com/dotnet/csharplang/blob/master/proposals/records.md
@qqq that’s the kind of idea that can cause unexpected side effects. For example it’ll bias your hiring on gender: iirc women for example contribute less to open source.
@lady3janepl yes, sadly that's a problem with almost any interview process, it's biased to a person's ability to conform to a specific view of what a "good" employee should be.
@lady3janepl Yes, that's very important to bear in mind about OSS. I will look at a candidate's OSS projects if they list them, but seeing their code is more likely to bias me against them if it's not good code. I don't consider a GitHub repo to be unequivocally a "good thing".
For example, I can hardly talk about, let alone show off what I've done for the past 4+ years of my life as it's all hidden behind NDAs and contracts.
I used to say that I considered a GitHub link or similar to be important on a resume, until I had it explained to me how much bias that can introduce.
@tbaldridge Yep, that’s another problem. The more involved you get in internal projects the less visibility you have.
If you look at the gender breakdown in software as a whole, then in OSS projects, it's radically different, unfortunately.
ah yeah. that's fair. I thought you were talking about the person with bad code and being biased against them. That's not bias that's just honest assesment
Same applies to talks, articles etc: not every position allows you to publish on what you’re working on.
@seancorfield I agree, I use Github simply as a gut check on a person's ability to code. If I go and see some odd paren formatting in Github then I get worried. If I see no code at all, then I'll dig deeper into design questions and the like
@dpsutton Right, if you don't have a GitHub repo, I won't hold that against you. If you do and you code is terrible, then I will consider that a black mark.
The worst sort of interviews is when the person has no GH profile, nothing they can show or talk about, and aren't even known in the industry. Then I have nothing to go on at all, and it makes it really hard hire someone. In those cases coding exercises are about the only tool left.
@seancorfield > a black mark what about code that was written many time ago or is just a throw-away code (say, some elisp hack) but is still stored at Github?
Terrible code in GitHub repo can also be a question of own code “good enough to work” vs code for others, prepared for reuse. TBH that’s why you can’t see most of my projects: I know people would judge me by their quality, but I don’t have the time to make them pretty, since they were explorations rather than products.
@tbaldridge I still find, even in that situation, that getting a candidate talking about their projects, what problems they ran into and how they solved them, what stuff gets them excited, etc... that's always a lot more valuable than a coding exercise. People can always be mentored and their code improved once they're onboard.
(There was a good article a month ago I think? About how open source code doesn’t necessarily mean open to contributions.)
@ghsgd2 If they only have bad code from several years ago and nothing recent, I'd ask them why they hadn't published anything recently. And it's usually easy to tell whether GH repos are "just storage" or actual projects.
You get to know their priorities; even if they don’t have much experience, you can see if they’re willing to be trained in the direction you want to go
But yes, when I look for black marks in the code, I'm not talking about "you should use reduce instead of apply", I'm talking about looking at some lisp and seeing this:
That can be fixed, but also says a lot about where the developer is in their learning cycle.
(foo (bar (baz 33) ) )
Definitely :) Bottom line is, github can be informative but also requires a lot of effort to process, so would be useful in a later stage rather than as an initial filter.
I think I've shared this before but I have a mind map that covers the areas I drill into in an interview... I don't always get into all of it, but it gives me a reminder of questions and ensures I mostly interview every candidate the same way...
I start in the top-right and go down that side, then switch over to the left, and start again at the top (usually -- some times I'll jump around a bit, depending on where the conversation is going with the candidate).
very similar to what we would talk about at last job's interviews. you can tell when people don't have any strong opinions about the left half
It's often hostile for men too as well - the latest example is Linus shouting at people I once published a patch for a bug and maintainer had an argument with me trying to prove that nobody ever needs it fixed. After lots of time wasted on discussion and refining minor details he accepted it but required me to sign legal documents and send them via post before merge.
It's part of my "mission" to get folks to stop doing those dreadful "coding monkey" challenge interviews 🙂
we hired a lot of interns in school or full timers right out of school. one of our favorite questions was what was your most favorite class and why, and then what was your least favorite class and why
@ghsgd2 Linus is a special kind of ass at times tho' (Stallman is worse). And I would challenge that it is "often" hostile to men.
also, you wouldn't get any code into clj or cljs without those legal papers. that's a real problem
those legal papers are electronic and 40 seconds away now so I don't see how that's a problem anymore
I'd agree with @seancorfield most of the "hostile to men" situations are not male specific, but just "hostile to all".
linus yells at people. but i've heard we only hear about him yelling so its kind of a survivor bias
Contributor Agreements are pretty standard for projects that are considered critical to companies' businesses. I've never understood why some devs seem so upset about them. But that's probably because I've also been on the corporate side and dragged into license auditing for projects 😐
like the FSF one doesn't give away your copyright, iirc (and I doubt the clojure one does, but I signed it so long ago I don't remember)
on the earlier point though, we deify people like ESR who are just genuinely unkind individuals. it's pretty messed up
also, most dudes don't get rape threats when they attempt to commit something or engage in the community, that's the difference
It's so weird that so much of "figuring out if a candidate is competent" is on the interviewer's side, when instead, if instead of listing keywords on CVs, every candidate just created a small github project demonstrating their use of that library/language, it'd make the interviewer's job much easier.
If you've spent 1000 hrs mastering a language/library, it's only 1% more work to spend 10 hrs setting up an open source code snippet showing how you use the language/library.
we discussed something like that. It kinda makes sense when looked at it as one thing to do. however, each job would like to see something current. and then applying for a job takes 10 hours or more, and multiple could easily lead to requiring a weeks worth of unpaid labor outside of normal hours of a candidate. and that's if the person has the time to spare to do this in the first place. we abandoned this requirement and went with a coding challenge that would take 1-2 hours at most and felt a little bad about that but figured it was a good compromise
What are folks' thoughts on Business Rules Engines? Are they useful? Are they a poor mental model for the logic they usually want to represent?
@fellshard I've used a few, really depends on what you're trying to accomplish and how the engine works
The worst one I've ever used was a pile of OOP gook where everything was controlled with events, and properties. So you'd set the property of an object it'd run a ton of rules and throw an exception if something failed
That was about the time I watched Rich's "Are we there yet" talk, and I just cried, lol
at my last job there was a rules engine built up over 15 years in vb5 (!) that we rewrote. it wasn't super pretty but we cleaned it up well and it processes medical billing to the tune of a couple hundred million a year
I guess the problem I tend to see when businesses reach for rules engines on reflex is that it doesn't end up being something the 'business experts' end up being able to understand effectively, much less modify. Are there tools to prevent that from becoming an issue as time goes on?
(Probably specifically addressing forward-chaining rules engines, e.g. Rete-based engines, Drools, etc.)
Right, so we should discriminate between business rules engines and production rules systems
Clara for Clojure looks pretty good. I think a GUI+something like Clara, could be pretty awesome, allowing users to do exploratory composition of rules. And they run really fast for streaming data.
So it ends up being a composable way of increasingly complex facts from a substrate of data. As long as you keep the number and breadth of facts in check - bounded properly by your biz domain - it would probably stay manageable
A little odd that Clara banks on side-effecting over producing new facts, but I guess the way facts are introduced to the system is up for grabs
Query engines - your data is relatively static, and you apply arbitrary queries to it
presumably you can add data to the query engine and add queries to a rules engines. is the distinction mostly based off usage? how does it affect the implementation?
Yes, the problem is, that with a query engine adding more data means you have to re-run all your queries. So it's really bad for stuff like airline reward points systems. Don't want to re-run queries whenever anyone buys a ticket.
And for the rules engine you have to re-run almost all your data through the engine whenever you add a new rule. So in production...don't update your rules much, parameterize them.
@tbaldridge Unless you have differentially/incrementally maintained query views (query result sets as semi-lattice structures): https://github.com/frankmcsherry/differential-dataflow/blob/master/differentialdataflow.pdf
I can't tell you the number of times though that I've seen companies try to process data streams by putting them in a DB and executing predicates/queries with every update.