Inspiring ideas from the Smalltalk community Smalltalk Best Practice Patterns, Kent Beck - List from Linda Rising  - Book draft Design Principles Behind Smalltalk, Daniel H. H. Ingalls, 1981 Smalltalk: Overview and Implementation Issues, 2002-2003 Dan Ingalls on the History of Smalltalk ...

Smart ideas from Smalltalk, forgotten and waiting to be re-invented The focus on message passing in OO programming.  Watch InfoQ interview with Ralph Johnson and Joe Armstrong on the State of OOP A language defined only with very simple rules, with the underlying concepts that are *simple* and *uniformly* applied.  The underling principle is that: If a system is to serve the creative spirit, it must be entirely comprehensible to a single individual. ...

Innovative ideas originated from Smalltak It is surprising how many innovations introduced recently originates from Smalltalk. This is an opportunity to go back to the origins of those ideas and better and deeper understand them. Some examples? Smalltalk implemented a platform-independent Virtual Machine and application program interface based on industry standards before Java (and so before .NET ). Smalltalk was one of the first systems to pioneer the WIMP (Windows, Icons, Menus and Pointers) interface (it was the one Steve Jobs...

Some alive and kicking Smalltalk free implementations Smalltalk/X: http://www.exept.de/en/products/smalltalk-x/stx-overview Pharo: http://www.pharo-project.org/ Squeak: http://squeak.org/ Now to play with the language, here we go : I can Read C++ and Java But I can't Read Smalltalk Smalltalk basics Introduction to Smalltalk ...

Learning Smalltalk why ? When you are ready to listen to the answer, the right question will naturally come Here a list of possible good reasons:  Why Smalltalk? My why to Smalltalk: Reading Smalltalk code will give me access to a library of books and papers and articles from a smart group of people with bright insights and a deep understanding of computer programming: a lot of forgotten gold lessons that can still be a competitive advantage. And also computer programming is old enough...

   1st Law of Software Process: Process only allows us to do things we already know how to do. 2nd Law of Software Process: We can only define software processes at two levels: too vague and too confining. Source: The Laws of Software Process: http://www.corvusintl.com/CACM003-LoSWP.htm A methodology is the conventions the team agrees to follow. Methodology Success = Project delivered + Staff would do it again Source: http://alistair.cockburn.us/Everyone+should+be+a+methodologist A software development process is a framework imposed on the development of a software product. Source: http://en.wikipedia.org/wiki/Software_development_process   Tags :  Team Work | Agile | Pratiche | Leadership | Progettazione Software | Traduci al ITALIANO...

An excerpt from Joseph Pelrine training material about Identities: are the roles and the responsibilities. By changing someone's role and identity you change the identity of the team. A human can have many identities and exist in multiple socially complex systems simultaneously, and the context will determine which identity dominates.     An identity, as I understood, can be a responsibility assigned to some team member, a role in the organization assigned to someone, or simply an already existing identity (personal, professional, ...). In a system is possible to add or remove or change a responsibility, assign a role,  reinforce or weaken...

An excerpt from Joseph Pelrine training material about Environment:  The fifth letter in ABIDE stands for Environment, starting with the purely physical environment but also the workplace culture. If you change your workplace structure, if you move people to different offices for example, you will change the dynamics of the team. Environment is also a prerequisite for a self-organising group. Another excerpt from Joseph Pelrine training material about Environment:  The emergent process of self-organisation requires a space to occur. Not too much space – that would allow the agents to avoid each other, and...