Fruits of CSS2: Eating Our Own Dog Food
It may seem obvious but eating our own dog food can definitely be good for your project's condition. Especially when it is maturing over time. How many testers can we have and how many personas for your user-centered design can we define and maintain? Usually just a few with the actual resources. Is only fulfilling needs of more or less fictional actors focusing on few use cases a good direction? Or does it put our vigilance to sleep?
Well, I am convinced you and your co-workers can be good actors if you actually start using your software more.
In the CSS2 presentation I published above there are only few but probably telling examples of what features of Calligra we can start using more in the project and how. There also a 'why'. Never force using apps if there are better (or good enough) tools already in place. Own dog food consumption can also be a risky business if the usage feels superficial and would not finally translate to any real-world use cases.
For example I do not intend to employ Kexi database creator for ad-hoc spreadsheet calculations on small, loosely structured data. Kexi and databases in general were not designed with this use case in mind. So as always it is better look closer.
The idea already brings its fruits. Adam has already set up a PostgreSQL server for internal project-related services, in addition to various tests we plan to host there.
Can you quickly identify your products' use cases that can be introduced by your team eating your own dog food? Please leave them in the comments section below.
PS: Next time in the CSS2 series on shared Calligra themes.
