Relative Content

Tag Archive for development-process

Is code reviewing good practice?

When the company I work in hired new managers, they offered us to overview someone’s code on every meeting. We have meetings every two weeks, so each time one of developers was to show his/her code on the projector, and others were going to discuss it.

Add a second developer to the team

In my company, I’m the only developer, but we plan on expanding the team by hiring a second programmer. I know there are a lot of implications to that (especially around source control). I’ve Googled a lot, but haven’t found a good tutorial/article on how to grow the team from one to many developers.

Are unit tests really that useful? [closed]

As it currently stands, this question is not a good fit for our Q&A format. We expect answers to be supported by facts, references, or expertise, but this question will likely solicit debate, arguments, polling, or extended discussion. If you feel that this question can be improved and possibly reopened, visit the help center for […]

How to avoid typo errors, etc?

For the first time I have been coding for an open-source software where all my work gets reviewed before being commited. I understand reviewing work isn’t an easy task, so I don’t like to waste reviewers’ time and effort. But many times I make silly typo errors and errors of other kind while making a change in the code.

Are there any good, open-source change request systems? [closed]

As it currently stands, this question is not a good fit for our Q&A format. We expect answers to be supported by facts, references, or expertise, but this question will likely solicit debate, arguments, polling, or extended discussion. If you feel that this question can be improved and possibly reopened, visit the help center for […]

User Stories with design elements in Scrum

We’re implementing a Scrum workflow and I’m trying to wrap my head around user stories, when they’re completed, iterations, etc. One thing we often do is work on a story during an early iteration, get it fully working but “ugly”. We use plain buttons, no images, just the text to show that it’s working the way they should. We show our customer, make sure they are happy with how it’s working, then we usually use images they provide to finish up the design of the feature and complete it.