Do thin fluent builder method chains have any need to be “extensible”?
In an environment where refactoring is difficult extensibility can be a life saver. However, this is no excuse to over engineer code.
Do thin fluent builder method chains have any need to be “extensible”?
In an environment where refactoring is difficult extensibility can be a life saver. However, this is no excuse to over engineer code.
Making an MVC app extensible for multiple business markets
Suppose you are to create a single, global e-commerce application to support multiple markets in different regions of the world using ASP.NET MVC.
Making an MVC app extensible for multiple business markets
Suppose you are to create a single, global e-commerce application to support multiple markets in different regions of the world using ASP.NET MVC.
Extending a class for debugging: public API, hidden implementation or something else?
I’m working on a fairly large project that involves 3D drawing, and I want to add some visualizers (for example, to see the bounding boxes of the objects) to make debugging easier. However, I’m having a problem in deciding how to go about this.
Architecture – 3D Modeling Library
I’m writing a library to allow users to generate 3D models programatically.
Should I represent physical accessories of a system as classes in software?
I am redesigning a system comprised of a data-acquisition unit and a lot of different sensors (voltage sensor, angle sensor, pressure sensor, etc.).
Should I represent physical accessories of a system as classes in software?
I am redesigning a system comprised of a data-acquisition unit and a lot of different sensors (voltage sensor, angle sensor, pressure sensor, etc.).
Should I represent physical accessories of a system as classes in software?
I am redesigning a system comprised of a data-acquisition unit and a lot of different sensors (voltage sensor, angle sensor, pressure sensor, etc.).
Should I represent physical accessories of a system as classes in software?
I am redesigning a system comprised of a data-acquisition unit and a lot of different sensors (voltage sensor, angle sensor, pressure sensor, etc.).