cja23 | 6 years ago | on: Absolute truths I unlearned as junior developer
cja23's comments
cja23 | 8 years ago | on: How to Become a Good Theoretical Physicist
cja23 | 11 years ago | on: The Statistical Crisis in Science
cja23 | 12 years ago | on: Ask HN: How do I honestly display my education on my resume?
cja23 | 12 years ago | on: Math is not necessary for software development
We don't teach every child math because we want them to become mathematicians or anything in the STEM fields, just like we don't teach them PE (physical exercise) because we want them to become professional athletes. We have mandatory PE classes because having a fit and healthy body will serve you (and society at large) extremely well no matter what you end up doing in life. In the same vein, we have mandatory math classes because having an agile and skilled mind will also serve you (and society at large) extremely well no matter what you end up doing in life.
The article claims written communication and reading comprehension are so much more important than math to a developer. This is like saying catching balls and breaking tackles are so much more important than push-ups, pull-ups, or all the weight-lifting you do in the gym. Learning math is a great way to enhance and improve your communication skills! Try explaining some advanced math concept to a kid sometime.
cja23 | 12 years ago | on: Ask HN: Is it possible to be very good in multiple languages?
Once you are in the linear portion of the technical skill curve, your hire-ability is much more strongly affected by the "softer skills": verbal & written communication, ability to think critically and express that thought, and the social skills to quickly assess your interviewers and establish a rapport with them.
After you get hired, better technical skill certainly helps, but it does level off. Also, it is not indepedent of the soft skills: I've known individuals with ridiculously impressive technical knowledge and skills, but their utter lack of communication/social skills not only hurt them career-wise, but actually made their high technical skill a liability at times.
cja23 | 12 years ago | on: "Careless" employees
It's definitely work to build and maintain that kind of culture, but I've had many people tell me it makes them want to come to work in the morning because they enjoy starting off this way. It also helps that I try very hard to make sure this is the one and only recurring "meeting" they have.
cja23 | 12 years ago | on: Introducing the Intel Galileo Development Board
cja23 | 12 years ago | on: What are your most common reasons for rejecting candidates after a job interview
2. Candidate ambitions / Job mismatch: this goes both ways. I have rejected candidates that were clearly just looking for the paycheck and would likely do the minimum necessary to not get fired. I have also rejected candidates that wanted to do a lot more than the position required and would likely get bored and move on quickly. (For the latter, I always try to find another position that would be a better fit, even if it's outside my group, company, or even industry.)
3. Culture/Team mismatch: this is the last, and rarest reason to reject a candidate, and is only considered if they passed the two above hurdles. If the candidate's work/communication styles don't seem like they will mesh well with the existing team, this is sufficient to reject the candidate, although my team needs to feel pretty strongly about this incompatibility.