16/11/2015

SAY AYE IFYOU THE 90s

https://en.wikipedia.org/wiki/St._Peter%27s_Basilica

https://en.wikipedia.org/wiki/Bazaar

DOING F/LOSS
the Cathedral & the Bazaar

Apostolos Kritikos, PhD Candidate
Informatics Dept., Aristotle University of Thessaloniki

@ TRANSMYTHOLOGIES IN ARCHITECTURE
School of Architecture, Aristotle University of Thessaloniki

Advanced Design: Innovation and Transdisciplinary in Architectural Design
Post-Graduate programme of studies

Unless otherwise expressly stated, all original material in
Doing F/LOSS. The Cathedral and the Bazaar by Apostolos Kritikos, 2015,
is licensed under Attribution-ShareAlike 4.0 International and CAN BE REUSED!

C o d i n g ! ! !A personal journey!
[ HINT: The elements are clickable ;) ]

2000ish

2003

20082010 HELLO WORLDBScMSc

2011PhD2016

2014

Social Mind

.: I :.it will not be possible to be and not to be the same thing

-- Aristotle
(law of excluded middle)

via Wiktionary.org

via Wiktionary.org

via Wiktionary.org

via Wiktionary.org

via Wiktionary.org

.: II :.The fact that this bazaar style seemed to work, and work well, came as a distinct shock. As I learned my way around, I worked hard not just at individual projects, but also at trying to understand why the Linux world not only didn't fly apart in confusion but seemed to go from strength to strength at a speed barely imaginable to cathedral-builders.

-- Eric Raymond
(the cathedral and the bazaar)

WHAT DO THE FOLLOWING MEAN TO YOU?

-- Eric Raymond(the cathedral and the bazaar)

Every good work of software starts by scratching a developer's personal itch.

Good programmers know what to write.
Great ones know what to rewrite (and reuse).

Plan to throw one away; you will, anyhow.
(Fred Brooks, The Mythical Man-Month, Chapter 11)

If you have the right attitude,
interesting problems will find you.

When you lose interest in a program, your last duty to it is to hand it off to a competent successor.

Treating your users as co-developers is your least-hassle route to rapid code improvement and effective debugging.

Release early. Release often. And listen to your customers.

Given a large enough beta-tester and co-developer base, almost every problem will be characterized quickly and the fix obvious to someone.

Smart data structures and dumb code works a lot better than the other way around.

If you treat your beta-testers as if they're your most valuable resource, they will respond by becoming your most valuable resource.

The next best thing to having good ideas is recognizing good ideas from your users. Sometimes the latter is better..

Often, the most striking and innovative solutions come from realizing that your concept of the problem was wrong.

Perfection (in design) is achieved not when there is nothing more to add, but rather when there is nothing more to take away.''

Any tool should be useful in the expected way, but a truly great tool lends itself to uses you never expected.

When writing gateway software of any kind, take pains to disturb the data stream as little as possibleand never throw away information unless the recipient forces you to!

When your language is nowhere near Turing-complete, syntactic sugar can be your friend.

A security system is only as secure as its secret. Beware of pseudo-secrets.

To solve an interesting problem, start by finding a problem that is interesting to you.

Provided the development coordinator has a communications medium at least as good as the Internet, and knows how to lead without coercion, many heads are inevitably better than one.

.: III :.I think a good rule of thumb that will scale with the community as it continues to grow is that organizations that want to grow the WordPress pie (and not just their piece of it) should dedicate 5% of their people to working on something to do with core be it development, documentation, security, support forums, theme reviews, training, testing, translation or whatever it might be that helps move WordPress mission forward.

-- Matt Mullenweg

HOW DO YOU WORK?(SYSTEM)

Scrum

https://en.wikipedia.org/wiki/Scrum_%28software_development%29

+CONVENTIONS

https://en.wikipedia.org/wiki/Scrum_%28software_development%29

- requirements
- coding standards
- documentation standards
- testing
- naming
- versioning

WHERE DOES YOUR CODE LIVE?

HOW DO YOU COMMUNICATE?

( All trademarks, service marks, trade names, trade dress, product names and logos appearing on the slide are the property of their respective owners )

U R COMMUNITY!
NOW WHAT?

(THE FLOOR IS YOURS)

Apostolos Kritikos

/akritiko

/in/apostoloskritikos

akritiko@gmail.com

Check www.socialmind.gr
we working with F/LOSS

thanks :)