Quotes About Developers

reuse is easiest within a project instead of between them. A manager's success depends on performance on a given project and not on performance over several projects. And preparing code for reuse requires additional work, not only by the reuse expert but also by developers. Therefore, preparing for reuse has a cost for any given project.

People often say that videogames made by Western developers are somehow different in terms of taste for the players, in comparison with Japanese games. I think that means that the Western developers and Japanese developers, they are good at different fields.

I think starting in anime, like I did, gave me a good idea of how to approach games that come from Japan. Japanese developers can be very different from companies here in the western market.

The concept of emergent gameplay is really exciting. That's when players are really crafting their own experience. So if you're clever and creative, you can do things that even developers of the game didn't know were possible.

Empowering the creativity of our developers is at the core of everything we do at Roblox.

We are shifting into an enjoyment-based economy. And who knows more about making enjoyment than game developers?

The more we can make our developers famous, the better.

With VR, we have this same vision, which is create this ultimate platform for sharing your imagination. Our huge community of 300,000 developers creates awesome content that's immersive, that's social. Although now, instead of accessing it in your living room with your controller, you literally can jump into this content.

For inexperienced, small developers, getting funding from big game publishers can be a Sisyphean task.

Just as the Hare was overconfident in its speed, so the developers are overconfident in their ability to remain productive.

Architecture should reveal operation. The architecture of the system should elevate the use cases, the features, and the required behaviors of the system to first-class entities that are visible landmarks for the developers. This simplifies the understanding of the system and, therefore, greatly aids in development and maintenance.

A shopping cart application with a good architecture will look like a shopping cart application. The use cases of that system will be plainly visible within the structure of that system. Developers will not have to hunt for behaviors, because those behaviors will be first-class elements visible at the top level of the system.

The developers may think that the answer is to start over from scratch and redesign the whole system—but that's just the Hare talking again. The same overconfidence that led to the mess is now telling them that they can build it better if only they can start the race over. The reality is less rosy: Their overconfidence will drive the redesign into the same mess as the original project.

Every software system provides two different values to the stakeholders: behavior and structure. Software developers are responsible for ensuring that both those values remain high. Unfortunately, they often focus on one to the exclusion of the other.

Remember that the people who read your code will be programmers.

Why do most developers fear to make continuous changes to their code? They are afraid they'll break it! Why are they afraid they'll break it? Because they don't have tests.

The problem is that we view estimates in different ways. Business likes to view estimates as commitments. Developers like to view estimates as guesses. The difference is profound.

I actually think Facebook made it their business to be close with all of the app developers. They couldn't have done more.

When I was young, we didn't have indie games. We had 'garage developers' or similar terms, who were just small teams making games out of passion.

One of the biggest problems that software developers face is that technology changes rapidly. It is very hard to stay current.

We like to think that every month, that Roblox game page is showing off some of the most innovative, intelligent, and creative programmers, artists, producers, and developers around the world.

The community of developers whose work you see on the Web, who probably don't know what ADO or UML or JPA even stand for, deploy better systems at less cost in less time at lower risk than we see in the Enterprise. This is true even when you factor in the greater flexibility and velocity of startups.

We allow the top developers whose games are being played millions of times to translate that into U.S. dollars.

For the first time we're allowing developers who don't work at Facebook to develop applications just as if they were. That's a big deal because it means that all developers have a new way of doing business if they choose to take advantage of it. There are whole companies that are forming whose only product is a Facebook Platform application.