One way to address this issue is to factor in your development grooming of young Smalltalk developers, which can act as pool of potential full developers for your project. If you can add some of your domain specific issues to their grooming, you could increase your project HR safety quite a lot.
Davorin Rusevljan On Thu, Oct 19, 2017 at 9:04 AM, Paulo R. Dellani <dell...@pobox.com> wrote: > Dear all, > > after using Smalltalk for several years I developed a passion for the > language (how not to?), and Pharo is just so great to develop with. > So thank you guys for keeping this wonderful project running. > > Unfortunately, it is not easy to always point out why Smalltalk > should be employed as "main development language" in a team > or for a project. In the last discussion of this sort I was confronted > with the question "where are we going to get new smalltalk > developers if our startup grows or if you go?". Well, I had no > good answer to that. What would have you answered? > > Cheers, > > Paulo > > >
