The three skills with a lot less overlap than you’d expect:
-
The three skills with a lot less overlap than you’d expect:
1. Ability to code.
2. Ability to perform well in a coding interview.
3. Ability to validate code. -
The three skills with a lot less overlap than you’d expect:
1. Ability to code.
2. Ability to perform well in a coding interview.
3. Ability to validate code.I hate live-coding interviews. If someone is watching me, I forget how to even type. Obviously my 30+ years of writing code, all my open source stuff, my extensive resume, all those papers and conference presentations were just me faking it.
-
I hate live-coding interviews. If someone is watching me, I forget how to even type. Obviously my 30+ years of writing code, all my open source stuff, my extensive resume, all those papers and conference presentations were just me faking it.
@rk @norootcause ever since Google made me write code (not pseudo code, not math) on a fucking white board during an staff engineer interview, I have seen them as an indication of pompous douchebags hazing people.
Nobody writes code like that.
I honestly thought people were exaggerating how stupid they were.
-
The three skills with a lot less overlap than you’d expect:
1. Ability to code.
2. Ability to perform well in a coding interview.
3. Ability to validate code.@norootcause - Ability to ship code to production in a bureaucracy.
- Ability to ship code to production in a 3-person shop with no help from no one. -
The three skills with a lot less overlap than you’d expect:
1. Ability to code.
2. Ability to perform well in a coding interview.
3. Ability to validate code.3a: actual willingness/ inclination to validate code or check-ins.
-
@norootcause - Ability to ship code to production in a bureaucracy.
- Ability to ship code to production in a 3-person shop with no help from no one.@mistersql @norootcause wait, are the other two people computer-literate? Once it was owners and a coder (trust me, run the other direction if approached thusly). Once it was a sales / clerical and two nerds; that was a pretty kickass gig
-
I hate live-coding interviews. If someone is watching me, I forget how to even type. Obviously my 30+ years of writing code, all my open source stuff, my extensive resume, all those papers and conference presentations were just me faking it.
@rk @norootcause
But do you remember how to vibe? I'm told that's all that matters any more! -
@rk @norootcause
But do you remember how to vibe? I'm told that's all that matters any more! -
@norootcause @shriramk @rk isn't that what a prototype or say, a log visualizer or other tooling is for? I vibe so much "peripheral" things that are there mostly to help me play and understand the main problem, at which point I can hopefully do a fairly reliable review. Example from today, learning cozodb/cozoscript. full vibe, incredibly useful.
-
The three skills with a lot less overlap than you’d expect:
1. Ability to code.
2. Ability to perform well in a coding interview.
3. Ability to validate code.@norootcause They never seem to test me on the classic "can you duct tape something together that will come in under budget and somehow wheeze along without maintenance for 20 years?" question in those interviews.
-
undefined paoloredaelli@mastodon.uno shared this topic