Group items tagged

TechEd Europe 2012: one of the best talks of the conference. If you love coding, you will love this talk about dealing with streams of events using the Reactive Extensions framework.

The goal of this blog entry is to explain the basic concepts of Scrum in less than five minutes. You learn how Scrum can help a team of developers to successfully complete a complex software project.

Some time ago, the development team at my firm staged a revolt against the sales team and senior management: our demand was that no Statement of Work was to be sent to a customer without first being reviewed by a member of the development team. [..] Today I would like to explore an important aspect of any Statement of Work: the pricing model.

"No matter which source control system you decide to use, there are a number of universal principles that will help you to get the most out of source control."

"As soon as you have more than a trivial set of tasks you'll need a better system than a simple list and for agile teams, we have Scrum's product backlog."

Using peer code review best practices  optimizes your code reviews, improves your  code and makes the most of your  developers' time. The recommended best  practices contained within for efficient,  lightweight peer code review have been  proven to be effective via extensive field  experience.

A popular saying goes that programmers are machines that turn caffeine into code. And sure enough, ask a random programmer when they do their best work and there's a high chance they will admit to a lot of late nights. Some earlier, some later. A popular trend is to get up at 4am and get some work done before the day's craziness begins. Others like going to bed at 4am. At the gist of all this is avoiding distractions. But you could just lock the door, what's so special about the night? Read more: http://swizec.com/blog/why-programmers-work-at-night/swizec/3198#ixzz2q7HdMxaZ