meta user
network profile
| bio | website | |
|---|---|---|
| location | Istanbul, Turkey | |
| age | ||
| visits | member for | 2 years, 8 months |
| seen | Apr 26 at 23:03 | |
| stats | profile views | 127 |
|
Apr 20 |
comment |
When to stop inheritance? @Benedict It is a solution ok but it is kind of tricky solution. There are bunch of rules that we can handle in this way but it will reduce clarity of code. |
|
Apr 20 |
comment |
When to stop inheritance? @GaryBuyn Color of piece completely affects it is behaviours. White pawns go to upside of board and black pawn go to downside. White pieces can not leave their king in check, white castle moves differ from black's...etc |
|
Apr 18 |
revised |
When to stop inheritance? added 274 characters in body |
|
Apr 18 |
comment |
When to stop inheritance? @gnat I agree with you |
|
Apr 18 |
comment |
When to stop inheritance? It may not purpose to write chess engine too faster. |
|
Apr 18 |
comment |
When to stop inheritance? @Blrfl You are right. Changing Color property name to direction does not change usage in the project. |
|
Apr 18 |
comment |
When to stop inheritance? you are wrong actualy and this is just your guess about implementation details. White pawn and black pawn moves to different directions. But it is not right for White queen and black Queen or any other pieces. This is only happen for pawns. But it is just implementation details. |
|
Apr 18 |
revised |
When to stop inheritance? deleted 39 characters in body |
|
Apr 18 |
comment |
When to stop inheritance? Good point. You have been thought that using spesific colored classes will cause another if statements in somewhere. In that case you are right that design would be wrong. But we can not know this at first without going into implementation so i understand that you would start to design by keeping color property. But if using spesific colored classes does not cause such as if statements in somewhere of project? Would be better choice to inherit ? |
|
Apr 18 |
comment |
When to stop inheritance? I have a little abstracted some of stuffs so you can just concentrate on this simplified example. As you can see i havent used any parameter. It is just prototyping classes and hieararchy. |
|
Apr 18 |
asked | When to stop inheritance? |
|
Feb 29 |
asked | Type mocking frameworks does not change coding practices from testability point? |
|
Jan 24 |
revised |
Question on design of current pagination implementations added 244 characters in body |
|
Oct 20 |
awarded | Nice Question |
|
Sep 27 |
awarded | Yearling |
|
Jun 12 |
comment |
Question on design of current pagination implementations I just wanted to know that is there something wrong about my ideas . Did i break some core principles if not so why all of them followed same design on their implementations .. i don't get it |
|
Jun 12 |
comment |
Question on design of current pagination implementations ASP.NET MVC has no built in pagination helpers just there are third party pagination implementations. |
|
Jun 12 |
revised |
Question on design of current pagination implementations edited body |
|
Jun 12 |
asked | Question on design of current pagination implementations |
|
Jun 7 |
comment |
Power failure should be considered as a scenario to implement? @Matt Ellen - yes, i mean that |
