elanning

6 ms·

31.
by elanning 6y ago
Imagine you're a senior developer with over 10 years experience. You're happily employed and make good money. You're contacted by a recruiter for an interview. Perhaps the company even uses some software you wrote. "Ok t
32.
by elanning 6y ago
A lot of senior engineers would refuse to do a fizzbuzz. I'm really not seeing the problem here.
33.
by elanning 6y ago
I believe most programmers know a lot of this stuff, they're simply not trying to build a system that captures reality perfectly. They know Prince's name was a symbol at one point, but force Prince to confirm to their system with
34.
by elanning 6y ago
I think it does its job perfectly; gives them candidates who are willing to put up with 10 hour study sessions for weeks OR people who are naturally brilliant (and don't break under pressure while being watched). It filters out a lot o
35.
by elanning 6y ago
Couldn't agree more. If you care enough to nit, you should care enough to add an linter rule for it. I do realize sometimes that's simply not possible, but a lot of times, it is. I even wrote a custom vscode plugin to encourage de
36.
by elanning 6y ago
Sorry to hear. I hope you find something that works for you. I wish I could help, but like me, I'm sure you've already researched most solutions.
37.
by elanning 6y ago
I have suffered from fairly bad RSI/tendonitis issues since my early 20s. Now a days I have a split keyboard and use wasd keys for my mouse, which is slower, but causes less pain. I would not wish this kind of pain on anyone. It has gr
38.
by elanning 6y ago
https://marketplace.visualstudio.com/items?itemName=checkr.c... - Checkr: write simple code checks with regex for vscode. I strongly believe big libraries will come with their own easy to plugin static analysis rules as the
39.
by elanning 6y ago
Related to the article: I noticed a lot of style like nits that ESLint didn't cover, but also weren't necessarily worth pausing and writing an entire ESLint rule for. So I wrote checkr: https://github.com/ELanning&
40.
by elanning 6y ago
Will do, that's on the TODO list.
41.
by elanning 6y ago
During code review, I noticed many nits could be caught by static analysis. I also noticed many bugs I've run into could also be caught by static analysis. I looked into writing custom ESLint rules, but often they required more ceremon
42.
Show HN: Checkr – write project specific static analysis easily(github.com)
1 points by elanning 6y ago|3 comments