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

Windows Docker Containers can make WIN32 API calls, use COM and ASP.NET WebForms

After the last post , I received two interesting questions related to Docker and Windows. People were interested if we do Win32 API calls from a Docker container and if there is support for COM. WIN32 Support To test calls to WIN32 API, let’s try to populate SYSTEM_INFO class. [StructLayout(LayoutKind.Sequential)] public struct SYSTEM_INFO { public uint dwOemId; public uint dwPageSize; public uint lpMinimumApplicationAddress; public uint lpMaximumApplicationAddress; public uint dwActiveProcessorMask; public uint dwNumberOfProcessors; public uint dwProcessorType; public uint dwAllocationGranularity; public uint dwProcessorLevel; public uint dwProcessorRevision; } ... [DllImport("kernel32")] static extern void GetSystemInfo(ref SYSTEM_INFO pSI); ... SYSTEM_INFO pSI = new SYSTEM_INFO(

Azure AD and AWS Cognito side-by-side

In the last few weeks, I was involved in multiple opportunities on Microsoft Azure and Amazon, where we had to analyse AWS Cognito, Azure AD and other solutions that are available on the market. I decided to consolidate in one post all features and differences that I identified for both of them that we should need to take into account. Take into account that Azure AD is an identity and access management services well integrated with Microsoft stack. In comparison, AWS Cognito is just a user sign-up, sign-in and access control and nothing more. The focus is not on the main features, is more on small things that can make a difference when you want to decide where we want to store and manage our users.  This information might be useful in the future when we need to decide where we want to keep and manage our users.  Feature Azure AD (B2C, B2C) AWS Cognito Access token lifetime Default 1h – the value is configurable 1h – cannot be modified

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.51 EF 6.0.2 VS2013 It see