Y
HN Search
Hacker News Search
new
|
comments
|
top
|
jobs
mjfisher
searching PlanetScale…
1.
▲
2.
▲
3.
▲
4.
▲
5.
▲
6.
▲
16 ms
·
151.
▲
by
mjfisher
7y ago
It's probably worth mentioning that any take home worth its salt will explicitly list what criteria you're being assessed on. It's crazy how many coding tests are poorly designed and waste a candidate's time. I'm pu
152.
▲
by
mjfisher
7y ago
Did anyone tell you why you failed the coding test stages? I'm putting together a best practice checklist for coding tests, and I wondered if you'd noticed any common themes.
153.
▲
by
mjfisher
7y ago
If you're just looking at the surface of the UI, the v1 release appears to include theming. There's a lot more to UI than that, but it might help it feel a bit fresher
154.
▲
by
mjfisher
7y ago
They absolutely should be artificial problems. If they're not carefully designed to test what the hiring company cares about, it's a bad test
155.
▲
by
mjfisher
7y ago
Talking to hiring engineers and job-hunting developers, I've come across a huge range of opinions about take home coding tests. In many cases, companies will still issue coding challenges without much thought about what they're wa
156.
▲
Coding Challenge Best Practice Checklist - techcnial recruitment test design
(candidatecode.com)
2 points
by
mjfisher
7y ago
|
1 comments
157.
▲
by
mjfisher
7y ago
Interesting, thanks for the response. Perhaps eventually ML could form part of a solution to that problem too
158.
▲
by
mjfisher
7y ago
Can anyone comment on how copyright and IP laws might play with this kind of concept? I can see accidental collision with existing branding, particularly if real world designs were ingested as training data. From what I understand that may
159.
▲
by
mjfisher
7y ago
I think the scenario you describe sucks for all kinds of reasons, but it doesn't have to be like that. If the coding challenge is for an early stage screen, you should be looking at about 30mins worth of work. If it's more in-dept
160.
▲
by
mjfisher
7y ago
Really helpful, as long as they're done well and respect the candidate as much as possible. In my experience, they provide a great way of understanding a candidate's skills. It also lets them work in a low-pressure environment wit
161.
▲
by
mjfisher
7y ago
It's been popularized, and I don't think that's a bad thing. It has spread fairly organically because it's not a bad starting point for a philosophy of life. I was introduced to the concept through Tim Ferris' podca
162.
▲
by
mjfisher
7y ago
The list of modules ( https://wtfutil.com/modules/ ) looks really quite impressive. I can imagine getting some good use out of this
163.
▲
by
mjfisher
7y ago
Hi Nate. I've recently launched a service for managing coding challenges for recruitment through git ( https://candidatecode.com ). I'm keen to start offering some lightweight integrations for a few ATS - is there anyone
164.
▲
by
mjfisher
7y ago
It's interesting to see how broadly the same experiences lead people in different directions. I loved iTerm2's window splitting and resizing so much I wanted it for all my windows. That lead me directly to install i3 on my Linux m
165.
▲
by
mjfisher
7y ago
I've never quite understood the rationale behind the 'public PR' method of submitting coding challenges. I understand it's much lower friction for the recruitment team, but having everyone else's answers public too
166.
▲
by
mjfisher
7y ago
Thanks; I've yet to meet any sql-wielding non-programmers in the wild. Perhaps it's worth releasing after all?
167.
▲
by
mjfisher
7y ago
I got quite excited by that entry. My immediate reaction was 'oh, that's really cool'. But after thinking a little further, I can't think of an audience that both uses SQL frequently and also couldn't use a git repo
168.
▲
by
mjfisher
7y ago
Interesting. I've got a feeling early stages of tech hiring pipelines are very poorly optimized at the minute; it's something I'm working on. Individual experiences help; thank you.
169.
▲
by
mjfisher
7y ago
I'm curious about the codepad/codeshare approach right at the first touch point. I fully agree that screening actual tech skill early on is important. Do you not find that you commit a lot of engineer time to codeshare interviews
170.
▲
by
mjfisher
7y ago
I couldn't agree more with the idea that you should move a 'can you code at all' test to as early as possible in your hiring pipeline. I used to wait to the first in-person interview to try simple fizzbuzz style questions (wi
171.
▲
by
mjfisher
7y ago
Not the OP, but I had eczema that required regular steroid cream treatment. It did get somewhat better in my twenties, but it wasn't until I started experimenting with different lotions and moisturizers that things got a lot better. In
172.
▲
by
mjfisher
8y ago
Or it's showing genuine respect for your employee's job, autonomy and skillset, and implicitly acknowledging that you probably aren't going to do as good a job as they would. "Mind if I take this call?" could easily
173.
▲
by
mjfisher
8y ago
Just to add a slightly different perspective: I'm comfortable with the notation and calculus involved, but had not known how backpropagation worked until now. I'm not sure if it's the same for others, but I don't find ba
174.
▲
by
mjfisher
9y ago
I've become increasingly interested in how people become offended recently. Offence tends to be bound up in notions of identity, and I think the way people offend and become offended is increasingly a factor in a world becoming more po
175.
▲
by
mjfisher
9y ago
I really enjoyed reading about Daniel Tammet and his book (Born on a Blue Day) is fascinating, but I'd hesitate to describe him as 'ordinary'. He's likely somewhere on the autism spectrum and also has synesthesia which a
176.
▲
by
mjfisher
9y ago
Just wanted to anecdotally affirm whalesalad's experiences with my own. I desperately wanted to like Django more than Rails (I just really appreciate python as a language), but I find projects much quicker to build in Rails. It really
177.
▲
by
mjfisher
9y ago
15% might be a stretch, but having your current git branch, rvm/node version etc displayed saves a lot of pointless command typing if you're jumping around between a lot of different projects, branches and libraries in the shell a
178.
▲
by
mjfisher
9y ago
I might be the first to say it, but this is very useful. I use zsh now, but put up with bash for years because I thought (entirely incorrectly) that a new shell meant new syntax and a drop in productivity while I learned it - and I've
179.
▲
by
mjfisher
9y ago
In reaction to some of the comments popping up re. OOP and functional programming: I've come across quite a bit anti-OO sentiment in my career now, and not nearly as much anti-functional sentiment. I suspect that the prevalence of OOP
180.
▲
by
mjfisher
10y ago
For learning RoR, I can't really recommend enough Agile Web Development with Rails 4 (although you might want to wait for a revised v5 version to pop up). It takes you through building a simple site with a shopping cart from scratch, a
More ›