3 ms·
Unless you're starting with zero.. Skills on the team? Current stack? If nothing then I do this: Git and stash. An agile approach, features and user stories.
by quintes 10y ago
Unless you're starting with zero.. Skills on the team? Current stack?
If nothing then I do this:
Git and stash.
An agile approach, features and user stories.
An agile board. Vsts or rallydev
Yes to continuous integration, deployment and automation.
Testing, unit tests first.
A desktop application may have specific technologies so .. depends.
Oh and code review, pull requests and I actually advise desk checks before submitting PRs.
Regular demos of sprint work is essential
- chris11 10y agoThose are good points. Tech stack can be anything as long as it runs on windows. What's the benefits of doing desk checks and code reviews?
- jyounker 10y agoCode reviews are one of the best ways we've found to improve code quality. If you're not familiar with it, then you should read up on it. There are plenty of resources out there discussing code reviews (e.g. http://dl.acm.org/citation.cfm?id=2597076 http://dl.acm.org/citation.cfm?id=2597076 or Steve McConnell's "Code Complete".) Think about it this way. Code is as complicated writing. There is no successful media organization in the world that would publish a book or magazine without at least having one round of review, because hundreds of years of practice has shown that review improves the final product significantly. It's hubris to imagine that programmers are any better than authors.
- chris11 10y agoOh, definitely. Code reviews are really valuable. I'm just curious about desk checks in addition to code reviews. Edit: that paper's pretty interesting. I haven't really thought about what made good code reviews and what the causes of defects are.