Hi!

Thanks a lot for your feedback! I'm glad that you like it here! Graphis for the site is a result of me generating very crappy first drafts and the illustrator Dmitry Zhart turning them into something really nice.

Thanks for the kind words, Ahsan!

Hi Matthias!

Thanks for reporting this! It's definitely a bug and I've just fixed. Thanks again!

Hi guys! I'm in the process of assembling the budget for this project. I think I will able to start it around September this year.

Thanks!

Hi Lukas,

It's not really required, because there are no direct relations between both at the moment. However, I'd probably advise reading the book on patterns first because it has an introduction to OOP and UML, whereas the refactoring course expects that you know all of that.

Hi!

Unfortunately, I don't have a formal syllabus for the course. However, if you need the outline for what the course covers, please visit the Catalog page. The course explains each of the topics listed there in details.

Thanks, that's a great suggestion.

Hi Syahriga!

Thanks for asking. Let me answer your questions by simply quoting parts of the article for starters:

> Why using it just to remove comment?

Make these assumptions obvious by adding corresponding assertions. As with type hinting in method parameters, these assertions can act as live documentation for your code.

> What is your consideration on using it?

If the exception can be caused by actions of the user or system and you can handle the exception. On the other hand, ordinary unnamed and unhandled exceptions are basically equivalent to simple assertions – you don’t handle them and they’re caused exclusively as the result of a program bug that never should have occurred.

If you have a followup question, shoot it! I'd be happy to help.

Thanks!