endur

14 ms·

1.
by endur 3y ago
Not sure about intern, but I've onboarded a lot of new people and I love it. I just take 1-3 hours a day and have them share their screen and work on their task. Once they're comfortable, the sessions turn from a pairing session t
2.
by endur 3y ago
The timing slide caught my attention as well. 3 months for anything is fast...
3.
by endur 3y ago
This is more like going to people's homes and collecting their ballots than anything you've posted. You've eliminated all nuance in your replies. If you think you see a fire in a crowded building and you say something, even i
4.
by endur 10y ago
I was taken out to dinner and drinks, referred to as a new hire, and then ghosted. I had been interviewing for a while so it was fairly painful.
5.
Is there a good place to casually discuss programming-related questions?
19 points by endur 10y ago|21 comments
6.
by endur 10y ago
After reading, I wouldn't necessarily say he's 'gaming' the interview. It sounds like this guy really expanded his programming knowledge, wrote a ton of code, and learned to solve a wide array of problems. If anything, i
7.
by endur 12y ago
I'm getting tired of these pseudo-cool programming job titles. Guru, hacker, wizard, ninja. I haven't met many well-functioning, self-described ninjas.
8.
by endur 12y ago
Until you want to undo something! Nano is definitely more user-friendly though. Some of the engineers I work with still don't know basic vim shortcuts, like 'w' and 'b'
9.
by endur 12y ago
After googling this three separate times I finally just aliased it to an 'untar' command. I'll remember this for when I'm ssh'ed somewhere!
10.
by endur 12y ago
It just takes a while to be faster in the terminal than with the gui, and most people won't switch from the thing they're used to until they see significant advantages. I remember when I first started using the terminal, it was sl
11.
by endur 12y ago
Bash scripts are great if they're yours. My current project has ~20 large bash scripts that do all sorts of different things. They were all written by people who haven't worked on the project for two years. Anyone who needs to mak
12.
by endur 12y ago
I really like '!$' and '!:1' in bash. '!$' holds the last argument of the last command and '!:n' holds the nth argument. $ cd /big/long/path/to/this.txt Oops $ vim !$