Open aschrijver opened 6 years ago
PS This excellent TechBeacon article has many nice culture improvement ideas: Lessons from 7 highly successful software engineering cultures
You're welcome @Vedikaledange I haven't checked Dat for a while, so much may have changed. For example, datproject.org website has been revamped and improved since, and there are other organizational changes.
(NOTE This proposal is part 1a of Positioning, vision and future direction of the Dat Project)
As a newcomer to dat coming from a business-oriented development culture I made some interesting observations on the dat community culture that I would like to analyse further. (Note: This discussion was started in https://github.com/codeforscience/sciencefair/issues/153)
PS I admire all the great people I've met so far! Below analysis is only meant to be constructive, and in no way offensive.
Community culture swot analysis
Strengths:
Weaknesses:
Opportunities:
Threats:
reliance on individuals
Consider if one core team member - e.g. @mafintosh - is suddenly no longer available to the dat project or at all, e.g. due to other cool job, sabbatical, or personal reasons?
implicit programmer anarchy
The community culture swot traits above are reflected in the general approach to development, which I would describe as implicit programmer anarchy (as opposed to explicitly opting for this approach).
From What is programmer anarchy and does it have a future?:
But: Not explicitly recognized, chosen or followed. The anarchism follows from cultural traits
developer myopia antipattern
There may already be some 'developer myopia' at play in dat project. A risk that is likely to increase if not tackled.
This antipattern is very similar to 'marketing myopia':
Taking a step back regularly and reconsider what you're doing and where you're headed is sensible advice, and boils down to becoming a bit more strategic in your approach.
Next part: Improve dat-awesome page