timo614

7 ms·

31.
by timo614 14y ago
Not surprised -- definitely agree that the code involved could be improved. That said there is a bit of a code smell to what you're describing; having separate functions just to set the resize event time is a bit much. What I think would be
32.
by timo614 14y ago
I'd say build your code such that you don't need to comment but comment wherever there is some unclear reason for why something is done. Instead of x+= n; running_total += total; But comments are helpful for understanding the reasoning beh
33.
by timo614 14y ago
Definitely agree. I had a CIS degree (not exactly computer science but some overlap) and I'd say some of the most helpful material I read to get myself on par with day-to-day developers was related to algorithms, data structures, and design
34.
by timo614 14y ago
Personally I don't get the argument that you can either have speed or well architected systems. Yes, if you build features outside the scope of the system to meet unforeseen features it's just scope creep and a waste of time but if you take
35.
by timo614 14y ago
You can file claims with the department of labor for unpaid bonuses earned while working at a company. Anyhow he was still working at the company at the time he should have been paid so the money was owed to him and he could have filed (for
36.
by timo614 14y ago
Contact the CA department of labor and ask them how strong your case is. CA's department of labor will handle the process of arbitrating any unpaid wages and can likely tell you about labor law much better than most people here. http://www