Scoring
Please don’t ask me what the score is, I’m not even sure what the game is.
I made a design decision to store all of the scores in one long text field…
The model relationships
A true relationship is when you can tell each other anything and everything. No secrets and no lies.
I’ve had a lot of playing with ORM relationships, mostly getting it sort of right. I’ve always hating reading other peoples code trying to work out what I’m supposed to do but sometimes it’s the easiest way.
The following code fragments show my current Model implementation in regards to their ORM relationships. If you read these in conjunction with the data schema you may learn something. On the other hand you might see what I’ve done wrong. If so, don’t be shy 🙂 Read more ›
Create a database schema
Without requirements or design, programming is the art of adding bugs to an empty text file. – Louis Srygley
So, this is what I came up with:
Identify the problem
First, solve the problem. Then, write the code. – John Johnson
I would qualify that: first, identify the problem.
Kohana 3.3 Introduction
The best programmers are not marginally better than merely good ones. They are an order-of-magnitude better, measured by whatever standard: conceptual creativity, speed, ingenuity of design, or problem-solving ability. – Randall E. Stross
I am merely good… and sometimes merely. To make up for this I am always looking to reuse code written by the best.
A self-preservation technique I try and follow is to not use other code that I don’t understand. Unfortunately this is a bit of a handicap for me because there is an awful lot that I don’t understand!
And then I found Kohana. I won’t pretend to understand it all but it is such a light elegant framework that it IS understandable. And it works.