Company technological stack

We must be able to understand and provide the benefits and risks of implanting needed technological solutions.

Ensure project is able to be technologically self managed. Offer supervision, not control.

Not only software

Managing technological part of the company is not only about coding, but tactical and operative parts as helpdesk, workplace, HR software, ERP, etc
On the strategical part how a technology can help create new products or making company grow and scale.

Development technological stack

• Technological stack may vary depending on the knowledge of the team
• When deciding to implement a technology it is necessary to know the resource availability on the market. We can evaluate the costs of each technology or which bootcamps are more demanded.
• We must keep our technological stack as homogenic as possible. If we use multiple technologies it will be more difficult to handle shared knowledge or teams interoperability.
• LowCode and NoCoding is a valid tool for easing development.
• Operators are tools provided by the same software provider to ease the management of their own product. For example Crunchy for PosgreSQL

Code versioning

we must have a repository for versioning our code.

• github
• bitbucket

Work methodology

• Jira
• Trello

Services

• supabase
• autoadmin
• roadmunk
• amplitude
• pulumi
• states machine
• N8N

Documentation

It is very important to keep documentation

• Confluence
• Notion
• Mediawiki