A Quote by Bill Budge

I write my programs primarily for myself. — © Bill Budge
I write my programs primarily for myself.
This is the Unix philosophy. Write programs that do one thing and do it well. Write programs to work together. Write programs that handle text streams, because that is a universal interface.
Much of my work has come from being lazy. I didn't like writing programs, and so, when I was working on the IBM 701 (an early computer), writing programs for computing missile trajectories, I started work on a programming system to make it easier to write programs.
Though The Kite Runner was my first completed novel, I had been writing on and off for most of my life, primarily short stories, and primarily for myself.
I think that like all writers - and if any writer disagrees with this, then he is not a writer - I write primarily for myself.
I think that like all writers - and if any writer disagrees with this, then he is not a writer - I write primarily for myself
Between rounds of speed chess I read enough of a programming manual to teach myself to write programs on the school's DEC mainframe in the language Basic.
I can't write anything for myself. I can write when I hear like [John] Coltrane play something; I used to write chords and stuff for him to play in one bar. I can write for other people, but I don't never write for myself.
To me, an intellectual is a person who is primarily interested in ideas. What I am is an aesthete, a person who is primarily interested in beauty. That's why I write about art.
I started out as a poet who primarily wanted to write about image and moment. Over the years I've been trying to teach myself how to do plot and scene. My first story collection had the most issues with the plotlessness, and when I was writing my second collection I was teaching myself how to make things happen.
The best way to prepare [to be a programmer] is to write programs, and to study great programs that other people have written. In my case, I went to the garbage cans at the Computer Science Center and I fished out listings of their operating systems.
But some people will say you just did these programs. Well, yes, the programs are important and I'm proud of the programs, but mostly I'm proud of the way the San Francisco Symphony plays these programs.
My earliest interest in game design came when I was in primary school, and my parents bought a Commodore 128 computer. I taught myself to write programs in BASIC, and then I made my own games.
There is a marvelous peace in not publishing. It's peaceful. Still. Publishing is a terrible invasion of my privacy. I like to write. I live to write. But I write just for myself and my own pleasure. I don't necessarily intend to publish posthumously, but I do like to write for myself. I pay for this kind of attitude. I'm known as a strange, aloof kind of man. But all I'm doing is trying to protect myself and my work.
When you write a program, think of it primarily as a work of literature. You're trying to write something that human beings are going to read. Don't think of it primarily as something a computer is going to follow. The more effective you are at making your program readable, the more effective it's going to be: You'll understand it today, you'll understand it next week, and your successors who are going to maintain and modify it will understand it.
When I make music, I play it, I produce it, I write it. It's a very self-centered thing, not in a negative way. But I primarily work by myself, that's my process. When I'm acting, I'm there to serve the director and the character. I'm here to give you what you need. Communicate that to me and I will do what I need to do to get that. So that's what it's about.
I've always thought of myself primarily as an artist; it's what I most define myself as. The acting was all an accident.
This site uses cookies to ensure you get the best experience. More info...
Got it!