that is awesome

I wish I could understand him better, but that's pretty cool.

Description of my advanced java class - I'm eager but I don't know if I was prepared well enough in my current class for this. It's a different teacher and it's my understanding that he moves REALLY quickly.

Anything I should brush up on before I start? I'm kinda murky on inheritance/polymorphism and we briefly did some abstract classes/interface stuff that really irritated me because I didn't understand the point completely, but it's not overly complicated I guess.

Basic syntax and algorithm stuff I'm very solid on. More advanced OOP concepts, not so much.

Swing! EJBs!

Just soak it up and you'll be fine. OOP takes a little while to get, but once you plow through enough examples – you should have an a-ha! moment or two.

If you want to post the stuff you're murky on – I'm sure plenty of people on here will be glad to try to help you conceptualize.

Seems like a bad deal. There are a lot of great cities with much lower cost of living where you can earn nearly the same money as NY it seems.

Shoe Lace,

You might also try contacting marketing/branding companies in your area and letting them know you are a freelance web developer. Some of these guys might end up giving you some subcon work when they need something done and you'll get higher rates from them than the average elance type job.

when I'm studying tomorrow I'll try to find a good example

we did a lot of stuff with the super and this keywords in our last test, and it doesn't help that she gives the wrong ****ing answers to them.

for instance:


Selected Answer:
A.
setVehicleAttributes("Blue");

Correct Answer:
D.
super.setVehicleAttributes("Blue");

this threw me for a loop, because it seems that setVehicleAttributes method in "Vehicle" is completely different than setVehicleAttributes in "Motorcycle" because in Vehicle it has a parameter, so in Motorcycle the setVehicleAttributes method is not overriding the Vehicle one, right? Since it inherits this method from Vehicle there's no need for the "super" keyword although I'm sure you could still write it that way but there's really no need to even have a new method in the Motorcycle class. I argued this one and she was sure I was wrong.

Wait, are you saying the teacher said A or D is the correct answer? I am pretty darn sure it is D. Color is not something that is unique to motorcycles but not all vehicles.

She says D is the correct answer.

I've tested the code and 'A' works. Since Motorcycle extends Vehicle and setVehicleAttributes(aColor) is a public method, I should just be able to write setVehicleAttributes("Blue") in the Motorcycle class and change the color to blue, right? No need for "super"

I am starting to come around to what you are saying. She should have made the code more detailed.

Everything you've said is correct except that access modifier doesn't really matter here - if it was private, it wouldn't be accessible either way and if it's protected/public it would be accessible either way.

Where are you taking this class and what are your teacher's qualifications?

Taking it at my local CC, she has a PhD but got it in the 70's. She told us she learned CS when they used punchcards. She's never taught java.

/facepalm

Shoe are you in the Boston area?

Yeah this is a good idea. I'm going to try and find some companies to do that for.


@Larry,
Nope, I'm in Long Island NY.

@Dave,
I have the same confidence issues. I'm not sure why either. I tend to always grab the uninteresting low paying jobs because they are easy to implement and I know with 100% certainty I won't have any problems delivering.

It's really really hard to break out of that way of thinking.

It's really funny how I never thought to market myself as a programmer/developer rather than an end to end web site guy. It didn't even cross my mind to do dedicated dev consulting work for other agencies.

Shoe, I recall about one year ago you said I was a programmer than you are, and you beat yourself up really hard for not having any CS knowledge. That always stuck in my head as your M.O. and I told you back then that your statement was patently false and I would say it today with no smoke and mirrors.

I totally get the pain of breaking out of mind-set loops. It is very difficult, no matter how much your brain tells you that the current situation if ****ed up. I'm 35, and it says a lot about me that I consider $20/hour some magical, unattainable number.

@Shoe,

These guys can clean up. I know because when we hire out to them at my company we always pay ridiculous prices, and for work that is far from outstanding. Just be sure you never extend more than a week credit (and probably not even that -- ideally, make them pay you up front to start). You could also consider contacting a high-end headhunter. The woman our company was working with, whose worked with a ton of big name SF startups you've heard of, said that even at salaries of 120K/year, demand was outstripping her supply. Hard to believe, honestly, but worth looking into.

Google gmail image caching broke a lot of things. Seems pretty evil to do that with no warning.

Seems like a good change to me. Or am I missing something (aside from breaking analytic related things for marketers)?

Anyone who is serving images that change just had everything broken and cannot fix it because Gmail is no longer respecting Email Headers and anything you put in there about caching gets ignored.

The 4 email trackers I use didn't break. There was a little bit of weirdness, but everything will be fine. The people affected basically have to write off their product working with gmail for now.

Right. I'm just wondering what are the use cases for changing images in an email? They all seem like cases where I'd rather they didn't change.

That's not to say a little notice wouldn't have been nice.

Countdown timers is one

Aren't all the analytic related 'images' unique URLs that wouldn't be cached?

Some are, some aren't.

Here's a quick overview: http://www.clickz.com/clickz/column/...mail-marketers

my java final was 100 questions and just had a lot of tracing and "what's wrong with this code" type questions. I hate those because I always rely on the compiler when I'm actually doing programming to catch that sort of ****.

tracing questions were easy, then she started using a lot of terminology I wasn't totally solid on because we never went into detail too much about pointers and memory allocation and stuff like that. Bunch of deep copy/shallow copy questions which were weird because we also never went over that stuff.

Then I kept finding typos all over the place which changed the answer to the question, so I never really knew if she made a typo on purpose or by accident so I kept having to call her over to check.

TIL i much, much prefer a practical test than a multiple choice test for programming. **** multiple choice.

Get used to it. That's how all the tests were for my first couple Java classes too.