Good morning any one can help me with his experience???????

Question

I'm a beginer in java programing and i wanted to see for my future. that means in future of my plans in programming. I'd like to be a good programmer by using Java language. but i want from you to suggest me which steps should I take to do that.
waiting for your suggestions.................
bye
Message was edited by:
Programers

Answer 1

ok, step 1. invest massive amounts of time in learning. write code. a lot. if it doesn't work, which it won't, find out why
step 2. work out at least a vague career plan. do you really want to be a programmer? I mean really? you might be enjoying yourself cutting a bit of code at home, but it's an entirely different game programming commercially. chances are you'll be working on and maintaining other peoples code a lot of the time, and unlike coding at home, you'll have actual real deadlines that actually really matter, and you'll actually really not enjoy missing a deadline very much at all. you won't be just writing code you want to write, more often than not somebody else will give you a set of requirements to implement, and if you're lucky you'll get a say in what they are. of course, you won't be working alone, so you'll have other people waiting for you to finish what you're working on, or you'll be held up waiting for somebody else to finish what they're working on, neither are attractive prospects. and the damn thing has to work, so you'll have hours of endless fun testing it, being told you got it wrong, having to re-do stuff and suchlike. you'll estimate that something will take you, say, 16 hours to write, and then halfway through those 16 hours you'll realize you're miles from the finish because sockets don't quite behave as you first thought they did, or actually, that widget isn't particularly reliable after all. so you've got 8 hours left to do 15 hours work, plus undoing all the wasted effort so far. if you're really unlucky, you'll have just tons of ceremony to follow, especially if you land a "cushy" public sector job, only to be told that, yes, they still use and follow SSADM, so goodbye getting any work done, hello tons of paperwork and rigmarole
then you find that, oops, I did quite well at coding back at uni, but now it's the real world, and, well, all those OO skills I thought I'd gained are actually pretty much valueless, so it's down to the bookstore to spend a fortune, and lots of late night catch-up sessions, because the world doesn't stand still, and in particular software development doesn't stand still, so it's either a constant struggle to keep up with the tide of new information - you want to be marketable, don't you? - or you find some dead-end job nailing new functionality onto the sides of ancient legacy systems written on an Atari ST 15 years ago, only they were only ever designed to do one thing well, and with every new module shoehorned into it you can actually hear it groan and creak and you just know you're doing a terrible job, professionally speaking, and nothing to be proud of at all but it pays the bills. until you get bored and want to leave, only to find that - yep, you've guessed it - your skills are murderously out of date, knowing Java isn't enough any more, there's J2EE to contend with, and you don't want to learn about EJB cos they're so horrible, but everyone still wants you to have the skill, or they think they do, as well as JSP and Servlets, and oh have you ever deployed this on Linux or HP-UX? and the frameworks. oh! the frameworks! every damn company you look at working for has a totally different set of tools they use, and although it's technically all just SQL they'd prefer if you'd used Oracle, or SQL Server, or DB2. what? what's object-relational-mapping, you cry! so it's back to the bookstore again, more late night sessions. or maybe you choose a professionally run training course, only that turns out to be run by some other guy who didn't really know what he was doing, and decided "yes! training! that's where the money is!" and is basically re-hashing some exercises out of Connolly-Begg or something, and is basically a months salary down the drain. by this time you might be thinking "well, this isn't at all what I thought it would be", but it's too late now, you're a coder and there's no denying it. you think about looking at other areas, but that means either a huge pay cut, or more re-training. and all you wanted to do was write code for a living - it can't be that hard, you enjoy it at home right?
liking coding for fun and doing it for a living are a world apart. the absolute minimum requirement before even considering it is to have the ability to solve problems without other peoples help. well? what are you waiting for??