Scribd
Upload
13 views10 pages

Troo Tech Presentation

Uploaded by

Udoh Godswill
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
13 views10 pages

Troo Tech Presentation

Uploaded by

Udoh Godswill
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
You are on page 1/ 10

Development

Process &
Culture
By: Olushola Albert
Overview
Introduction 01
The Goal 02
Methodologies 03
Tools 04
Technology Standards 05
Best Practices 06
Introduction
Our culture are the set of values and systems that define how we
perceive and interact with the market we are playing at and most
importantantly, how we interact with each other in the organization.
This also trickles down to every dept in the company including the IT
team.
The Goal
The best team culture are the ones that reflect the behaviour and
beliefs of the initial members of the team .
The goal of this exercise is to discuss our experiences, personal
development standards, brainstorm and agree on best tools,
practices to adopt as a company so that continuity is guaranteed.
Methodologies

Agile Scrum Prototype


The agile approach is very flexible because Just like agile, scrum also adopts the sprint model but it Protoype methodoly involves building a finished product
development only reflects end users' needs and usually involves breaking down the entire dev team into prototype instead of full scale build, showing it to the
requirements. The application is broken down into groups. Each group consists of a scrum master and the client to get market feedback and requirement before
components(not necessarily features, i.e. that would be developers working on a common goal. full-scale development. This approach works for both
Feature Driven Development) that can be achieved in features and the whole product.
one to four weeks.

Key Notes Key Notes Key Notes


The model is usually iterative which means we This model allows different group to focus on This method allows us to identify issues and market
consider market feedbacks and work on them different part of the project. There could be a group needs early in the development process
almost immediately which is a good thing for the focused on till and another group focused on KDS. Also, real development work does not start until the
business. For a startup like us, the dev team gets to This model is very responsive to emerging changes customer is satisfied with the prototype and that will
handle support as well. as turn out on feedbacks is faster. save us time and money.
Developers are stretched on tasks and usually does This approach also works best with highly skilled Prototyping could sometime take a lot of time
not mean the feature is achieved. members and maybe external consultants.
Alot of development progress is not documented It is a more feature driven approach.
because of time constraint
Dev team might have to deal with a lot of scope
creep base on feedbacks
Tools

Development Dev Operations

Visual Studio Code Postman GitHub actions


Git & GitHub AWS Elastic Beanstalk Ansible
Docker AWS EC2 Elastic IP
AWS RDS Systemctl &
Amazon Q
AWS Route 53 Supervisorctl
BlackBox / Github Copilot
Sentry
Chat GPT AWS Cloudwatch
DBeaver AWS SNS
DBdiagriam Sendgrid
iTerm Twilio
Mock API AWS CLI
Locust AWS S3
Linters Vim
Nano
Linux
Technology Standards

Backend Web Mobile

Language Language Language


Python Javascript /Typescript Javascript
Javascript /Typescript
Framework Framework
Framework React React Native.
Django
DRF Noteable Mentions
Flask 1. Next JS
CLI or Expo ?
NodeJS 2. Rsuite
Express 3. Material UI
4. Bootstrap
Database
PostgreSQL
MongoDB
MySQL

Notable Mentions
Nest JS
Adonis
Best Practices

1. DRY: Don’t Repeat Yourself. You should always avoid knowledge duplication. Avoid logic
duplication. A component or function can be reused instead of rewriting.
2. Don’t write code you don’t need right now. Even if it may come in handy in the future, leave
it for the future.
3. Always use version control
4. Try as much as possible to write test cases
5. Design your logic before coding
6. Code Reviews
7. https://github.com/eHealthAfrica/lomis-suite/blob/develop/CONTRIBUTING.md
Resources

https://github.com/caramelomartins/awesome-linters
THANK YOU!

You might also like