4 ms·
>Why did you name your variables like this? I never know how to approach this question, because often the answer is, "the problem is so simple and general to t
by dropit_sphere 11y ago
>Why did you name your variables like this?
I never know how to approach this question, because often the answer is, "the problem is so simple and general to the point that all variable names are either academic (solved computer science problem with technical name for each concept involved) or hopelessly generic ("counter").
When I code things that actually do things, I just name things what they should be called. I think functional programming makes this glib prescription much more tenable, as many of the things you write are abstract of the implementation, so you never find yourself naming something "screen_refresh_counter_for_process_x."
- edw519 11y agoSee. You're also proving my point. I don't give a shit about what you wrote on the page, I care what you have to say about it. Your comment tells me more about you than you imagine.
- dropit_sphere 11y agoMaybe so, but if that's the case, isn't the entire process a case of unspecified, morphing requirements? I'll flatter myself and assume you liked what you saw in what I wrote. But if that's the case, why code at all? Why not just sit down and have a short conversation? I feel like there's something about a rigorous, test-of-endurance interview process that feels professional. "We can't afford to hire anyone but the best." So experienced hackers with good instincts end up ignoring them in favor of a gauntlet they know is not representative of actual work.