This is more a system design question/challenge, than a coding question. Basically, I'm thinking of throwing together a Bejeweled-esque game on Facebook using just HTML, CSS, and javascript. This is mostly out of a desire to learn all the little caveats of FBJS via a non-trivial project. So here's the deal. When developing for Facebo...
G'day, While having a think about this question here about overdesigning for possible future changes it got me thinking. What reasons against can you provide to people who insist on blowing out designs because "they might want to use it somewhere else at some stage in the future"? Similarly, what do you do when people take the require...
I hate having a bunch of "left/right" methods. Every time a property is added or removed, I have to fix up each method. And the code itself just looks ... wrong. public Foo(Foo other) { this.Bar = other.Bar; this.Baz = other.Baz; this.Lur = other.Lur; this.Qux = other.Qux; this.Xyzzy= other.Xyzzy; } Really this is ...
I'm writing a wide component infrastructure, to be used in my projects. Since not all projects will require every component created, I've been thinking of splitting the component into discrete assemblies, so that every application developed will only be deployed with the required assemblies. I assume that creating an assembly has some s...
I have a simple program which can have an admin user or just a normal user. The program also has two classes: for UserAccount and AdminAccount. The things an admin will need to do (use cases) include Add_Account, Remove_Account, and so on. My question is, should I try to encapsulate these use-cases into the objects? Only someone who is...
Example: I need to manage users in a website,'manage' means: register and allow them to send comments. user registration will use: username, email, password and user_id comments will have: date, link, text and user_id Now, I have several projects with similar structure - give or take a table/field or two.. I hate writing it all again a...