Quotes of All Topics . Occasions . Authors
I'd like to point out that I don't think that there is anything fundamentally superior in the GPL as compared to the BSD license, for example. But the GPL is what I want to program with, because unlike the BSD license it guarantees that anybody who works on the project in the future will also contribute their changes back to the community.
We didn't see any statistically significant relationship between our buzz and our short-term sales...Is that the end of the story? I would say no. This is one study on a set of brands in a particular company within a certain segment of the consumer-packag ed-goods industry. It is by no means a generalized result that applies to all industries.
So the HP guy comes up to me (at the Melbourne conference) and he says, 'If you say nasty things like that to vendors you're not going to get anything'. I said, 'No, in eight years of saying nothing, we've got nothing, and I'm going to start saying nasty things, in the hope that some of these vendors will start giving me money so I'll shut up'.
You can understand Tunisia revolution as a failure to censor the internet. And Libya had that failure too. It's very difficult for governments that are autocratic and don't have broad popular support to be in power when a lot of people have these devices. That was what Arab Spring was about, that people could express this and lead to revolution.
I seldom get self-righteous, and even when I am being impolite (almost always on purpose - there's an art to insulting people, too), I tend to try to not be too serious about it. And most of the time it means that I can take criticism constructively, and sometimes just change my opinion on the fly and laugh at myself over having turned on a dime.
All programmers are optimists. Perhaps this modern sorcery especially attracts those who believe in happy endings and fairy godmothers. Perhaps the hundreds of nitty frustrations drive away all but those who habitually focus on the end goal. Perhaps it is merely that computers are young, programmers are younger, and the young are always optimists.
Linux has more than satisfied any small initial expectations I had. It's simply incredible how successful Linux has been, and how good a time I've had developing it and leading the project. It does take a lot of my time, but it's time I really enjoy spending, and Linux has continued to be challenging both technically and from a managing standpoint.
The underlying issue is the system of capitalism itself, and under this system the best means for regulating or checking their power is not relying on a government which represents the interests of the rich but for millions of working people to become politically active in workplaces and communities through building unions and our own political party.
There's a few historical reasons for why git was considered complicated. One of them is that it was complicated. The people who started using git very early on in order to work on the kernel really had to learn a very rough set of scripts to make everything work. All the effort had been on making the core technology work and very little on making it easy or obvious.
I think it is astounding that people could argue for "you just must trust someone else to fix it" instead of "you could fix it yourself, or hire someone to fix it." There is a contractor base out there that can solve these problems as well as or better than the major vendors could. But I think the major vendors are still having more luck at getting the ear of the press.
Observe that for the programmer, as for the chef, the urgency of the patron may govern the scheduled completion of the task, but it cannot govern the actual completion. An omelette, promised in two minutes, may appear to be progressing nicely. But when it has not set in two minutes, the customer has two choices - wait or eat it raw. Software customers have had the same choices.
One other specific piece of guidance we've offered is that low-quality content on some parts of a website can impact the whole site’s rankings, and thus removing low quality pages, merging or improving the content of individual shallow pages into more useful pages, or moving low quality pages to a different domain could eventually help the rankings of your higher-quality content.
I'm not a big believer in revolutions. What people call revolutions in technology were more of a shift in perception - from big machines to PC's (the technology just evolved, fairly slowly at that), and from PC's to the internet. The next "revolution" is going to be the same thing - not about the technology itself being revolutionary, but a shift in how you look at it and how you use it.
We weren’t trying to strike it rich with Firefox. It’s open source and it’s free. We weren’t trying to take over the world; we had kind of modest goals, and it was OK if it failed. We were a lot freer to make risky decisions. If you can afford to do things that way, it’s just so much better. You’re not thinking about venture capitalists or marketing or sales. Just product and users, all day every day.
The first step toward the management of disease was replacement of demon theories and humours theories by the germ theory. That very step, the beginning of hope, in itself dashed all hopes of magical solutions. It told workers that progress would be made stepwise, at great effort, and that a persistent, unremitting care would have to be paid to a discipline of cleanliness. So it is with software engineering today.
The hardest single part of building a software system is deciding precisely what to build the most important function that software builders do for their clients is the iterative extraction and refinement of the product requirements. For the truth is, the clients do not know what they want. They usually do not know what questions must be answered, and they have almost never thought of the problem in the detail that must be specified.
One can expect the human race to continue attempting systems just within or just beyond our reach; and software systems are perhaps the most intricate and complex of man's handiworks. The management of this complex craft will demand our best use of new languages and systems, our best adaptation of proven engineering management methods, liberal doses of common sense, and a God-given humility to recognize our fallibility and limitations.
The critical thing about the design process is to identify your scarcest resource. Despite what you may think, that very often is not money. For example, in a NASA moon shot, money is abundant but lightness is scarce; every ounce of weight requires tons of material below. On the design of a beach vacation home, the limitation may be your ocean-front footage. You have to make sure your whole team understands what scarce resource you're optimizing.
Code wants to be simple... I had to give up the idea that I had the perfect vision of the system to which the system had to conform. Instead, I had to accept that I was only the vehicle for the system expressing its own desire for simplicity. My vision could shape initial direction, and my attention to the desires of the code could affect how quickly and how well the system found its desired shape, but the system is riding me much more than I am riding the system.
Continuous Integration is a software development practice where members of a team integrate their work frequently, usually each person integrates at least daily - leading to multiple integrations per day. Each integration is verified by an automated build (including test) to detect integration errors as quickly as possible. Many teams find that this approach leads to significantly reduced integration problems and allows a team to develop cohesive software more rapidly.
There is a myth that the New Deal programs on their own pulled the US out of the Great Depression and created the conditions for the economic boom after World War II. As an economist, I can tell you, that is not true. In reality, it was mainly World War II that launched the boom - the massive war mobilization, the horrifying destruction and death caused by it, and then the reconstruction in its aftermath. he US was the only advanced capitalist country that was not bombed during the war.
In science, the whole system builds on people looking at other people's results and building on top of them. In witchcraft, somebody had a small secret and guarded it - but never allowed others to really understand it and build on it. Traditional software is like witchcraft. In history, witchcraft just died out. The same will happen in software. When problems get serious enough, you can't have one person or one company guarding their secrets. You have to have everybody share in the knowledge.
UNIX has a philosophy, it has 25 years of history behind it, and most importantly, it has a clean core. It strives for something - some kind of beauty. And that's really what struck me as a programmer. Operating systems that normal home users are used to, such as DOS and Windows, didn't have any way of life. Nobody tried to design Windows - it just grew in random directions without any kind of thought behind it. [...] I don't think Microsoft is evil in itself; I just think that they make really crappy operating systems.
A permanent and sustainable solution to all the problems facing working people is possible by taking the biggest companies into democratic ownership, and reorganizing the economy on a democratically planned basis. Under such a system we could democratically decide how to allocate resources. We could rapidly transition away from fossil fuels, develop massive jobs programs to rebuild the country's rotting infrastructure, and begin to build a whole new world based on meeting the needs of the majority, not the profits of a few.
My first operating system project was to build a real-time system called RSX-11M that ran on Digital's PDP-11 16-bit series of minicomputers. ... a multitasking operating system that would run in 32 KB of memory with a hierarchical file system, application swapping, real-time scheduling, and a set of development utilities. The operating system and utilities were to run on the entire line of PDP-11 platforms, from the very small systems up through the PDP-11/70 which had memory-mapping hardware and supported up to 4 MB of memory.
Bernie Sanders talks about socialism in Scandinavia, and he's correct to point to the huge victories the working class has won there through struggle, such as socialized medicine, free college education, and paid family leave. But if you talk to working people in Sweden or Norway today, you will find out that many of those past gains have been eroded and some virtually eliminated, including massive under-funding of healthcare and other public services and a return to for-profit systems that are unaffordable to working class people.
Find a way to say yes to things. Say yes to invitations to a new country, say yes to meet new friends, say yes to learning a new language, picking up a new sport. Yes is how you get your first job, and your next job, and your spouse, and even your kids. Even if it's a bit edgy, a bit out of your comfort zone, saying yes means that you will do something new, meet someone new, and make a difference in your life. Yes lets you stand out in a crowd, be the optimist, to stay positive, be the one everyone comes to. Yes is what keeps us all young.
The magic of myth and legend has come true in our time. One types the correct incantation on a keyboard, and a display screen comes to life, showing things that never were nor could be.... The computer resembles the magic of legend in this respect, too. If one character, one pause, of the incantation is not strictly in proper form, the magic doesn't work. Human beings are not accustomed to being perfect, and few areas of human activity demand it. Adjusting to the requirement for perfection is, I think, the most difficult part of learning to program.
The Linux kernel is under the GPL version 2. Not anything else. Some individual files are licensable under v3, but not the kernel in general. And quite frankly, I don't see that changing. I think it's insane to require people to make their private signing keys available, for example. I wouldn't do it. So I don't think the GPL v3 conversion is going to happen for the kernel, since I personally don't want to convert any of my code. You think v2 or later is the default. It's not. The _default_ is to not allow conversion. Conversion isn't going to happen.
Well over half of the time you spend working on a project (on the order of 70 percent) is spent thinking, and no tool, no matter how advanced, can think for you. Consequently, even if a tool did everything except the thinking for you - if it wrote 100 percent of the code, wrote 100 percent of the documentation, did 100 percent of the testing, burned the CD-ROMs, put them in boxes, and mailed them to your customers - the best you could hope for would be a 30 percent improvement in productivity. In order to do better than that, you have to change the way you think.