---
# System prepended metadata

title: IDEAS for Dev Presentation for CC Team

---

# IDEAS for Dev Presentation for CC Team

- **What we do?** - Quick and simple explanation of different code layers – e.g. html responsible for structure of the page, css for styling of elements, js – functionalities, php – server actions. Something like that may be helpful to have better understanding of next things we will talk about.

- **How we work?** - how repo works – branches, pull requests, code reviews, why template separation would be beneficial, working with vbulletin etc. 

- **Task estimation problems** – usual blockers, what information we need to estimate task right, what problems we can face.

- **Why refactoring matters?** - small idea – Comparison of work on a website to a kitchen work in a restaurant. At the beginning, all chefs are faced with the question of whether to cook something quickly or make many portions to spare and take care of the organization of the kitchen and cleaning. After some time, when everyone cooks dishes in small quantities to make it faster, the kitchen becomes very dirty and cooking anything becomes problematic, because first you need to clean up your position and each dish is created from scratch. Sometimes you need to close the kitchen for some time and take care of the elements that will speed up the work.
- **Why we pick and choose what goes to contractors** examples of where things went wrong with contractors and how it impacts 1. They went and did their own thing/site (not follow coding standards), 2. Work on complicated tasks - high risk of getting it wrong as well as needing a lot of support impacting our other tickets we have to do.
