Steps to Becoming the Java Developer
Developer 1: Blog
Set up a blog, and publish more than once a month. Do real research and make sure you do not sound stupid. Seriously, learn to write. Do the things your English teacher taught you: Create a plan, draw a story, and check the grammar and spelling. Then, with a lot of sadness, simplify it and shorten it to enough point where someone sweeping it will have an idea of what it is. The Internet does not tolerate nuance (nor my publisher).
Developer 2: Go Open Source
Do not believe the lies about open source. The youngest of you may not remember the days when a developer might actually be unemployed, but even in the darkest periods of the dot-bomb recession, all the developers of the open source project I started Were quickly back to work. Just make sure that the open source code you produce reflects the type of job you want. I wanted to solve difficult problems with the simplest possible solutions, but I interviewed developers who, as was clear from their open source code, wanted to complicate simple problems. Believe it or not, there is a market for it, but make sure your code reflects the market you are.
Developer 3: Not Six Months, Not 10 Years
Do not change jobs every six months. Seriously, the end of 100 percent job developer will come back. When this time comes, nothing will haunt you more than jumping work. On the other hand, do not stay in the same place doing the same thing for 10 years. You will become isolated and institutionalized. To remain valuable, you need to be familiar with more of how to encode the IBM stack while at IBM in the way of IBM. I have not hired anyone who was at IBM or a similar organization for more than a year or two. They usually impress me in the interview but fail the programming test.
Developer 4: Eye on the new stuff, hands on practice
Unusually young developers tend to work on the brilliant. Ruby is probably my favorite programming language, but it does not pay (average) as much as Java, and the market is smaller. This may not always be true. Scala looks like what happens on strong, but do not prepare yourself on the size of the market – it is not yet here. On the other hand, do not stay so long that you are the future equivalent of a COBOL developer or PowerBuilder either.
Developer 5: Write Your Own Documentation
I cannot tell you how many times I worked on a project, only to be pulled into an executive meeting because I wrote a document or a presentation that they saw and understood. I always start with an executive overview – that is, the page you really have to read – while the rest boils down to details in case you do not believe me. The question is: what does a busy person need to know about the subject if that is not the only thing they are working on? What most managers want to know: Who can drive this in the end and do me BS me on how it goes? Write that way.
Developer 6 : Brevity is the soul
One thing you learn about management right away is that people who know what they are talking about tend to give shorter, concise answers. When answers become long and complicated, this often means that they do not know or do not want to commit. You also learn that the tone is often inversely proportional to the importance of the subject. When bad news strikes, someone comes into the office, closes the door, and whispers. When something is not intrinsically important but disturbs someone anyway, they will try to elevate their prominence with an inflammatory tone.
Do not be that guy. Know what you are talking about, find out how to sum it up and the details, but do not load each sentence with minutiae and do not build the hype – the sky probably does not fall (but maybe someone should take a look at Jenkins Because we did not have a good build in a while). When all else fails, drive with the money. Make sure your numbers are well thought out, plug them into the charts, and clearly demonstrate that one point is superior to the other in dollars and cents.
Developer 7: Wow the crowd
Learn how to give presentations and learn how to speak in public. Search for a topic and make you at least one expert, if not the expert. Presentations to the public are generally.