few days ago we discussed among "Javer" of Biko2 on best practices, tools, libraries, automated that each project should take in search of truth ie, perfect quality:)
Began a lot about specific issues, and ramble a bit about some tools and practices to be incorporated or strengthened, that's what we love to discuss how to most. These issues the association at the tactical level of implementation of agility in an organization, short-term maneuvers that are directly applicable to obtain a purpose on the battlefield. But I got the impression that we were lost in acronyms and names, and share a little levels that was important. We then extract a bit of email to send at that time to my colleagues, on the levels of performance for quality, as developers in technical work:
- Programming: PMD and Checkstyle (code analysis tools) help us not to make mistakes more, even having to review any rules that say. But every line you write is a decision we made on the application, and that can only be resolved with the developer intelligence. You have to know things SOLID exception management, log management, ... etc. that can not be automated.
- Ecosystem: The ecosystem we can see that we do not break the build, we have good coverage of tests, we do TDD infrastructure will purchase, good sound metrics, automatic deployment, the management of merges / branches .... but all this, there is no way we go it alone ... only depends on intelligence, and now also the hard work developer. Need to know about continuous integration, Branch Management, ...
- Application: A standard application is the definition of over-TER-MI-NA-DO, the evidence acceptance, or the functional part. Here comes into play above: the intelligence and hard work, but above all, responsibility and commitment developer, wanting to do things right and move customer.
0 comments:
Post a Comment