Is this somewhat similar to Soasta Mpulse RUM?
The way you inject the code to start sending data points is similar. With them i have to specify what i want to track though, using tags. It won't allow me to track all ajax calls.
Would be great to include the opinion and feedback from your coworkers who actually go to the office. This seems like good feedback for people who maybe does not feel comfortable with their home setup and a few practices. But I still feel the team's productivity is certainly increased if the team is working together.
So, if a person wants to start a company, how can he make sure it's not breaking any patent that could cost him money and a legal mess later?, I suppose a few hours of investigation previous starting up is not enough...
This is in my opinion the biggest problem with the patent system. The bars for obviousness and novelty are too low if startups need to start worrying about whether they're accidentally coming up with the same designs as existing companies. Provable independent invention needs to be a defense to patent infringement.
The current dance around the broken patent system look something like this :
- When you are small, nobody will come to get you because you are not interesting enough for troll of big compagnies (except maybe other direct competitor but it's unlikely)
- Then you become bigger and you will have to deal with licenses from other compagnies and trolls.
- At that point you become defensive, and start to patent things yourself.
- Then you are unwilling to fight against patents because it starts to be an asset for you. And you might even be tempted to go to the dark side and use them to attack other companies at this point.
The good news in all that is that when you are a small company in software, you should not worry too much about patent. I don't remember any startup failing because of that...
Absolutely not. First, I have heard anecdotes about patents for (device and method for) transferring data over a network. Second, if you know about a patent you are now wilfully infringing and will get triple damages in court.
But don't worry, the patent trolls only want income, so they'll demand you license their patent at a price carefully calculated to be your revenue minus your costs.
I understand it to generally be simply not possible. Any product is going to be infringing on dozens of patents held by any of the big companies in the field.
That's all true but code reviews certainly share a lot of information and feedback specifically related to the context of the day by day development. Which certainly will increase your productivity by teaching you about mistakes and at the same time letting you evangelize someone else in your team/organization. You won't find the same amount of information for your project with as much frequency as you do on code reviews.
"Improve it later because it's painless to do so?" I don't think so. Quick and dirty approach and then fix it later is just the start of future issues, broken designs, infinite refactoring.
I feel java helps a bit more on design scalability. Yes, maybe somewhat overegineered but it certainly does not hurt to think on the future
After checking out the bunch of complaints, I wonder what's going on with Apple's quality process. They must had seen some of this 'roller coaster street' bugs before...
They either sacrificed quality for getting the product out soon... Or maybe they are assuming most of fans won't care about the bugs just because they'll get the new phone anyway... Or their quality process just needs some improvements.
"We dig in the dirt so that out of the muck we can construct something we ourselves can find worthwhile, all the time knowing in our true hearts that we’re likely to be the only ones to ever find it beautiful" ... That's one of the reasons why being a maker is sexy. Plenty of startups have probably started this way...out of the muck, against all odds, against disbelief from the rest of the world, you can take something and make it work. Makers are pursued by a lot of companies. That's sexy...
I would find this method useful for some types of college projects when students can spend a few days researching but the conclusions are short(short does not necessary mean poor). I've seen plenty of papers that when you finish reading them you certainly think the author could have written the same in just a couple of sentences. Interesting tool for focusing on a fact and a result.
We started doing Scrum around a year ago and it has worked well for us. I feel some of the points described in the article about Scrum are not because of the framework itself but because there could have been a lack of a Scrum Master, which is an important piece in the puzzle, to ensure Scrum effectiveness.
