If I were going to give this talk, I would want to change a few things.
- If I was going to put an example of bad code on the screen, I would use my own code.
- If I was going to put an example of good code on the screen, I would use somebody else's code.
- I would avoid ever saying "you should", "you must", or "is important". Instead, I'd say something more like "I always try to ... because ...". But that's just me.
There is nothing wrong with an opinionated talk. It's entertaining and engaging.
This topic needs to be covered by a speaker with a bit more experience. Also, dogging the person who wrote your negative example is not cool. It would have been more appropriate to dodge the question.
Also, the personal positive example, while better then the negative example, could have used a lot of work.
I would suggest next time, take a bad example and walk through the process of making it better.
Comments
Comments are closed.
If I were going to give this talk, I would want to change a few things.
- If I was going to put an example of bad code on the screen, I would use my own code.
- If I was going to put an example of good code on the screen, I would use somebody else's code.
- I would avoid ever saying "you should", "you must", or "is important". Instead, I'd say something more like "I always try to ... because ...". But that's just me.
There is nothing wrong with an opinionated talk. It's entertaining and engaging.
Excellent talk. Gave clear examples of how to improve our code. Can't wait to hear his next talk.
This topic needs to be covered by a speaker with a bit more experience. Also, dogging the person who wrote your negative example is not cool. It would have been more appropriate to dodge the question.
Also, the personal positive example, while better then the negative example, could have used a lot of work.
I would suggest next time, take a bad example and walk through the process of making it better.