This code is awesome. This code is CRAP!
WCF, Windows Live Writer
Future Ticketing Programme
Part of a ticketing modernisation programme
Sending card taps to a back office affords the organisation to centralise behaviour and move hardware costs from the gates to the cloud.
A centralised back office ticketing system.
Permit high throughput cheap travel.
"Every journey matters"
What differentiates an organisation from their competitors, what is their USP?
This is where we tend to concentrate our efforts to best support an organisation to give it a competitive advantage.
Supporting the core domains. Commodity business process like invoicing, CRM, ERP.
Where to put that magic source?
Does your domain require a hi-tech solution?
What is a fat model, skinny controller, what is an anemic domain? Do we care? Yes. Why?
Understand the why behind the problem
Appreciating good enough
Putting the model at the heart of the problem
Facilitiate emergent design
Have confidence to meet business demands
Using or based on what one feels to be true even without conscious reasoning;
instinctive: his intuitive understanding of the readers' real needs
Composition is explicit. Explicit code is more intuitive.
Abstractions require more reasoning and are not always intuitive
Never use an abstract class for code re-use