A Quote by Jessica Livingston

Finding a programmer to work with if you don't already know one will be a challenge. Merely judging if a programmer is exceptional vs. competent will be very hard if you are not one yourself. When you do find someone, work together informally for a while to test your compatibility.
Because of the nature of Moore's law, anything that an extremely clever graphics programmer can do at one point can be replicated by a merely competent programmer some number of years later.
You become a serious programmer by going through a stage where you are fully aware of the degree to which you know the specification, meaning both the explicit and the tacit specification of your language and of your problem. "Hey, it works most of the time" is the very antithesis of a serious programmer, and certain languages can only support code like that.
To be a programmer is to develop a carefully managed relationship with error. There's no getting around it. You either make your accomodations with failure, or the work will become intolerable.
To be a programmer is to develop a carefully managed relationship with error. There's no getting around it. You either make your accommodations with failure, or the work will become intolerable.
My advice for finding a literary agent would be first, put your work out there as much as possible and hopefully someone will find you, because I still have literary agents writing to me after they find my site. You want someone who understands your work and is going to be your cheerleader from day one.
Testing proves a programmer’s failure. Debugging is the programmer’s vindication.
It's a very complex network of genes making products which go into the nucleus and turn on other genes. And, in fact, you find a continuing network of processes going on in a very complex way by which genes are subject to these continual adjustments, as you might say - the computer programmer deciding which genes ultimately will work.
Before 'Dilbert,' I tried to become a computer programmer. In the early days of computing, I bought this big, heavy, portable computer for my house. I spent two years nights and weekends trying to write games that I thought I would sell. Turns out I'm not that good a programmer, so that was two years that didn't work out.
Your first problem is relying on someone else's word. Always depend on yourself. No one will work as hard for you as you will.
The programmer, who needs clarity, who must talk all day to a machine that demands declarations, hunkers down into a low-grade annoyance. It is here that the stereotype of the programmer, sitting in a dim room, growling from behind Coke cans, has its origins. The disorder of the desk, the floor; the yellow Post-It notes everywhere; the whiteboards covered with scrawl: all this is the outward manifestation of the messiness of human thought. The messiness cannot go into the program; it piles up around the programmer.
When you have an emotional reaction to what you see, you are judging. That is your signal that you have an issue inside of yourself - with yourself - not with the other person. If you react to evil, look inside yourself for the very thing that so agitates you, and you will find it. If it were not there, you will simply discern, act appropriately, and move on.
Don't blame me for the fact that competent programming, as I view it as an intellectual possibility, will be too difficult for the average programmer, you must not fall into the trap of rejecting a surgical technique because it is beyond the capabilities of the barber in his shop around the corner.
I'm not a programmer myself, but I am a very, very picky end user of technology. I like my machines to work they way they're supposed to, all the time.
You see, if you take pains and learn in order to get a reward, the work will seem hard; but when you work... if you love your work, you will find your reward in that.
It's easy to isolate yourself when you're buried in work, or to rely only on work friends for empathy. And while your work friends will always 'get it' more than your life partner, they don't know how to comfort you like your partner does.
The first is that good writing consists of mastering the fundamentals (vocabulary, grammar, the elements of style) and then filling the third level of your toolbox with the right instruments. The second is that while it is impossible to make a competent writer out of a bad writer, and while is equally impossible to make a great writer out of a good one, it is possible, with lots of hard work, dedication, and timely help, to make a good writer out of a merely competent one
This site uses cookies to ensure you get the best experience. More info...
Got it!