English Boards > V3 Development

Are the Rules getting too complicated ?

<< < (2/3) > >>

JohnS:
For me, the hardest part is knowing what variables can be used with each rule.
Using Printer Template Tags as a base for variables is a great idea.

And we definitely need an easy way to read Ticket Tags and Ticket States, so we don't need to track info already available with Update Program Settings.

We are putting together manuals for SambaPOS, but some things like promotions are hard to document because there can be so many variants, and honestly, most of my customers would rather pay me to configure the backend for them.

emre:
John no problem I can create documentation and as more people gets features they'll contribute. However we need to reach final state to prevent double work. For example as we implement tooling like Wolfgang suggested documentation should change.

Ticket Tags and Ticket States can be read by printer template tags like {TICKET TAG:Blah}. When I bring it to final state you'll see it will be even easier than we thought (V2) :)

Note: I prefer to write documentation because while writing it I notice a lot of issues and fix them. This is something like a test.

JohnS:

--- Quote from: emre on August 21, 2013, 06:06:37 pm ---Note: I prefer to write documentation because while writing it I notice a lot of issues and fix them. This is something like a test.

--- End quote ---
For the backend, like Rules, Accounts, etc you will not get any arguments from me :) And I am the same with documentation.

We are putting together manuals for end users to cover day to day activities. These processes will hardly change.

JohnS:
I understand the issue with documentation. As SambaPOS keeps evolving, any current documentation runs the risk of being outdated. And this really is not a bad thing. All it means is that SambaPOS is reaching new levels of potential and features.

My lecturers used to complain that when we had a programming assignment, I would start coding first. They kept saying that I needed to do a high level design first. My reply was, that would be double work as the end result would be different to the original concept and half way through I would find better ways of doing something.
In the end they gave up because I always got 80% or higher marks and more often then not I had more interesting solutions to the problems.

emre:
I think in ancient times (!) most software development ideas taken from civil engineering :) We should thank to Kent Beck (and other special people) for agile software development idea.

Navigation

[0] Message Index

[#] Next page

[*] Previous page