941 karma · joined February 7, 2008
[ my public key: https://keybase.io/bencollins; my proof: https://keybase.io/bencollins/sigs/hGAUM3Q3RKADa9EOm1RLFk7arseXNo5EiDH6U1f9qzE ]
The real price of contracting isn't the loss of benefits, but the increased burden of providing those things for yourself (if they were that important to you in the first place). The real reward is: freedom. You can provide any/all/none of those things for yourself as you see fit.
All presuming you have work, of course ;-)
This to me is like arguing that object-oriented programming isn't really any better than procedural programming because I know how to write well-structured procedural programs. This is completely beside the point, which is that procedural programming as a style tends toward balls-of-mud programs (to simplify things), and object-oriented techniques were conceived of in order to address the characteristics of procedural programming that are the cause of this tendency.
I view RESTful API programming in a similar vein: RPC also has negative tendencies (such as the creation of fragile protocols), and REST addresses many, if not all of those. Most of the time for more people, RESTful techniques will lead to better service and API design than will RPC, just like for most of the people most of the time, object-oriented programming will lead to better programs than will procedural programming.
I don't have an inherent problem with coworkers asking each other out on dates, or within a professional context in general, but doing it in an interview is beyond stupid.
My recollection was that OpenBSD code was actually quite polished, and even elegant in lots of places. They also produced what I think were easily the best and most complete manpages out there. It was actually enjoyable to read both the code and manpages, and pretty easy to understand (assuming proficiency in C and basic machine architecture, of course).
What was not enjoyable, for me, was the constant hostility on the mailing list and frequent lashing out at others in various OSS communities (...as demonstrated in the OP). I know there there were others for whom that played no small part in their loss of interest in the project.
I also think being distributed encourages small chunks of work, where being centralized encourages the batcave approach, and that, I think, is a much bigger differentiator than most people realize. It impacts everything. Suddenly, merging doesn't seem as bad, and then suddenly being able to easily and cheaply create branches is more important. Centralized systems never really got there because the client/server nature works against them. I'm glad to see some big players giving them attention again, because one of the author's best points is that being centralized has certain advantages. It's just that the existing centralized systems suck.
I also think the GitHub workflow comparison to the email list + patch days is a bit contrived because the email list procedure was never that simple (well, for getting ignored maybe it was, but the point was to contribute, not be ignored). I, too, remember those days.
Steps 1&2 under GitHub aren't really harder than step 1 under CVS (or what have you). He just neglected to mention all the steps involving fiddling with CVS connection parameters, or finding the right URL for a SVN repository (trunk? All the branches? Do I care about tags? Good luck if they aren't using the standard layout).
Github #3 also belongs in the first list. Goodness...have you ever read the OpenBSD mailing list? It's about as friendly as EFnet on PMS.
I could go on, but the point is that the number of steps for CVS+mailing list isn't really different than with GitHub.
I think in contemporary usage, "freeway" and "highway" mostly mean the same thing: no stops.
I would add that Lessig is spectacularly self-unaware as he goes about raising money for his cause. I have no idea how I got subscribed to the Rootstrikers mailing list, but I stay subscribed for the occasional lulz.
I think your biggest problem here is your expectation of how much good skilled work is going to cost you.
If all you need is to find people, then try local meetups: Android or iOS meetups are going to be happening in almost any major metro area. Look for non-technical meetups, too. In Dallas there's at least one startup happy hour each month, and I'd be shocked if LA didn't have something like that. One good source for this is meetup.com, but also...Google.
Once you find people, though, you need to be prepared to offer appropriate compensation. If you don't have cash, then you might need to offer equity (or a slice of whatever revenues you make) along with some cash. Almost nobody is going to do anything for you without at least some cash, though.
And hey: NuGet is open-source.
If you don't like real estate, then pick something else: save a bit longer and buy a pizza franchise. Save for a few centuries and buy a football franchise. Buy some other kind of small business. Learn an investment strategy that makes you a few percentage points annually.
> Is there a way to get a ...decent salary...doing very little from 9-5?
This is generally called passive income, and you don't get this on someone else's payroll. You have to get there on your own.
heh. it may actually be worse, because being remote adds a new dynamic to all the politics.
Good luck.
I understood the point, which I would summarize thusly:
We can't have a law enforcement regime of prohibition against "drugs" because who can say what a "drug" is, anyway?
Was the article well researched and well-written? I don't deny it and don't need to. This, to me, is unbelievably stupid and utterly unconvincing to anyone who supports the current approach to prohibition. Call me a nitwit all you want, but this argument is exactly the wrong one to end the drug war.
Somebody was working a little too hard to have a clever headline.
I'm all for ending the drug war as we know it, but I don't find this kind of thing helpful. Is a very technical way, he's right: the overall picture of what drugs are and what they do and why some are judged "bad" and others not is a nuanced, historically literate view. And almost completely irrelevant.
Being high on meth is a completely different phenomenon than being stimulated into wakefulness. The former can cause people to do really stupid and dangerous things, not to mention the physical destruction it wreaks on the human body. The two are really incomparable in practice. IMO, policy arguments out to focus on the ill effects of the "drug war" itself, not the technical equivalencies between drugs to which most people will not assent (including me).
Consider: if you devoted yourself to reading and working on open-source projects or even some contracting, going to workshops/codeathons, local user groups, and etc., you could built up some expertise and even a pretty decent portfolio of work within a few short years. Give it even just 2-3 years of being disciplined with it, and you could very possibly have more to show for it than some who have been coasting in the industry for far longer. After 3 years, you would be only 31, and you could have a programming career for 20-30 years, if you so desired.
Bottom line: you can do it. But you gotta be ready to work hard and jump into things.
This is not at all like programmers working on side projects. The equivalent thing for a programmer would be to run off with the source code you wrote for your employer and take it to another employer, which is an obvious no-no. The grey area for side projects is defined by how much your employer thinks it might be competing (or directly related to) your paid work. Some employers explicitly don't care, while others do. You need to consult your employment agreement first and the state law where you live second. If it's not clear after that, consult a lawyer. FYI: this is a good thing to do before taking a job.