This morning, while reading one of Coding Horror’s classic blog posts on software schedules, On Our Project, We’re Always 90% Done, I came across an essay from Mary Poppendieck, which argues against rewarding team members by merit pay.

In his book, Practice of System and Network Administration, Tom Limoncelli explains the importance of writing down the requirements for the system you are building. I think the list applies equally well to software projects. Having a list of clear requirements written down is probably one of the most important things you can do before starting a project.

One of the quirks of being an enterprise software developer is that when your users find a problem with the product, they actually call your company support. Most of the time, the support resolves the issues on their own, but sometimes, especially for complicated ones, developers have to get on the call and see what’s going on.

People are interested in how you work, if only you presented it to them in the right way.

I am looking for a roommate to share my one bedroom apartment on Quadra-Mckenzie. It’s a semi-private room, most suitable for students who are looking for temporary stay.

One of the classic Stoic texts that has stood the tests of time for over two thousand years.

One of the best books on finance. Doesn’t delve into complex formulas, saving money on lattes, or maths. Instead focuses the fundamentals. Simplicity, discipline, patience, and a focus on the long-term.

In C#, we can declare properties in a few different ways. Let’s try to understand each one in detail.

Agile is the most common software development methodology used when building software. Ideally, it means that you don’t do any big, upfront design. Instead, you work in sprints and evolve your design as your understanding of the project grows. Design is part of the programming.

Though I didn’t read as many books as last year, I read them with more focus and understanding. Here are all the books I read in 2019.