Please ignore post, I have no idea what I am talking about.
Group is the operative word. All trades have their beginners. Every trainee plumber has to change their first tap washer or connect their first capillary joint with a blowlamp. Every electrician has to wire in their first fusebox. And each of them is one of a group, or maybe better cohort. There are lots of people in that same position, and potential employers know that. That is why they have training jobs (called entry level), and if you are any good you will progress rapidly to double the salary and double the responsibility. If I remember correctly, the film shows the programmer describing how she went from beginner to craftswoman.Paul Clements wrote:. . . I count myself in the first group. . . . to be part of the second group must be difficult. IT is a trade/skill . . .
William Barnes wrote:Everyone is different. If someone finds Java easy, and they post that, that is their opinion. How many different languages have you used?
> I don't believe there are any easy languages especially if you want to be a good developer.
That is a bit of a strange statement.
Fergus Flanagan wrote:I've never used OO languages at the coal face and TBH never had a proper understanding of the methodologies around OO. Which is why I'm now finding Java a tough challenge.
Paul Clements wrote:My experience of a few weeks on this forum as that there are essentially two distinct groups of "newbies" on here:
Experienced IT professionals (i.e. multiyear experience of the entire project life-cycle, including coding/development, testing, deployment, maintenance etc) People new not only to Java but new to programming and a formal IT career
I count myself in the first group. As such I have zero anxieties about actually learning Java. My underlying worry is getting taken seriously due to age and lack of commercial Java experience. However, I am determined to give it a year and see what happens.
Personally I think to be part of the second group must be difficult. IT is a trade/skill - I'm not sure some people realise that. You don't just become a programmer. You need to have a logical, problem-solving mind which is capable of breaking things down into component parts. You also need patience and determination. Giving up on a problem isn't an option if you want to succeed in IT. People will be relying on you to come up with a fix. In short, it's not a job for either the faint or half-hearted.
All the best,
PaulC.
My underlying worry is getting taken seriously due to age and lack of commercial Java experience.
You also need patience and determination. Giving up on a problem isn't an option if you want to succeed in IT. People will be relying on you to come up with a fix. In short, it's not a job for either the faint or half-hearted
Paul Clements wrote:
Fergus Flanagan wrote:I've never used OO languages at the coal face and TBH never had a proper understanding of the methodologies around OO. Which is why I'm now finding Java a tough challenge.
If you spend time hammering home the basic constructs i.e. Classes, Objects, Inheritance, Polymorphism etc with loads of clear/fuss free examples then you should get it eventually. The worst thing you can do is plough on without a sound grasp of a language's building blocks i.e. focus on semantics not the minutiae of syntax.
Even though it's far from perfect, I would thoroughly recommend Head First Java as a great intro. Explains the basics very well.
Please ignore post, I have no idea what I am talking about.
Don't get me started about those stupid light bulbs. |