Tech team docs

# Start here

# Introduction

The purpose of this knowledge site is two fold:

  1. To introduce a common set of standards to be followed by everyone writing code as part of the tech team at no-more.
  2. To help new developers getting up speed faster

The site contains three overall sections:

  • This Read Me section, which aims as introducing the required background and all the details required to realize the two-fold purpose
  • A checklist section which aims to be a fast way to revisit the most essential processes
  • A detailed presentation of all the repositories and some of the essential business concepts

# Background

Its important to stress that this site is written roughly three years after the first code was written on the code based (repo: knowmore).

When the first code was written many of the best practices were not implemented (and in most cases unknown to the team).

Thus, do not expect that all code across the repositories are 100% compliant with these practices. This fact should not encourage deviations from the norm – but instead provide a chance " clean up" when you come across such code.

# The tech team's role

The tech team's role in SlideHub is to continuously add value to following stakeholders:

  • Customers/Requesters (sending us PowerPoint projects to deliver & use the PowerPoint tools)
  • Customer account owners / managers (usage, team setting, user roles, billing etc)
  • Specialists (conducting the PowerPoint projects)
  • Internal Project Managers (your colleagues who manages customer expectations and conducting quality assurance of projects)
  • Administration (reporting, documentation, accounting etc)
  • Customer success and sales (bring in new clients and help clients use the service in the best way)

The software we have built create the infrastructure that connect these stakeholders. The software aims at either fully automating and/or supporting each of the many steps associated with making the day-to-day processes run as smooth, fast, and flawless as possible.

Furthermore, the recently developed "library" software provides an additional revenue source to the company that is enabled by the initial service offering.

On a very high level we do this by:

  • Creating new features
  • Improving existing features
  • Fixing bugs, and
  • Keeping the systems running 24/7

In order to be relevant and justify our salaries we need to make a significant impact across these areas every week.

# The role of the analytics team

Recently (late 2020) we have established a small team (Lasse) who execute various analytics initiatives. This is done via a combination of the following low-code tools:

  • Amazon Redshift (data warehouse)
  • Hevo.io (data load and transform)
  • Redash (graphs and reports)

As a result, we aim to minimize analytics work conducted by the tech team and instead focus on building features for the different stakeholders

Principles →