Skip to main content

What is a good design?

By
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

Post a Comment

Popular posts from this blog

How to audit an Azure Cosmos DB

By
In this post, we will talk about how we can audit an Azure Cosmos DB database. Before jumping into the problem let us define the business requirement: As an Administrator I want to be able to audit all changes that were done to specific collection inside my Azure Cosmos DB. The requirement is simple, but can be a little tricky to implement fully. First of all when you are using Azure Cosmos DB or any other storage solution there are 99% odds that you’ll have more than one system that writes data to it. This means that you have or not have control on the systems that are doing any create/update/delete operations. Solution 1: Diagnostic Logs Cosmos DB allows us activate diagnostics logs and stream the output a storage account for achieving to other systems like Event Hub or Log Analytics. This would allow us to have information related to who, when, what, response code and how the access operation to our Cosmos DB was done. Beside this there is a field that specifies what was th...
Post a Comment
Read more

Why Database Modernization Matters for AI

By
  When companies transition to the cloud, they typically begin with applications and virtual machines, which is often the easier part of the process. The actual complexity arises later when databases are moved. To save time and effort, cloud adoption is more of a cloud migration in an IaaS manner, fulfilling current, but not future needs. Even organisations that are already in the cloud find that their databases, although “migrated,” are not genuinely modernised. This disparity becomes particularly evident when they begin to explore AI technologies. Understanding Modernisation Beyond Migration Database modernisation is distinct from merely relocating an outdated database to Azure. It's about making your data layer ready for future needs, like automation, real-time analytics, and AI capabilities. AI needs high throughput, which can be achieved using native DB cloud capabilities. When your database runs in a traditional setup (even hosted in the cloud), in that case, you will enc...
Post a Comment
Read more

Azure Service Bus - How to extend the lock of a message | RenewLock

By
In this post we will discuss about Azure Service Bus Topics and Queues, with a special focus on Peek and Lock feature. Introduction Azure Service Bus is a messaging system that allows us to send messages between different systems in a reliable and easy way. A lot of concepts from ESB are implemented by Service Bus, allowing us to do do magic stuff with messages. There are two ways to consume messages from Service Bus Peek and Lock - locks a message for a specific time internal and notify Service Bus when we want to mark the message as processed (removed from Service Bus) Receive and Delete  - once a message is received from Service Bus, it is also deleted automatically from the messaging system Peek and Lock When using Peek and Lock, by default we lock the message for 60 seconds. This means that in this time interval the message is not available/visible for other consumers. Once we process the message we can mark it as processed. If we don't mark the message as processe...
Post a Comment
Read more