Hacker News new | past | comments | ask | show | jobs | submit login

I've been coding for 30 years and I still have to look up syntax for case/switch statements. You ding me?



Seriously, that's just not super valuable information to have stored in your mind like that.

Sure I could, it'd be fine, but why store the entire syntax structure in my mind rather than a pointer to the location where I can find it in its most updated form?


I'm sorry, but what?


They have been coding for quite a while and are saying that they still look up the syntax for case/switch statements, because they cannot remember it off the top of their head. I am in the exact same boat, except with about a third of their experience coding.


I would definitely ding someone and think less of them if they claimed to be a senior engineer but couldn't remember how to write a switch statement in Java/C++. If you have to look things up you work slower and you don't understand nuances of e.g. what types can be used in switch statements in what language which limits your design skills.


Do cases fall through? Do I need to have them sequential? Can I put additional conditions on it? What if I have a case multiple times?

There is a surprising amount of complexity behind switch/case.




Join us for AI Startup School this June 16-17 in San Francisco!

Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: