Quotes About Development

Implementation Patterns.

We in this industry sorely need to increase our professionalism. We fail too often. We ship too much crap. We accept too many defects. We make terrible trade-offs. Too often, we behave like unruly teenagers with a new credit card. Martin, Robert C.. Clean Agile (Robert C. Martin Series) . Pearson Education. Kindle Edition.

Am I suggesting 100% test coverage? No, I'm not suggesting it. I'm demanding it. Every single line of code that you write should be tested. Period.

the history of software development technology is the story of how to conveniently create plugins to establish a scalable and maintainable system architecture.

You should be able to run all the unit tests with just one command.

Professional developers do not prevent others from working in the code. They do not build walls of ownership around code. Rather, they work with each other on as much of the system as they can. They learn from each other by working with each other on other parts of the system.

The most efficient and effective way to review code is to collaborate in writing it.

QA and Acceptance Tests If QA has not already begun to write the automated acceptance tests, they should start as soon as the IPM ends. The tests for stories that are scheduled for early completion should be done early. We don't want completed stories waiting for acceptance tests to be written.

If a component contains software that should be reused, it should not also contain software that is not designed for reuse. Either all the classes in a component are reusable, or none of them are.

The tests fit the production code like an antibody fits an antigen.

Procedural code (code using data structures) makes it easy to add new functions without changing the existing data structures. OO code, on the other hand, makes it easy to add new classes without changing existing functions.

refactored)    /**

Analysis and design are not binary deliverables. They do not have unambiguous completion criteria. There's no real way to know that you are done with them.

THE STABLE ABSTRACTIONS PRINCIPLE A component should be as abstract as it is stable.

The complement is also true: Procedural code makes it hard to add new data structures because all the functions must change. OO code makes it hard to add new functions because all the classes must change.

That's being attentive to every variable name. You should name a variable using the same care with which you name a first-born child.

software artifact should be open for extension but closed for modification.

Don't hide side effects with a name. Don't use a simple verb to describe a function that does more than just that simple action.

So, when and why should we use UML? Diagrams are most useful for communicating with others and for helping you work out design problems.

Os padrôes facilitam a reutilização de ideias e compomentes, recrutam pessoas com experiência considerável, encapsulam boas ideis e conectam os compomentes. Entretanto, o processo de criação de padôes pode, ás vezes, ser muito longo para que o mercado fique á espera deles, e alguns padrôes acabam se desviando das necessidades reais das pessoas a quem eles pretendem servir.

Classes and modules that are grouped together into a component should be releasable together. The fact that they share the same version number and the same release tracking, and are included under the same release documentation, should make sense both to the author and to the users.

As you mature in your profession, your error rate should rapidly decrease towards the asymptote of zero.

The architecture of a software system is the shape given to that system by those who build it. The form of that shape is in the division of that system into components, the arrangement of those components, and the ways in which those components communicate with each other.

the architecture of a system has very little bearing on whether that system works. There are many systems out there, with terrible architectures, that work just fine. Their troubles do not lie in their operation; rather, they occur in their deployment, maintenance, and ongoing development