Skip to content

Manjarink/Daily-Code-Practice

Β 
Β 

Folders and files

NameName
Last commit message
Last commit date

Latest commit

Β 

History

7 Commits
Β 
Β 

Repository files navigation

πŸš€ WTC Coding Practice Repository

Welcome to the WTC Coding Practice Repository.
This repository is a collaborative workspace where the WTC team solves programming problems, strengthens problem-solving skills, and builds a strong personal and team coding brand through consistent GitHub contributions.


🎯 Purpose of This Repository

  • Practice and master Data Structures & Algorithms
  • Develop logical thinking and coding discipline
  • Build a professional GitHub profile for each team member
  • Maintain clean code and standard conventions
  • Track individual and team progress transparently

πŸ‘₯ Who Can Contribute?

This repository is intended only for WTC team members.
Every contributor is expected to:

  • Solve assigned programming questions
  • Push solutions regularly
  • Follow the repository standards strictly

πŸ“ File Naming Convention (Strictly Mandatory)

Each solution file must follow the naming format below:

Name_Question_q.No.extension

βœ… Correct Examples

Divyansh_TwoSum_q1.py
Aarav_ReverseArray_q12.cpp
Sneha_BinarySearch_q7.java

❌ Incorrect Examples

q1.py
solution.cpp
TwoSum.java

Rules:

  • Name β†’ Your name (use the same format every time)
  • Question β†’ Short and meaningful problem name
  • q.No. β†’ Question number as per the shared list

🧠 Problem Source

All problems will be taken from the official question list shared with the WTC team
(e.g., Top 100 DSA sheet, daily practice sheet, or curated problem sets).

Make sure:

  • You solve the correct question number
  • Your solution matches the problem statement
  • No copied or plagiarized code is pushed

πŸ› οΈ Allowed Programming Languages

You may use:

  • C / C++
  • Java
  • Python
  • JavaScript

Choose your preferred language, but ensure:

  • Readable code
  • Proper formatting
  • Meaningful variable names

πŸ“Œ Contribution Guidelines

  1. Clone or fork the repository (as instructed)
  2. Add your solution file following the naming convention
  3. Write clean and well-structured code
  4. Push your changes to the repository
  5. Update the progress tracking sheet after every submission

πŸ“Š Progress Tracking

Each contributor must update the shared tracking sheet with:

  • Name
  • Question number solved
  • Programming language used
  • Date of submission

This helps maintain accountability and transparency.


πŸ† Building the WTC Brand

This repository represents the technical identity of WTC.
Your contributions should reflect:

  • Consistency
  • Professionalism
  • Strong coding fundamentals

Code as if a recruiter or senior engineer is reviewing it.


πŸ“¬ Support

For any doubts related to:

  • Problem statements
  • Contribution rules
  • File naming conventions

Please contact the WTC core team.


πŸ”₯ Code Daily. Improve Constantly. Build Your Brand.

Happy Coding! πŸš€

About

No description, website, or topics provided.

Resources

Stars

Watchers

Forks

Releases

No releases published

Packages

 
 
 

Contributors