Quotes About Software

Using the Internet to secure employment is as vital to a construction worker as it is to a software engineer.

Automation is no longer just a problem for those working in manufacturing. Physical labor was replaced by robots; mental labor is going to be replaced by AI and software.

There's a common personality type to software developers - one I certainly fall into. We're more comfortable staring at a screen than staring into someone's eyes. Engineers can be brilliant in the workplace, and something less-than-brilliant everywhere else.

In many cases, the user interface to a program is the most important part for a commercial company: whether the programs works correctly or not seems to be secondary.

I worked in a software company in Bangalore and made short films during weekends. I learnt the basics during a one-day workshop called Film Camp Sanjay Nambiar.

We're entering a new world in which data may be more important than software.

To make an embarrassing admission, I like video games. That's what got me into software engineering when I was a kid. I wanted to make money so I could buy a better computer to play better video games - nothing like saving the world.

Software drives hardware in this business. We see it time and time again. We saw it with our Wii and DS businesses.

It's important not only to have the right timing of when the hardware is going to be released but also when we are going to be able to introduce quality software.

Software is now so complex - requiring so many gazillions of tiny files all over your computer - that most consumers don't want to bother to know what's really going on.

I took this 'how to build computers' course basically because I'm sick and tired of getting ripped off by cheesy computer companies. Software baffles me. I like hardware. I used to change my own oil, and now I want to build my own computer so I can have what I want.

If we reduce the number of employees for better short-term financial results, employee morale will decrease. I sincerely doubt employees who fear that they may be laid off will be able to develop software titles that could impress people around the world.

Games take years to make, and it's important that when we launch, it can't just be a great launch catalog and then a desert for a really long time. To be honest, for a lot of developers, they'd rather not be competing at launch with all this other software.

Apple is the only company that can take hardware, software, and services and integrate those into an experience that's an 'aha' for the customer. You can take that and apply to markets that we're not in today.

The most sought-after candidates in the world today by companies like mine are people who make computer software - there's a shortage of talent.

Software tends not to kill people, and so we accept incredibly fast innovation loops because the consequences are tolerable and the results are astonishing.

Dont write perfect code, write code that works

the only reason anything good ships is because of the programmers. They are everything. They are not factory employees; they are craftspeople, craftspeople who are the fundamental creative engine of making software.

But the problem isn't functionality. Functionality means a piece of software is capable of doing something. Merely having a function doesn't say anything about how many people can figure it out or are even interested in trying.

While most software is copyrighted and closed, Cafelog had different rules. It did not have a copyright. Instead it had something called an open source license, or a copyleft.

I'd used open source software before when studying computer science in college, including countless caffeinated hours writing code in EMACS, a brilliant editing program made by Richard Stallman (who coined the term copyleft). I used other tools that were open, or free, or in the public domain, but that was rarely the reason I chose them.

At the heart of the debate over how to overcome the challenges of shipping good things is an idea referenced in the title of Eric Raymond's book The Cathedral and the Bazaar.1 The book, which is about observations on making software, raises a central question that is relevant to all work: Is it better to invest time in making a big masterful plan or instead to start immediately and figure it out as you go?

People write programs. That statement is worth pausing over. People write programs. Despite the field's infatuation with metaphors like architecture and bridge-building and its dabbling in alternative models from biology or physics, the act of programming today remains an act of writing—of typing character after character, word after word, line after line.

countries allow organizations to claim some aspects of software development as R&D and thereby receive tax benefits for doing so.