Jeff Dutra

Background

About Jeff Dutra

List of things that define how I approach software development 1. People over process: it is important to have the right people. This allows you to trust in your team and use as little process as needed. Writing software is a creative enterprise, therefore you have to ensure developers are not hamstrung by a process put in place to minimize the negative impact of untrusted team members. Test Driven Development: unless you are prototyping an idea, you need to write tests before you write any application code. You need to structure those tests in way that also provides documentation for your software. Adhere to design principles: whether the principle is for interface design, or software development there should be clear and valid business reasons to stray from a principle. Be agile: for me "agile" is not a template that comes with Jira. You process needs to always be reviewed and modified; this should not be hampered by the techology you are using. Software craftsmanship: this includes things like write great code, name things well, make your code very readable. Refactor to improve future business outcomes, not because the code will look better. Avoid over-engineering: build the simplest solution to the problem 7. Don’t label things as “Best Practices”: instead think of them as you current practices, which are based on research and experience; the main difference is that you realize there could be a better way and you should constantly look for better ways to solve problems. Support others in achieving all the stated ideals