| |||||||||||||
Avoiding the OS abstraction trapAvoiding the OS abstraction trapPosted Aug 12, 2011 23:25 UTC (Fri) by neilbrown (subscriber, #359)Parent article: Avoiding the OS abstraction trap
Several good points but this is my favourite:
> The "community" is external to the development team
It is nonsense in much the same way that a "stable ABI" is nonsense.
Integrating with the rest of the community certainly requires an inventment and if you cannot afford the time, then "Arrang[ing] for a developer with at least 100 upstream commits to be permanently assigned to the development team" sounds like a suitable alternative investment strategy.
I can just see a new standard line in resumes:
(Log in to post comments)
Avoiding the OS abstraction trap Posted Aug 13, 2011 5:58 UTC (Sat) by agrover (subscriber, #55381) [Link]
I definitely had a line like that on my resume, the last time I was job-seeking.
We don't want # of contributions to be a major career boost (otherwise people will game the system with more patches) but it does loosely correlate with something of value on a CV.
Avoiding the OS abstraction trap Posted Aug 16, 2011 8:20 UTC (Tue) by Np237 (subscriber, #69585) [Link]
As long as these patches are useful additions or real bug fixes (which the acceptance guidelines should guarantee), this is not “gaming the system”. Quite the opposite actually, it means giving more incentive to improve the system.
|
|||||||||||||