I hereby claim:
- I am f1337 on github.
- I am f1337 (https://keybase.io/f1337) on keybase.
- I have a public key whose fingerprint is 21B3 9C7A ECB8 B241 1A97 5752 D327 3B7A C408 D88F
To claim this, I am signing this object:
--- build-gcc.sh.original 2011-11-18 18:28:59.000000000 -0500 | |
+++ build-gcc.sh 2011-11-18 18:29:01.000000000 -0500 | |
@@ -213,6 +213,20 @@ | |
exit 1 | |
fi | |
ABI="$OLD_ABI" | |
+ | |
+ | |
+ | |
+# via Jackie Gleason |
source '/usr/local/share/chruby/chruby.sh' | |
source '/usr/local/share/chruby/auto.sh' | |
alias ll='ls -la' | |
# set the bash prompt | |
function set_bash_prompt () { | |
SEPARATOR="" | |
STATUS_COLOR="" |
I hereby claim:
To claim this, I am signing this object:
https://github.com/f1337/qmk_firmware/blob/master/keyboards/atreus62/keymaps/f1337/keymap.c
http://www.keyboard-layout-editor.com/#/gists/f798ce77dfa02f79bfa9ae0f93d3619d
[{r:10,rx:2,y:-0.1,x:2},"3"],
[{y:-0.65,x:1},"2",{x:1},"4"],
These are my favorite interview questions. They don’t include coding problems, at all. You can learn that stuff better from interviewcake.com than from me anyway. 🙂
Tell me about a particularly difficult problem you solved recently – technical or not. Give me the gory details.
^ I ask a lot of probing questions based on the answer.
What accomplishment in your career or life are you most proud of? Tell me about a professional mistake you made recently, one with consequences, and how you resolved it.
^ I’m most interested in the topics chosen for both of these. I am way more impressed with answers that involve social consequences. It indicates a lack of empathy to me when the answer is 100% technical.
For the first decade of my career, I crash learned frameworks and tools, bullshitted my way through the interviews, became an expert on the job… Then used that expertise as a platform to bullshit my way into the next level. Rise and repeat, and here I am.
True, I learn very, very fast. And I'm obsessively curious. But I also game the interview system…
In the screening call, I ask about the tech stack, specific pain points the team may have, anything I can use in the next interview to better position myself. Then I crash study every tool and framework they use that I don't already have mastered. I also look up solutions to organizational pain points, and mention possible solutions ("you may have already tried this…") to demonstrate leadership thinking.
^ FWIW, experienced tech interviewers will recognize that I'm doing this, but it is counted as a POSITIVE attribute: proactive problem-solving.
I only take 1 interview per day. This is probably an autistic coping mechanism, because anxiety, but I find that i
We are a network of former & current colleagues who have enjoyed working together in the software industry, and who support one another in our ongoing careers. Some of us work for stealth startups, some for Fortune 10 companies, and most somewhere in-between. We share advice, review resumes, discuss interesting new technologies & processes, post job opportunities, and geek out about space & music.
The current admins are: