Company technological stack - Revision history

Root at 19:33, 20 October 2025

2025-10-20T19:33:23Z

← Older revision		Revision as of 20:33, 20 October 2025
Line 1:		Line 1:
	We must be able to understand and provide the benefits and risks of implanting needed technological solutions.		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.		Ensure project is able to be technologically self managed. Offer supervision, not control.<span id="not-only-software"></span>

	<span id="not-only-software"></span>
	== Not only software ==		== 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<br />		Managing technological part of the company is not only about coding, but tactical and operative parts as helpdesk, workplace, HR software, ERP, etc<br />On the strategical part how a technology can help create new products or making company grow and scale.<span id="development-technological-stack"></span>
	On the strategical part how a technology can help create new products or making company grow and scale.

	<span id="development-technological-stack"></span>
	== Development technological stack ==		== Development technological stack ==

Line 16:		Line 11:
	* 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.		* 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.		* 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 [https://www.crunchydata.com/ <u>Crunchy</u>] for PosgreSQL		* Operators are tools provided by the same software provider to ease the management of their own product. For example [https://www.crunchydata.com/ <u>Crunchy</u>] for PosgreSQL<span id="code-versioning"></span>

	<span id="code-versioning"></span>
	== Code versioning ==		== Code versioning ==

Line 24:		Line 17:

	* github		* github
	* bitbucket		* bitbucket<span id="work-methodology"></span>

	<span id="work-methodology"></span>
	== Work methodology ==		== Work methodology ==

	* Jira		* Jira
	* Trello		* Trello<span id="services"></span>

	<span id="services"></span>
	== Services ==		== Services ==

Line 41:		Line 30:
	* pulumi		* pulumi
	* states machine		* states machine
	* N8N		* N8N<span id="documentation"></span>

	<span id="documentation"></span>
	== Documentation ==		== Documentation ==

Line 51:		Line 38:
	* Notion		* Notion
	* Mediawiki		* Mediawiki
	~~<!-- From bodyContent 1543081.mraw -->~~

	[[Category:IT scalability]]		[[Category:IT scalability]]

Maintenance script: Added category IT scalability

2025-10-19T17:51:22Z

Added category IT scalability

← Older revision		Revision as of 18:51, 19 October 2025
Line 53:		Line 53:
	<!-- From bodyContent 1543081.mraw -->		<!-- From bodyContent 1543081.mraw -->

			[[Category:IT scalability]]

Maintenance script: Maintenance script moved page UserDocumentation:Knowledge Central/KC IT/IT scalability/company technological stack to Company technological stack: Cleaned title and categorized

2025-10-19T17:51:22Z

Maintenance script moved page UserDocumentation:Knowledge Central/KC IT/IT scalability/company technological stack to Company technological stack: Cleaned title and categorized

← Older revision	Revision as of 18:51, 19 October 2025
(No difference)

imported>Unknown user at 09:35, 19 April 2025

2025-04-19T09:35:59Z

← Older revision		Revision as of 10:35, 19 April 2025
Line 1:		Line 1:
			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.

			<span id="not-only-software"></span>
			== 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<br />
			On the strategical part how a technology can help create new products or making company grow and scale.

			<span id="development-technological-stack"></span>
			== 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 [https://www.crunchydata.com/ <u>Crunchy</u>] for PosgreSQL

			<span id="code-versioning"></span>
			== Code versioning ==

			we must have a repository for versioning our code.

			* github
			* bitbucket

			<span id="work-methodology"></span>
			== Work methodology ==

			* Jira
			* Trello

			<span id="services"></span>
			== Services ==

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

			<span id="documentation"></span>
			== Documentation ==

			It is very important to keep documentation

			* Confluence
			* Notion
			* Mediawiki
	<!-- From bodyContent 1543081.mraw -->		<!-- From bodyContent 1543081.mraw -->

imported>Unknown user at 09:35, 19 April 2025

2025-04-19T09:35:59Z

← Older revision	Revision as of 10:35, 19 April 2025
(No difference)

imported>Unknown user at 09:35, 19 April 2025

2025-04-19T09:35:59Z

New page