Know what you're talking about.
In programming when you're making a change you have to know all the affected places, and you have to be able to model in your head what the performance impact will be.
In Europe, radio stations are owned by a variety of different entities, so there is less uniformity on radio programming and more opportunity for artists to get radio play and break overseas.
I'm seeing too many kids where they get fixated on their own autism. I'd rather have them get fixated that they like programming computers or they like art or they want to sing in the church choir or they want to train dogs, you know, something that they can turn into a career.
Instead of three networks you have three hundred or three thousand. Audiences are inundated with programming, and that sometimes gives them a sense of petulant entitlement.
If you've got a stick hitting a drum and you're programming it on a computer, it's so much more interesting than a sample playing back - it's something in the air, that's the magical ingredient.
I became this guy that does drum programming, and I don't want to be that guy anymore. I don't want to sit in front of my computer for 18 hours programming 16 bars of music.
I was not in a good space in my life, emotionally particularly, so I needed to do something to recharge my batteries emotionally and musically. I took a break and I learnt software and programming a little bit, and that's how I designed my live machine, which I've been using for years.
In software, we rarely have meaningful requirements. Even if we do, the only measure of success that matters is whether our solution solves the customer's shifting idea of what their problem is.
After you finish the first 90% of a project, you have to finish the other 90%.
Before Ruby on Rails, web programming required a lot of verbiage, steps and time. Now, web designers and software engineers can develop a website much faster and more simply, enabling them to be more productive and effective in their work.
If our designs are failing due to the constant rain of changing requirements, it is our designs that are at fault. We must somehow find a way to make our designs resilient to such changes and protect them from rotting.
We have to stop optimizing for programmers and start optimizing for users.
Opposites are not contradictory but complementary.
In the practical use of our intellect, forgetting is as important as remembering.
Always to see the general in the particular is the very foundation of genius.
Whenever there is a hard job to be done I assign it to a lazy man; he is sure to find an easy way of doing it.
Go isn't functional, it's pragmatical. Why pure paradigms like FP or OOP are always a must? (sigh)
Why would you have a language that is not theoretically exciting? Because it's very useful.
Go is such a refreshing language to program in, there is very little clutter just the stuff you need to get the job done
Go is most fun I've had with a compiled PL since I've discovered Turbo Pascal as a kid.
A user interface is well-designed when the program behaves exactly how the user thought it would.
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.
Convenient though it would be if it were true, Mozilla [Netscape 1.0] is not big because it's full of useless crap. Mozilla is big because your needs are big. Your needs are big because the Internet is big. There are lots of small, lean web browsers out there that, incidentally, do almost nothing useful. But being a shining jewel of perfection was not a goal when we wrote Mozilla.
Decisions in 10 minutes or less, or the next one is free.
Follow AzQuotes on Facebook, Twitter and Google+. Every day we present the best quotes! Improve yourself, find your inspiration, share with friends
or simply: