Skip to main content

What is a good design?

The main scope of this post is to try to define what is a good design of a startup in the software industry. Different characteristics of a good startup will be discussed below.  


What is a good design?
Some people would say that is a UX that can be used by anybody, regardless of age of nationality. Others would say that a good design of a software product give us the ability to extend it, adding new features with a minimal cost.
In my opinion a good design is a design that works. A good design should bring real value, should enable us to make a difference.

What is a startup?
This question could sound silly, but before going forward you should ask yourself “What is a startup?”
The classic definition of a startup is an organization that search for a business model that is scalable and repeatable. In general a startup is in research or development field. If we go further with this definition and try to define “startup” as a noun we will discover that startup means:
The action or process of setting something in motion.
I think that this is the most pure definition of a startup. A startup is an action or thing that changes something around us, makes the world better and improves the quality of our life.
And the final question is:

What is a product?
A product is anything that can be offered to the market. A good that can be sold as a finished product or as a service. It can be physical or virtual. A product can have many forms and prices based on the market needs and maturity.
Like “startup”, the pure definition of a product is:
An article or substance that is manufactured or refined for sale.

Take a look again over the below expression:
Good design of a startup product

Creating a working software product that brings value to people it is one of the most complicated things in the world.

Comments

Popular posts from this blog

How to check in AngularJS if a service was register or not

There are cases when you need to check in a service or a controller was register in AngularJS.
For example a valid use case is when you have the same implementation running on multiple application. In this case, you may want to intercept the HTTP provider and add a custom step there. This step don’t needs to run on all the application, only in the one where the service exist and register.
A solution for this case would be to have a flag in the configuration that specify this. In the core you would have an IF that would check the value of this flag.
Another solution is to check if a specific service was register in AngularJS or not. If the service was register that you would execute your own logic.
To check if a service was register or not in AngularJS container you need to call the ‘has’ method of ‘inhector’. It will return TRUE if the service was register.
if ($injector.has('httpInterceptorService')) { $httpProvider.interceptors.push('httpInterceptorService&#…

ADO.NET provider with invariant name 'System.Data.SqlClient' could not be loaded

Today blog post will be started with the following error when running DB tests on the CI machine:
threw exception: System.InvalidOperationException: The Entity Framework provider type 'System.Data.Entity.SqlServer.SqlProviderServices, EntityFramework.SqlServer' registered in the application config file for the ADO.NET provider with invariant name 'System.Data.SqlClient' could not be loaded. Make sure that the assembly-qualified name is used and that the assembly is available to the running application. See http://go.microsoft.com/fwlink/?LinkId=260882 for more information. at System.Data.Entity.Infrastructure.DependencyResolution.ProviderServicesFactory.GetInstance(String providerTypeName, String providerInvariantName) This error happened only on the Continuous Integration machine. On the devs machines, everything has fine. The classic problem – on my machine it’s working. The CI has the following configuration:

TeamCity.NET 4.51EF 6.0.2VS2013
It seems that there …

Run native .NET application in Docker (.NET Framework 4.6.2)

Scope
The main scope of this post is to see how we can run a legacy application written in .NET Framework in Docker.

Context
First of all, let’s define what is a legacy application in our context. By a legacy application we understand an application that runs .NET Framework 3.5 or higher in a production environment where we don’t have any more the people or documentation that would help us to understand what is happening behind the scene.
In this scenarios, you might want to migrate the current solution from a standard environment to Docker. There are many advantages for such a migration, like:

Continuous DeploymentTestingIsolationSecurity at container levelVersioning ControlEnvironment Standardization
Until now, we didn’t had the possibility to run a .NET application in Docker. With .NET Core, there was support for .NET Core in Docker, but migration from a full .NET framework to .NET Core can be costly and even impossible. Not only because of lack of features, but also because once you…