timo614

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 better is to set a constant to the resize frame rate and then remove magic numbers so that people viewing the code would understand how it works implicitly without the comment like you're describing. That or improving the library such that it's more clear what's exactly happening.

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 behind why something was done.

For example: $.resize.delay = 16;

Was placed in one file of some code I collaborate on with the comment "// this is probably a horrible idea"

I had to ask the developer what exactly the code does (yeah I could have looked it up but since he said it was a horrible idea I wanted to know why). Turns out it just configures the jquery resize event to fire at about 60 frames per second.

Having a comment like: // Configures jquery resize to fire the resize event approx 60 frames per second

Would have made the code a bit easier to understand.

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 patterns (the GOF book is very course-bookish but there are friendlier head start books if you're just getting into it).

To be honest though I'd say the best learning material I experienced was just surrounding myself with people who know more than myself. Ask for code reviews (don't just get forced to do them) from people you know to be excellent developers (not the easiest thing to spot when you're green though).

Also never stop learning whether it's through a degree or online through one of these sort of courses.

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 a few minutes to actually think before you code the actual implementation time is usually on par (assuming you're not working in system that has allowed bad programming practices to take place; isn't DRY, etc.).

I've worked with people that copy and pasted half of their code base on a few occasions. Whenever a change needed to be made to a few of the more complicated systems you had to give it to the original 'rockstar' developer because he was the only one who knew every location it was used in the system.

To me it's just a sign of laziness. The effort to introduce design patterns and keep your code DRY is trivial. Just keep scope in mind and don't build systems to anticipate unforeseen features.

I do get the whole MVP we need to get it out the door argument but usually if you hire people who know what they're doing and aren't just an inflated ego (we all know those sorts of developers) it's really not a problem because they'll take the few minutes to think before they implement.

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 likely at least the interest on the bonus if not wages up until it was paid).

"Unpaid wages, including commissions and bonuses."

http://www.dir.ca.gov/dlse/HowToFileWageClaim.htm

Either way it's a moot point now.

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.dir.ca.gov/dlse/HowToFileWageCLaim.htm "Unpaid wages, including commissions and bonuses." "A claim based on an oral agreement must be filed within two years from the date the claim arose."

Personally I think they lost their case as soon as their executive mentioned that the reason they would withhold payment was because of mistakes made on the job. By doing such they appear to acknowledge the debt and state their reasoning for not complying with payment is related to such reasons. Regardless of any future emails that kind of breaks CA labor code as far as I know. I'm not a lawyer though so what do I know.