Download A Mentoring Course on Smalltalk by Andrés Valloud PDF

By Andrés Valloud

A developer regularly seeks higher knowing of software program engineering and layout. occasionally success intervenes and a mentor is helping to strengthen one's skills. even if, there are just such a lot of of those infrequent encounters, and hence, no longer everyone seems to be afforded such possibilities. This publication makes an attempt to take away good fortune as a proscribing issue for one's specialist development in Smalltalk through disseminating fabric realized over numerous years of mentoring.

Show description

Read or Download A Mentoring Course on Smalltalk PDF

Similar programming: programming languages books

Flash MX Application & Interface Design: Data delivery, navigation, and fun in Flash MX, XML, and PHP

The times of Flash as an artistic luxurious are long past. After months of downsizing, Flash creativity has been on an enormous explanation software. it truly is not sufficient to give animation in hundreds of thousands of colours and 100 transparencies. it really is now not enough to supply interactivity and dynamism for his or her personal sake.

Extra resources for A Mentoring Course on Smalltalk

Sample text

But in the same way readers would disapprove of such a writing style, any savings are made by abbreviating names in Smalltalk would quickly vanish when examining or changing the same code at a later point in time. The implementation of behavior is a much more permanent expression of intention than a quick scribble. At the same time, it must allow change at a low cost. Therefore, there is no excuse for laziness nor carelessness. Names should not betray the private nature of implementation details either.

Write only one method. Hardcoding class names or overloading doesNotUnderstand: are not allowed. 0d raisedTo: -1070 one would expect that the one below would work as well. 0d raisedTo: 1070) And yet, it does not. Why? 26 [29] What, if anything, is wrong with this? 27 [35] Create a new class called Test. In a workspace, evaluate the following code. t := Test new. Smalltalk at: #test put: t. Test become: String new After doing this, trying to send any message to t will cause the virtual machine to crash because the class of t will be the empty string.

Despite how hard we try to design the messages, either the order of evaluation causes problems, or syntactic sugar appears, or the pattern simply does not work at all. No matter what we come up with, the result always seems contrived and unnatural. To summarize, using multiple messages is causing too much difficulty. While this may seem obvious and perhaps a bit harsh, the phrasing is key because it hints at a problem looking for a solution3 . 3 Note how stating a requirement makes it so much easier to find the answer!

Download PDF sample

Rated 4.84 of 5 – based on 47 votes