|
@ -1,5 +1,18 @@ |
|
|
# Lerntagebuch |
|
|
# Lerntagebuch |
|
|
|
|
|
|
|
|
## Vorlesung vom 24.10.2023 |
|
|
|
|
|
|
|
|
## lecture 24th October 2023 |
|
|
|
|
|
|
|
|
### |
|
|
|
|
|
|
|
|
### takeaway |
|
|
|
|
|
- developer != artist |
|
|
|
|
|
- developer == craftsman |
|
|
|
|
|
- developer does not express emotions |
|
|
|
|
|
- developer solves problem |
|
|
|
|
|
- professional developer sets himself apart from non-professionals with following well thought through guidelines and best practices |
|
|
|
|
|
|
|
|
|
|
|
### perception |
|
|
|
|
|
Following modern clean code best practices that have stood the test of time is a good idea for the group project. |
|
|
|
|
|
Favoring polymorphism over inheritance is one of such practices. |
|
|
|
|
|
More examples can be found on the [CleanCodeDeveloper](https://clean-code-developer.com) website. |
|
|
|
|
|
|
|
|
|
|
|
### repetition |
|
|
|
|
|
Developers should not be considered artists. An artist expresses his emotion with his work. On the contrary, developers solve a real world problem enabling businesses to gain an edge on their competitors for example. As such, developers are way closer to craftsmen than artists. |