On 5 February 2013 13:13, Camillo Bruni <[email protected]> wrote: > > Ask yourself: > - why do we have tests? > - why do multiple people work together? > - why do we want publicly available artifacts? > - why do we want these artifacts tested publicly? > - why do we write configurations? > - why do we try to following coding standards? > - why do we program in Smalltalk? > - why do we mostly write deterministic code? > - why do we work on Pharo? > - why do we build a jenkins infrastructure? > - why do we write down documentation? > > > After successfully answering these questions you will understand!
Of course you right. But i am not arguing about that. Can't you understand? If you took initiative about something, don't expect that others will work in same pace as you or automatically/immediately pick up everything you did and integrate it into their working cycle. It takes time and effort (both mental and physical). Ask yourself: - who, except original author knows best how things work? - when you creating a new artefacts, like a bunch of bash scripts for jenkins. Who, you think, should take responsibility about them by _default_? - when you reconfiguring stuff and doing it completely different than it was done before, why you think that rest of the world should immediately jump in and start using it? - and finally, when you creating/releasing new stuff every other day.. how many people is capable of keeping clear track of what you are doing over months (+ doing own tasks)? -- Best regards, Igor Stasenko.
