Technology Sales

Photo by fauxels

Technology sales is the act of connecting customers with technology that can provide a solution to a specific problem or challenge1. Technology can include software, hardware, or services1. Technology salespeople identify consumer needs and show them how their products or services can meet them. They can sell to different types of customers, from individuals to large organizations.

To become a technology salesperson, you need to have some skills and qualifications, such as:

  1. A passion for technology and a willingness to learn about new products and features
  2. A customer-oriented mindset and a knack for building rapport and trust
  3. A strong communication and presentation skills, both verbal and written
  4. A problem-solving and analytical ability, to understand customer pain points and offer solutions
  5. A sales acumen and a drive to achieve sales goals and targets
  6. A teamwork and collaboration skills, to work with other salespeople, engineers, marketers, and support staff

(Software Architect series) Communication in Microservices Architecture

Communication is one of the biggest challenges in Microservice architecture. However, we should try to reduce communication between the microservices. Because it has possibility of failure. It is better to have minimum number of communications between services. Nevertheless, dependencies between services is inevitable. That is why we should carefully determine how the services talk each other, otherwise it can affect each other and results a bad performance.

Photo by Alex Andrews from Pexels
Lanjutkan membaca “(Software Architect series) Communication in Microservices Architecture”

(Software Architect Series) Microservices Architecture

Microservices is an architecture that divides the big system become structured services that run separately and deployed independently. Those services communicate each other in a loosely couple relation. Each service can be in different server and has its own database. But in some cases, the services are located in the same server or even have one same database. However, the service function run and deployed separately.

Photo by Sharon McCutcheon from Pexels

It is different with Monolithic architecture, that all function is run by one big system and can’t deployed separately between functions. And the functions communicate in tight coupling. Consequently, it affects each other densely.

Lanjutkan membaca “(Software Architect Series) Microservices Architecture”

(Java) Design Pattern part 1. What is design pattern?

What is design pattern?

Photo by Porapak Apichodilok from Pexels

Design pattern is a general solutions for common case that happen in the programming world. But, we should adapt with with the actual condition. The Design pattern was initiated by Gang of Four (Erich Gamma, John Vlissides, Ralph Johnson, Richard Helm) in the book titled “Design Patterns: Elements of Reusable Object-Oriented Software”, in 1994.

What is the benefit of design pattern?

Lanjutkan membaca “(Java) Design Pattern part 1. What is design pattern?”

Agile User Story & Task

What is user story in Agile?

User story is a functionality requirement of a system that required by the user. A user story can be defined in two kind of sentences

  • As a <User Role> I want <Functionality> so that <Business Value>
  • In order to <Business value> as a <User Role> I want <Functionality>

Agile Planning

How Agile plan the work?

Agile works in iterations tp deliver user stories which already prioritized on the product backlog, based on the team capacity to decide how much scope they have to plan

Point

A Point defines how much a team can commit. A point usually refers to 8 hours. Each story is estimated in points.

Capacity

Capacity defines how much an individual can commit. Capacity is estimated in hours.

Agile

Agile is a software development methodology which use short iteration process (about 1-4 weeks) to get frequent feedback for aligning business requirement changes.

There are roles in Agile :

Scrum Master
Scrum master is the leader and facilitator who ensures/helps agile process can be implemented well.

Functional Responsibilities :

  1. Lead daily stand up meeting
  2. Held problem solving meeting
  3. Review
  4. Arrange demo

Non functional responsibilites :

  1. Cooperates with all roles and functions to make good connection
  2. Solves problem which comes
  3. Tracks progress

Product Owner

Product Owner is the one who drives the product from business prespectives.

The responsibilities are follows:

  1. Define requirement and priorotize it
  2. To determine release date and content
  3. Represent the voice of customer
  4. Define aceptance criteria
  5. Accept user stories that meet requirement of done

Cross Functional Team

This team consist of developers, testers and technical leader