A Quote by Kevin Systrom

It's funny: I was a photographer before I was a programmer. — © Kevin Systrom
It's funny: I was a photographer before I was a programmer.
If a photographer cares about the people before the lens and is compassionate, much is given. It is the photographer, not the camera, that is the instrument.
Testing proves a programmer’s failure. Debugging is the programmer’s vindication.
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.
I've never not been sure that I was a photographer any more than you would not be sure you were yourself. I was a photographer, or wanting to be a photographer, or beginning - but some phase of photographer I've always been.
I became a photographer in order to be a war photographer, and a photographer involved in what I thought were critical social issues. From the very beginning this was my goal.
Well, I'm not going to get into that. I think that those kind of distinctions and lists of titles like "street photographer" are so stupid. I'm a photographer, a still photographer. That's it.
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.
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.
I was always introduced as the Beatles photographer and I gave it up in the end. I was so unsure of myself. Am I good or am I just the Beatles photographer? People were not interested in what I did before. I could not stand it any more.
Before coming to Congress, I worked as a computer programmer and a systems analyst.
We could talk, act, and dress funny. We were excused for socially inappropriate behavior: 'Oh, he's a programmer'. It was all because we knew this technology stuff that other people found completely mystifying.
A good programmer is someone who always looks both ways before crossing a one-way street.
When we take the position that it is not only the programmer's responsibility to produce a correct program but also to demonstrate its correctness in a convincing manner, then the above remarks have a profound influence on the programmer's activity: the object he has to produce must be usefully structured.
I think that's the responsibility of the CEO and the CEOs below me: to make sure that we're constantly putting people in places where they have the opportunity to develop into those careers but also having a rewards and recognition system that allows a great programmer to stay as a great programmer.
I'm not a great programmer; I'm just a good programmer with great habits.
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.
This site uses cookies to ensure you get the best experience. More info...
Got it!