Tarun Balaji V
👋 Hi, I'm Tarun Balaji Vuppalapati(tarunbvj8)
🧠 About Me
I'm a passionate Computer Science undergrad who enjoys solving real-world problems with technology. With strong interests in AI, cybersecurity, and blockchain, I aspire to become a Machine Learning Engineer who creates impactful and ethical AI systems. I'm enthusiastic about learning new technologies, building scalable systems, and contributing to open-source communities.
💻 Tech Skills
Languages & Tools:
- Languages: C, C++, Java, JavaScript, Python (TensorFlow, PyTorch)
- Frontend: HTML, CSS, React.js, Next.js
- Backend: Node.js, Spring Boot
- Databases: MongoDB, SQL
- Other Tools: Docker, Git, OpenFlow, VS Code, Linux, Windows
Planning to Learn:
- Cloud Platforms (AWS/GCP)
- DevOps Tools (Kubernetes, Jenkins)
- Advanced Distributed Systems
- Cybersecurity Tools
🚀 Projects
🔐 Cryptanalytics – AI-Assisted Cryptanalysis Playground
July 2025
- Developed an educational cryptanalysis platform to learn and break classical ciphers.
- Features Caesar, Vigenère, and Substitution cipher tools with AI-guided hints.
- Integrated frequency analysis, Kasiski examination, and real-time feedback from an AI mentor.
- Built with Streamlit for an interactive and responsive web experience.
Tech Stack: Python, Streamlit, Regex, AI Prompting
Setup:
pip install -r requirements.txt
streamlit run streamlit_app.py
🔍 Educational Value: Learn how cryptographic weaknesses are exploited and gain hands-on experience in cipher-breaking techniques. Ideal for students in cybersecurity and cryptography.
🤖 NoteWise – Hugging Face AI-Powered Study Assistant
July 2025
- Built a smart assistant that transforms PDF/PPT/DOC study materials into intelligent, searchable conversations using RAG.
- Supports multi-subject Q&A (DS, DBMS, OS, ML, CN, etc.) with context-aware answers.
- Includes flashcards, quizzes, personalized study plans, voice input/output, and analytics dashboards.
- Deployable on Hugging Face Spaces using LangChain, Transformers, and Streamlit/Gradio UI.
Features:
- Vector search + document chunking
- Flashcard & quiz generators
- Study progress analytics
- Conversation bookmarking
- Voice Q&A and report export
Tech Stack: Python, LangChain, Hugging Face Transformers, FAISS, Streamlit/Gradio, SQLite
Future Scope: Real-time collaboration, leaderboard challenges, curriculum-based flashcard packs
📜 Certifications
-
✅ Mastered Java Spring Framework 6 with Spring Boot 3 – Udemy (2024) -
✅ JP Morgan Software Engineering Job Simulation – Forage (2024) -
✅ Python and Django Basics – Udemy (2024) -
✅ Machine Learning Specialization by Andrew Ng – Coursera (2025)
🏆 Achievements
-
🥈 Finalist – OctCoder: Code Under the Stars coding contest by Turing Hut -
🥉 2nd Place – Webathon 2.0, ACM & GDSC VNR VJIET 2024 -
🏅 SIP Abacus Regional Prodigy 2015 – Top 3 of 7500+ participants -
💡 Participated in FOSS 2025
📌 Positions of Responsibility
-
✒ ️ Technical Content Writer & Designer – ICTIEEE IASP 2025 - 🧑
💼 Organising Committee Member – ICMACC 2024
🌟 Aspirations
I aspire to become a Machine Learning Engineer specializing in AI-driven cybersecurity and decentralized technologies. I’m driven by the vision of building safe, scalable, and intelligent systems that solve critical global problems.
Thank you for visiting my profile! Let's connect and build something impactful together.
Getting started
To make it easy for you to get started with GitLab, here's a list of recommended next steps.
Already a pro? Just edit this README.md and make it your own. Want to make it easy? Use the template at the bottom!
Add your files
-
Create or upload files -
Add files using the command line or push an existing Git repository with the following command:
cd existing_repo
git remote add origin https://code.swecha.org/tarunbvj8/tarunbvj8.git
git branch -M main
git push -uf origin mainIntegrate with your tools
Collaborate with your team
-
Invite team members and collaborators -
Create a new merge request -
Automatically close issues from merge requests -
Enable merge request approvals -
Set auto-merge
Test and Deploy
Use the built-in continuous integration in GitLab.
-
Get started with GitLab CI/CD -
Analyze your code for known vulnerabilities with Static Application Security Testing (SAST) -
Deploy to Kubernetes, Amazon EC2, or Amazon ECS using Auto Deploy -
Use pull-based deployments for improved Kubernetes management -
Set up protected environments
Editing this README
When you're ready to make this README your own, just edit this file and use the handy template below (or feel free to structure it however you want - this is just a starting point!). Thanks to makeareadme.com for this template.
Suggestions for a good README
Every project is different, so consider which of these sections apply to yours. The sections used in the template are suggestions for most open source projects. Also keep in mind that while a README can be too long and detailed, too long is better than too short. If you think your README is too long, consider utilizing another form of documentation rather than cutting out information.
Name
Choose a self-explaining name for your project.
Description
Let people know what your project can do specifically. Provide context and add a link to any reference visitors might be unfamiliar with. A list of Features or a Background subsection can also be added here. If there are alternatives to your project, this is a good place to list differentiating factors.
Badges
On some READMEs, you may see small images that convey metadata, such as whether or not all the tests are passing for the project. You can use Shields to add some to your README. Many services also have instructions for adding a badge.
Visuals
Depending on what you are making, it can be a good idea to include screenshots or even a video (you'll frequently see GIFs rather than actual videos). Tools like ttygif can help, but check out Asciinema for a more sophisticated method.
Installation
Within a particular ecosystem, there may be a common way of installing things, such as using Yarn, NuGet, or Homebrew. However, consider the possibility that whoever is reading your README is a novice and would like more guidance. Listing specific steps helps remove ambiguity and gets people to using your project as quickly as possible. If it only runs in a specific context like a particular programming language version or operating system or has dependencies that have to be installed manually, also add a Requirements subsection.
Usage
Use examples liberally, and show the expected output if you can. It's helpful to have inline the smallest example of usage that you can demonstrate, while providing links to more sophisticated examples if they are too long to reasonably include in the README.
Support
Tell people where they can go to for help. It can be any combination of an issue tracker, a chat room, an email address, etc.
Roadmap
If you have ideas for releases in the future, it is a good idea to list them in the README.
Contributing
State if you are open to contributions and what your requirements are for accepting them.
For people who want to make changes to your project, it's helpful to have some documentation on how to get started. Perhaps there is a script that they should run or some environment variables that they need to set. Make these steps explicit. These instructions could also be useful to your future self.
You can also document commands to lint the code or run tests. These steps help to ensure high code quality and reduce the likelihood that the changes inadvertently break something. Having instructions for running tests is especially helpful if it requires external setup, such as starting a Selenium server for testing in a browser.
Authors and acknowledgment
Show your appreciation to those who have contributed to the project.
License
For open source projects, say how it is licensed.
Project status
If you have run out of energy or time for your project, put a note at the top of the README saying that development has slowed down or stopped completely. Someone may choose to fork your project or volunteer to step in as a maintainer or owner, allowing your project to keep going. You can also make an explicit request for maintainers.