Posts

Showing posts from July, 2024

User Stories

  User story is one of the most important tool to think customer backwards. When we decide to build a software solution, it is because the users will be able to do something in future that they are not able to do today. So it is important for the development teams to keep in mind these needs while building the solution. A user story is a very short description of a very specific thing that users need.   “Good story conversations are about who and why, not just what”. Think about any story in general. Any story is incomplete without knowing who the characters are and what is the motivation behind their actions - it can be revenge, love, ambition. Similarly a user STORY is incomplete without knowing the exact person whose needs we are trying to fulfil and why it is their need.   “User stories are not the written form of requirements…The real goal of using stories is shared understanding.” This is the most common mistake most of us make – treating stories as requirements. Ho...

Representation Learning

  In machine learning, the way we represent the data can have a big impact on how well the models perform. Representation   refers to the relevant information that describe the problem you're trying to solve. For example, if you want to predict the price of an apartment, the relevant information might include the size of the apartment, its location, the amenities available, and the floor it's on. In machine learning, we call these relevant pieces of information " features ." You can think of representation like an Excel spreadsheet, where each column represents a feature (e.g., size, location, etc.), and each row represents a different apartment with values for those features. The job of the machine learning algorithm is to learn how these features are related to the desired output (in this case, the price of the apartment). Sometimes, it's easy to identify the relevant features for a problem. But in many cases, it's challenging to know which features are impo...