681–690 of 704 posts
Someone posted a page here on the topic, and it was a revelation. It still feels wrong to tie my shoes correctly with amount of muscle memory I have. and it’s extra embarrassing given that I spent a fair amount of mental effort on knots in my youth.
Earlier quoted context omitted.
I was once asked about Slack, fortunately they were already a colleague
Man I really hope other people get this one, because it is awesome.
Earlier quoted context omitted.
They could have used any hashmap or dictionary in the first place... The DB solution was far more complicated.
Delivering the over-complicated feature and improving the performance of the over-complicated feature both seem to get more praise than shipping the simple version to begin with.
Earlier quoted context omitted.
Thanks for sharing! So, a question in balancing the regret against knowing what you know now. This situation sparked a change in you to recognize how to handle these situations better. Would you make the same mistake again in order to learn the lesson?
Absolutely not. I would hope to learn the lesson some other way. In hindsight, it equates to kicking someone hard in the groin for laughs. It hurts my foot, them a lot, and it's just a poor way to learn how to earn "respect".
I worked as a sysadmin for a whole year before learning tab->autocomplete in linux
* I learned Scheme after Perl and JavaScript. I strongly advise that this is the wrong order. One should learn C (or C++, if you must), then an assembler, then a Lisp, then everything else. There’s no point trying to be prescriptive about the rest, but trust me on those three; however you got started - and I got started with BBC BASIC, Acorn BCPL, 6502, and Modula-2, if you can believe it - however it goes, make sure…
The trigger for seeing that I don't have enough interviewing skills was during an interview, the interviewer replied to my answer with, "Okay, I guess that's one way to answer the question..."
In 1993 I was interviewed for an operating job in a power plant for a major airline, assigned to their data center. At my current job, I was working in a high rise office building with sixty-six floors. The operating system computer was a JC8520, which was running a version of MS-DOS. All commands had to be typed in correctly or nothing would happen. While operating the plant, several commands had to be entered every…
That is how a conversation between mature adults should be. Contrast that the typical today's IT interview questions, all posed to prove that is the interviewer is of superior intellect.
* I learned Scheme after Perl and JavaScript. I strongly advise that this is the wrong order. One should learn C (or C++, if you must), then an assembler, then a Lisp, then everything else. There’s no point trying to be prescriptive about the rest, but trust me on those three; however you got started - and I got started with BBC BASIC, Acorn BCPL, 6502, and Modula-2, if you can believe it - however it goes, make sure…
Do you think you'd still be thinking about it if it wasn't Bono?
Earlier quoted context omitted.
You must have absolutely nailed the rest of the interview!
It was the early nineties. If you've touched a computer, companies would assume that any skill gap you had you could straightforwardly bridge yourself, on the job. It wasn't like today where you have to be a perfect cinnamon roll of a candidate who ticks all of HR's required-skill checkboxes before you can move on to the grueling 5-6 rounds of interviews.
He knew I was doing computing at uni and that seemed to be enough.