chairleader

Documentation is only good if you can find it again when you need it. Does anyone have a good pattern for documenting the things the team will need to have to build and deploy working software? I assume for this…

I am a professional software engineer who has spent most of his 20-year, post-college career in interpreted languages. As much as I love never having to think about pointers or threads, more and more I bump up against…

Dealing with faults is easy: read the stack trace and stop doing what shouldn't be happening. But what about errors where something should be happening but isn't? For example, I might have a notification system where…

It seems natural that a startup with a small team forego traditional project management in favor of delivering the product. However, at a certain scale, project management components start to become critical. For…