However, that is not the case at all with digital copying, where the original owner of the data is not deprived of anything. That is the real point - the idea of property is inextricably related to scarcity, which doesn't exist in the digital realm.
666 karma · joined August 11, 2009
However, that is not the case at all with digital copying, where the original owner of the data is not deprived of anything. That is the real point - the idea of property is inextricably related to scarcity, which doesn't exist in the digital realm.
He was only using the closet, because MIT was trying to singlehandedly change the terms of access to to the database to prevent the hoovering up of the info.
It's like getting arrested at a lunch buffet for eating too fast, or too much.
"I want to set param to the object property or the default" is much clearer than "I want to check if if I have an object property and if I do then I'll set the param to the object property otherwise I'll set the param to the default"
That is just mixing in a lot of noise about how you do it instead of just what you are doing.
My major was architecture, and the design classes gave me a sense of organization and elegant problem solving that are useful even as I build web apps for a living.
My drafting classes were useless - thank god I taught my self to use a pirated copy of AutoCAD at the time.
My classes in concrete and steel used large books of tables to look things up, which I am pretty sure can be easily handled by computers nowadays.
Data Structures and Algorithms would be the only thing from a traditional comp sci program I would have benefited from, I think, but I've done quite a bit of self directed learning in those areas, and am not worse off for it.
If I had it to do over again, I would've skipped school and tried to apprentice myself to people working on cool things instead. But I love to educate myself, and learn wherever I am. Some people are better off being guided, and those at upper-tier schools will benefit 90% from the connection they make, and 10% from the classes.
(Actually, I prefer Chris Rock's idea for bullet control. Make it too expensive to buy enough for mass shootings.)
By the same token, it's harder to kill a dozen people with a knife, if that's all you have to work with.
I think this article makes a much more convincing argument about what is going on than the one in the post: http://markcrispinmiller.com/2011/02/eight-big-problems-with...
I might not account for the cat tripping over my network cable.
I might not account for a server unexpectedly crashing.
I might not account for the office being too noisy to think in on Tuesday.
I might not account for Amazon having EC2 issues
I might not account for a DDoS attack on my DNS provider.
All of those things impact the time it would take, and the only way to fully account for everything that could happen would be to actually complete the project. Of course, if the project was identical to one I've done before, I could get a lot closer to an accurate estimate, with fewer real unknowns, but in 20 years of software, I've never had to create an identical solution. Because if it was an identical problem, I'd just use the previously developed software.
So the time to make the estimate would be 100% of the project time, and the estimate would be 100% accurate, since all the work would be done.
That is reductio ad absurdum, but the underlying problem is, as Donald Rumsfeld would say, there are "unknown unknowns" which cannot be accounted for ahead of time.
In a perfect world, estimates would come before deciding to proceed, but in 95% of the places I've ever worked, the project necessity is decided first and the estimates are asked for afterwards.
In reality, the project often settles for a shoddy subset of the original vision in order to make an arbitrary date, when they could have had the same exact subset at much higher quality if they had merely proceeded with the important parts first in a lean/agile manner, using micro-estimates (if bothering to estimate at all).
A bigger problem with estimating the solution of unknown problems is that confidence in the estimate varies inversely with the precision (or usefulness) of the estimate. I could estimate all my projects with 99% confidence as "somewhere between 1 day and 1 year".
That's not a useful estimate.
Or I could estimate "this will take 42 days" and be wrong 99% of the time.
The manager gets credit for success, and the developers get the blame for failure.
If the software has to be out the door by a specific date or the company dies - you DON'T NEED AN ESTIMATE.
Are you going to cancel the project based on the estimate? Dead Company
If the project is really too big to complete in time: Dead company, and optimistic estimates won't help.
If you could build a subset of the project and survive, then you still don't need an estimate - you just do the important stuff first.
If you were being chased by a lion, would an estimate of the time necessary to outrun it be of any use whatsoever? Of course not. You start running, and you either make it or you don't.
If there is other stuff happening in parallel, like marketing, then it is happening in parallel, and has no dependency on the software. That's what parallel means.
If you have a critical path dependency, then you're back to the situation above where you are going to make it or not, and the estimate won't really affect your ability to deliver.
Even estimating for cost is bullshit - if you practice lean development, you watch your metrics and if something doesn't work, just scrap it for the minimum amount of money lost. You can't do much better than that, except for not starting, and in that case you don't need an estimate.
I prefer the approach that saya "we're going to deliver feature X, and if it takes longer than Y or costs more than Z, we abort." You know exactly how much you stand to lose under this plan. The problem is, this means that management has to be involved on a day-to-day level with monitoring progress and making go/no-go decisions, when most managers I've met would prefer to have a single 3 hour planning meeting and then disappear for 4 months to raise money or play golf or go to tradeshows in Vegas or whatever.
Ah, youth.
Ruby / Rails / Heroku
code: https://github.com/mattvanhorn
blog: http://mattvanhorn.com
18 years web experience, 6 with Rails
Would like to try an Agile/BDD, pay-by-the-story (not hour) approach. This might work better for very early-stage startups.
twitter: @nycplayer
him: http://mattvh.com
Also, I did not see the presentation, so I can't comment on it firsthand, but as portrayed it looks to be in pretty bad taste. I don't know Matt that well, mostly through social media, but I can say that he's never come across as a knuckle-dragging misogynist. So ridiculing the presentation is fair, but trying to make him the face of the problem that is very widespread in the industry seems a bit unfair. (Not to mention this is all going to come up in Google searches for me, a programmer (not brogrammer) who lives and works in the bay area as well. /selfinterest )