Strategy/algorithm to divide pot to chips
I want to split poker pot to chips.
would a composite design pattern be useful for group membership?
I’m trying to think about the best way to handle group memberships on a website. People sign up and select checkboxes in a list of interests. Every week we send out interest-themed emails to those members that indicated that interest.
Liskov substitution and abstract classes / strategy pattern
I’m trying to follow LSP in practical programming. And I wonder if different constructors of subclasses violate it. It would be great to hear an explanation instead of just yes/no. Thanks much!
Where to check that a function actually did what I told it to?
Consider this function intended to kill all running instances of a subprocess:
Context class in Strategy pattern
I’m trying to understand the strategy pattern and asking myself: is the context class must-have or can I leave it out without compromising pattern’s purpose ?
Do integrated systems increase development time and cause inflexibility?
I work for a large financial company that manages money for thousands of clients. This company has very complex business processes and they operate in a very dynamic environment.
How to handle “animated” game where the visual should “animate” instead of abruptly change?
I’ve been playing around and learning javascript/KineticJS by making some simple games (think like board games).
Best strategy in SQL
Recently, a colleague told me that it wasn’t advisable to make conditions in the join clauses. Instead he suggested to make conditions in the where clause. He told me that the SQL engine was optimized for this way.
Inheritance vs ‘specification’ by fields
I’m currently reading ‘Head first design patterns’ and I already have a few questions on the first chapter of the book.
This chapter introduces the ‘prefer composition over inheritance’ design principle, by explaining the ‘Strategy-Pattern’. My question isn’t about the pattern, but rather about a more basic design decision in one of the examples:
Inheritance vs ‘specification’ by fields
I’m currently reading ‘Head first design patterns’ and I already have a few questions on the first chapter of the book.
This chapter introduces the ‘prefer composition over inheritance’ design principle, by explaining the ‘Strategy-Pattern’. My question isn’t about the pattern, but rather about a more basic design decision in one of the examples: