Thank you for the article, I've enjoyed it. And I have couple of thoughts on the subject, that I'd like to share.
"Hello world" is more of a teaser than an actual introduction. Something to make you want to read "The book of {language}", which explains the pros and cons and the process in depth.
A generic "Hello world" example sets a simple task and gives you an immediate feedback, giving you a taste of the flow.
One more thing to add is that globals, monkey patching and side effects are not to be demonized. Instead we should promote right use for the right tool, expanding the possibilities and creativity of the newcomers.
Why do we write crappy code? Because we're tired, lazy or there was no time for the tests (hint: there's always time for the tests)
Learn something new every day.
- I am a senior software engineer working in industry, teaching and writing on software design, SOLID principles, DDD and TDD.
Location
Buenos Aires
Education
Computer Science Degree at Universidad de Buenos Aires
Thank you for the article, I've enjoyed it. And I have couple of thoughts on the subject, that I'd like to share.
"Hello world" is more of a teaser than an actual introduction. Something to make you want to read "The book of {language}", which explains the pros and cons and the process in depth.
A generic "Hello world" example sets a simple task and gives you an immediate feedback, giving you a taste of the flow.
One more thing to add is that globals, monkey patching and side effects are not to be demonized. Instead we should promote right use for the right tool, expanding the possibilities and creativity of the newcomers.
Why do we write crappy code? Because we're tired, lazy or there was no time for the tests (hint: there's always time for the tests)
Interesting. I agree with you