edabobojr

You might want to do fewer, less frequent releases in order to provide training to end users. You might also want to do do fewer, less frequent releases in order to facilitate a marketing push centered around the release.

"Non-owner" was a poor choice of terms. I was thinking more in terms of the little guys who have at most a 1-2% ownership stake in the company.

How does this work from an employee point of view? Are they compensated in the buyout? Do they get to do any negotiation with their new employer? The cynic in me thinks this could easily be a raw deal for non-owners.

Which makes you wonder if they restaurateurs are writing just as many articles complaining about all of the cooks running around looking for someone to build and run a restaurant for them.

There can also be accounting considerations. Sometimes contractors are the first to go, other times they are last. Carrying a contractor frequently looks much cheaper than carrying an employee.

You're using the wrong frame of reference here. The first test referenced here is the first test run by a separate qa team.

Black on light gray. I've notices as I've gotten older that a white background just gives me headaches.

The java version spends 75% of it's time gc? That smells fishy to me.

edit: I just got to section VI of the paper, which does some gc tuning. In my playing, I also found about a 20% speedup by changing the HavlakLoopFinder.UnionFindMode class to being a statuc class.

It's been a long time, but I believe Ada provides the ability for the first 4 and I would bet you could define the last two in it.

Would you care to expand on your experiences with this? I keep hearing of people who take this approach, but I've always been skeptical on how well it really works out.

Assume that I have a job. What you would be offering me would be an opportunity to quit my job in return for a temporary job that might or might not convert to full time. During the transition, I will lose my benefits. Your assumption of a pay bump when going permanent also seems to indicate that I wouldn't be compensated for the risk of a permanent position not being offered.

What do you see as the value proposition for an already-employed person in this arrangement?

If you are ever exercising your options; get out the crowbar, pry open your wallet, and go find an accountant to explain all of your tax options and the risks involved in them.

If you exercise your options, I believe you generate a taxable event. If you do not sell the stock for twelve months (as advocated in the article), you risk the stock price dropping below your strike price and you might not have enough money left to pay your tax bill. I recall reading a sob story (Money magazine?) about a guy going bankrupt because of this but I haven't been able to find it.

As the age-old saying goes, "A poor workman always blames his tools." Where is the accountability? I would be much more interested in hearing some retrospect on what they did wrong.

When evaluating your coworker's abilities, do you judge their ability to perform CRUD and tedious bug fixes or their knowledge of abstract concepts, hard computer science, and cutting-edge math?

How many hours a week are the employees expected to put in versus the number of hours you were billing? I've been places where the employees were abused and the contractors were expected to work not a minute more than 8 hours per day.

Whenever people talk about git, they seem to talk about how you can have all of these working copies locally. My concern is the frequency with which code would be published to the centralized server and possible loss if all of the working copies were to disappear.

Admittedly, this is a bigger problem in svn if you aren't using branches for work-in-progress.

Or you could talk to Joe down the hall. He has the 'gold' version of the source code on his desktop. Don't forget to send him your changes when you are done and he will integrate it to the current 'gold' version.

The big risk I always see with git is that you start storing more and more work locally. This exposes you to the chance of hardware failure on a desktop pc. With svn, it would be easier for the hardware to be redundant and backed-up.