Forem: Bharath Manepalli

From Barriers to Opportunity: A Glass Ceiling Animation

Bharath Manepalli — Sat, 28 Mar 2026 09:08:23 +0000

This is a submission for the 2026 WeCoded Challenge: Frontend Art

Breaking the Glass Ceiling Through Code

Show us your Art

👉 https://codepen.io/Nani-Hatake/pen/QwKQdZz

Inspiration

This piece represents the idea of breaking invisible barriers in technology and opportunities through visual storytelling.

I wanted to express this concept using only HTML and CSS animations. The glass-like surface represents limitations and barriers that exist in many spaces, while the cracking and falling shards symbolize those barriers being broken over time.

As the glass breaks, the idea of code and opportunity rises upward, representing progress, growth, and equal access to technology. The entire piece is built with simple frontend tools to show that even basic web technologies can be powerful for creative expression.

My Code

👉https://codepen.io/Nani-Hatake/pen/QwKQdZz

Optional Note

This project is built using only HTML and CSS, focusing on animation and visual storytelling

Thanks for the opportunity to participate in this challenge!

From Errors to Experience: My Developer Journey

Bharath Manepalli — Sat, 28 Mar 2026 08:38:13 +0000

This is a submission for the 2026 WeCoded Challenge: Echoes of Experience

Echoes of My Early Developer Journey

I didn’t start with a clear roadmap or a perfect plan. Like many developers, I began by trying things, breaking things, and slowly understanding how systems actually work.

At first, even simple setups felt overwhelming — configuring environments, fixing errors, understanding how backend and frontend connect. But instead of avoiding those challenges, I leaned into them. Every error became a clue, and every fix felt like unlocking a new level.

Learning by Building

Rather than just watching tutorials, I focused on building small, real projects. Recently, I worked on creating an AI-powered bug tracking system that logs errors into a structured workflow. While building it, I faced real issues — API errors, configuration mistakes, and integration problems.

What changed things for me was realizing that these problems are not obstacles — they are the learning process.

The Reality of Growth

Working on practical systems taught me something important: development isn’t about knowing everything. It’s about being able to figure things out step by step.

There were moments where things didn’t work at all — APIs failed, integrations broke, and errors made no sense. But each time I debugged and solved something, my confidence grew.

What This Journey Taught Me

Consistency matters more than perfection
Building teaches more than consuming content
Errors are not failures — they are feedback
Real growth comes from solving real problems

Final Thoughts

This journey is still ongoing, but one thing is clear: progress comes from showing up and building, even when things feel confusing.

If you’re just starting out or feeling stuck, keep going. The confusion you feel today will become the experience you rely on tomorrow.

AI Bug Tracker with Notion MCP

Bharath Manepalli — Sat, 28 Mar 2026 06:35:04 +0000

This is a submission for the Notion MCP Challenge

What I Built

I built an AI-powered Bug Tracker that automates the process of logging and organizing application errors using Notion as a centralized system.

Developers can send error messages through a simple API endpoint, and the system processes them by categorizing each issue (Frontend, Backend, Database, or API) and generating a suggested fix.

Each error is then automatically stored in a structured Notion database with its category, solution, and status. This removes the need for manual tracking and keeps debugging workflows clean and organized.

The goal of this project is to turn raw error messages into structured, actionable data and demonstrate how developer workflows can be automated using Notion as a backend.

Video Demo

Watch how errors are analyzed and automatically logged into Notion 👇

Show us the code

GitHub Repository:

https://github.com/Nani-Hatake/ai-bug-tracker

How I Used Notion MCP

I used Notion as a backend database by integrating it through the Notion API.

Whenever an error is sent to the application, it is processed and stored as a new entry in a Notion database with structured fields like error message, category, suggested fix, and status.

This transforms Notion into a lightweight bug tracking system, enabling a centralized and automated workflow for managing errors efficiently.

Tech Stack

Node.js
Express.js
Notion API
dotenv

Key Features

Automatically logs errors into Notion
Categorizes issues (Frontend, Backend, Database, API)
Stores suggested fixes
Centralized bug tracking system

Future Improvements

Integrate a real LLM for smarter error analysis
Add a frontend UI
Enable status updates (Open → Fixed)
Add search and filtering

Final Thoughts

This project shows how integrating a backend system with Notion can create a simple yet powerful workflow automation tool. It highlights how structured data and automation can significantly improve developer productivity.