Popular @
Forum Controls
Spotlight Features
The Rich Engineering Heritage Behind Dependency Injection
Andrew McVeigh takes us on a tour of the rich heritage behind dependency injection, what it represents, and tells us why its here to stay.
NetBeans 6: Matisse Updates
NetBeans 6 delivers great updates to the Matisse GUI builder. Spend a few minutes with Roman Strobl and get an expert briefing on what's new and what has changed. (sponsored)
Introduction to Groovy Part 3
In this, the third and final installation of Andres' Introduction to Groovy series, you learn about how Groovy handles variable numbers of arguments, named parameters, currying, and more about Groovy operators. Including, some new operators.
Easier Custom Components with Swing Fuse
Swing Fuse (actually just Fuse), is a framework designed to make it easier to create your own custom desktop components. In this article, Daniel Spiewak shows you how to get started and provides sample source code you can download.
Benchmark Analysis: Guice vs Spring
Willam Louth shows how he uses JXInsight Probes to investigate probable performance issues with code bases that he is not familiar with. He also highlights possible pitfalls in creating a benchmark, as well as in the analysis of results.
Out of Bounds : Avoiding Career Protection Faults
At 2:42 PM on Jan 31, 2006, Matthew Schmidt wrote:
Fresh Jobs for Developers Post a job opportunity
Despite all of this, I keep facing resistance, and I don't think the team likes me very much. Many of my suggestions aren't adopted, and several people have replied with what I suspect is thinly veiled sarcasm.
Read on for the whole article!
5 replies so far (
Post your own)
Re: Out of Bounds : Avoiding Career Protection Faults
Excellent article. It had all of my thoughts and a lot more. I have been guilty in the past of exhibiting some of those traits myself. Trying to understand what makes a software development team tick is sometimes more interesting than the development of the software itself.When one joins a team, the first task ( apart from understanding the product that needs to be developed ) is to understand team dynamics, how the team functions, behaves, interacts and communicates. After gaining the respect of the team through hard work and delivering good results over a period of time, one can then suggest improvements. Infact by that time, once you are accepted into the team, the members of the team will start discussing with you the shortcomings of the processes and the software. That would be the time to provide your input and slowly introduce your thoughts into the discussion. Like a lot things in life, it is easier if the change comes from within.
Re: Out of Bounds : Avoiding Career Protection Faults
This article is a useful read, especially for young people starting their IT careers. Many of them are expecting a new project to be a state of the art software roller-coaster. But reality is different and some people can not adjust themself to such a slow animal as a corporate IT world.The only problem with this article is that it's too long. Not everyone will have a patience to read it to the end, which has a nice summary not to be missed.
Re: Out of Bounds : Avoiding Career Protection Faults
Excellent article. I forwarded a link to several of the old-timers around here, and it made a lot of them smile. What particularly piqued my interest was how newer developers often think that something is useless unless it is fully buzz-word compliant. It actually motivated me to blog about this topic on my own (usually fairly dormant) blog at http://www.jimako.com/blog/2006/02/08/an-interesting-article-on-legacy-code/(warning: it's quite a long post)
Re: Out of Bounds : Avoiding Career Protection Faults
True. First focus of any new joinee should be to walk with the team. Even if the person has come from background of having solved similar problems before; the circumstances are never same. So first learn what the common knowledge is and then see if everything that you want to advocate makes sense. And if it does, lead by example. It always works and if does not then you are in wrong organization.Re: Out of Bounds : Avoiding Career Protection Faults
Programmers who stayed in the same job for long belong to 2 categories. First category consists of programmers whose skills and abilities are very low so they have no chance of finding another job. Second are good developers who are compensated well and they have no reason looking for another job. Even in second category programmers get stagnated. Familiar, comfortable environment makes people lazy and they stop learning. So management likes to bring a new guy who will stir up the team. Old programmers hate new guy but management encourages and protects him. So it is an interesting and fun game to watch.