Catch up on stories from the past week (and beyond) at the Slashdot story archive

 



Forgot your password?
typodupeerror
×

Comment Don't sabotage your opportunity! (Score 4, Insightful) 276

If the project has momentum then the absolute worst thing that you can do is resist adding additional people to the project. If you do not understand how additional people can increase project velocity and add value then you are not experienced enough to make that decision and it will show to all of management. What you need to do is be strategic about how the team grows.

First you need to think deeply about what you do not know. What are the organizational hurdles you are likely to face? At what stages of the project will you be over-allocated as a resource? How many presentations and one-on-one conversation will be necessary keep momentum? How will this project be monetized? How will the end product integrated into an existing offering? Or how will the end product be marketed and sold?

Once you have a good inventory of what you will need, sit down with management and talk about how to address these needs--this alone will earn you a lot of respect. Ask who will likely be assigned to the project. Start taking these people out to lunch to discuss the project. If they are more senior they will generally offer to pay. Don't hesitate to pay even if out of your own pocket. It will show how committed you are to the project and organization. During these lunches ask questions about the process other successful projects have gone through and the types of problems your project is likely to face. NOTE, it is critical to not be defensive or offer too many pre-baked solutions during these meetings--it will come of arrogant, dismissive and impulsive. It is much better to say things such as, "I have some thoughts around this, but need to vet the ideas with people who can really help shape them." You will have opportunities to solve the problem in due time, or even better to have other people "solve the problems" with your solutions.

Ask if you can be a part of the decision making process for attaching additional people to the project. If you are included, be very judicious using any perceived veto power. It is better to raise concerns and shape involvement than to try to establish a front. Of course, there are always cases where lines should be drawn, but if you have voiced realistic concerns then you can keep management up to date if you seen things going awry. If you are not included, accept that decision maturely and remain engage in the process. You will likely have more influence on the side lines than you realize.

As the project grows you will need to find an exit from your technical role. You will need to own the vision, but you will not have time to execute all the technical details. Mentor people to take over the details and build as many documented repeatable processes as possible.

Learn how to present your ideas. You will likely be invited to more presentations. Know your place in these presentations. You have more to lose than gain if you say too much. Be there as the "guru with upside" instead of being the "one-hit wonder" or the "wild card."

Good luck! I hope you do well. Don't be afraid of not knowing something. Nobody knows everything. Embrace other people's capabilities especially when you don't understand what they do or who they can help. These are generally the people you really need.

Comment Re:Inconsistantly Odd Alert (Score 1) 151

File this one under uninteresting and an obvious forgery.

Technically this is not much different than just hosting a look-alike page to collect passwords. The phishing attack would be much more interesting if the URL wasn't so obviously bogus. According to the paper an attack could use a URL shortener to further hid the obviously odd URI. The problem with this is that the URI attack described in the article requires that you send the URI with payload to the victim. A URL shortener service has no reasonable way to direct the short URL to the crafted URI.

Ironically, using a shortened URL (tinyurl, bit.ly goo.gl etc) would make it easy to hide a real phishing site hosted out on the Internet. To say that this is a security hole is to say that because all browsers allow people to go to sites that can claim to be who they are not all browsers are insecure.

Comment Re:Drug test the final standard? (Score 2) 482

It should also be pointed out that cyclists are typically not very wealthy. The longer this goes on the more people close to Armstrong will be dragged into an unaffordable and life wrecking ordeal. It is one thing to say that Lance can afford to pay for his defense. However, it would be inappropriate for him to fund the defense of other. It is a really bad situation all the way around.

Comment Re:Willing to bet.. (Score 1) 1706

Exactly, the individual who happened to fire that particular bullet. While the initiator is to blame for the situation each individual holds their own responsibility for how they respond. Think of it this way, if a gunman entered a crowded room and shot some people, would it be acceptable to take him out with a grenade?

This is not such a black and white issue. If people who are not properly trained respond in a reckless manner then they are responsible. There is a line somewhere between do nothing and everybody should be armed.

As an aside, I think that the do nothing crowed is just as loney and the guns for everybody crowed.

Comment Re:advantages of multiple inheritance (Score 1) 209

Actually, more than 50% of programmers are below average. There is always a large number of beginning programmers compared to the few exceptional programers in the long tail of the population. Long tail populations almost always have an average on the long tail side of the median. In this sense I think that it would even be fair to say that the overwhelming majority of programmers are below average. This is in line with my experiencing with programmers.

Slashdot Top Deals

I've noticed several design suggestions in your code.

Working...