DEV Community: Shaik Bibi Jahera

Still Learning, Still Exploring — And That's Enough

Shaik Bibi Jahera — Mon, 09 Mar 2026 12:54:31 +0000

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

I can read a coding problem and understand it.
I can follow the logic when someone explains it.
But when it's time to open a blank file and write the code myself — I freeze.
That gap, between understanding and doing, is where I've lived for most of my second year.

The Honest Truth About My Lab Sessions

In lab sessions, we're given problems to solve. Most of them are related to what we're studying — but not quite taught. The expectation is that we figure it out.
So I open the problem. I read it. I understand what it's asking.
And then I open AI.
I copy the code. I paste it. I run it. It works.
I feel a small relief — like I finished something.
But I didn't finish something. I just moved past it.
And the next lab session, the same thing happens. And the next. Each time telling myself I'll actually learn it properly later. That "later" kept moving forward without me.

Watching People Like Me Move Ahead

The pressure in my life doesn't come from a classroom where someone talks over me.
It comes from quieter places.
WhatsApp groups. LinkedIn. Program announcements.
Competitive coding contests. Campus programs. Internship selections.
I watch people who seem exactly like me — same year, same starting point, same course — attempt things I haven't attempted. Get selected for things I didn't even apply for.
And I feel it. A small jealousy. Not bitter. Just honest.
Followed immediately by: maybe I need to at least attempt properly. Maybe I need to practice. Maybe next time.
But next time came. And I froze again.
The problem was never that I didn't understand the question.
The problem was that I couldn't convert understanding into code.
And I didn't know how to fix that — so I kept collecting roadmaps instead of solving problems.

The Room Feels Louder Than I Do

I am a second-year Computer Science student at a top private university in South India.
Sometimes I am one of the few girls in spaces where coding is being discussed — online groups, college chats, technical communities.
I want to participate. When I understand something, when I have a doubt, when I think I could attempt an answer — I want to speak.
But then: What if it's wrong? What if it sounds too basic? What if everyone already knows this?
So I stay quiet.
And once you stay quiet once, it becomes easier to stay quiet again.
By the time I gather confidence, the conversation has already moved on.
It's not that I don't belong. I've never felt that.
I've only felt like I need to get better before I show up.
And that waiting — waiting to be ready — was keeping me stuck.

The Call That Changed the Direction

During the Campus Mantri program of GeeksforGeeks, we had a task to connect with an expert through GeeksConnect.
I was nervous — not because I didn't have questions, but because I wanted to ask the right one.
I asked her about DSA. About what to focus on. About how to stop feeling behind.
She didn't give me a strategy or a roadmap.
She said: "Second year is for exploring. Learn DSA. Explore. Don't rush."
It wasn't dramatic advice.
But it felt like permission.
Permission to stop collecting and start doing.
Permission to not have a title yet.
Permission to build slowly — but actually build.
When the call ended, I didn't feel transformed.
I felt calmer.

What Actually Changed

I stopped bookmarking twelve YouTube playlists and jumping between DSA sheets.
I picked one thing — the GFG 60 Day Challenge — and I started.
When I get stuck, I don't just copy anymore. I ask AI to explain the approaches. I read them. I try to understand which one makes sense. Then I attempt it myself.
It's slower. It's messier. Sometimes I still get it wrong.
But I'm 19 days in. Somehow maintaining.
And that "somehow" feels more honest than any clean transformation story I could tell you.
Half knowledge creates anxiety.
Deep knowledge creates confidence.
I'm not there yet. But for the first time I'm actually attempting — not just moving past it.

Still Learning. Still Exploring.

I still freeze sometimes.
I still feel that small jealousy when someone like me moves ahead.
I still have lab sessions where I don't know the answer.
But I'm getting better at sitting with that discomfort instead of scrolling away from it.
I don't need to call myself an engineer yet.
I don't need to compete with LinkedIn headlines or campus leaderboards.
Right now, I just need to become better than yesterday.
Second year isn't for proving.
It's for exploring.
I'm still learning.
Still exploring.
And for the first time — that feels enough.

DevLog CLI - AI-Powered Development Journal Built with GitHub Copilot CLI

Shaik Bibi Jahera — Mon, 16 Feb 2026 07:34:57 +0000

A command-line tool that helps developers track daily work and generate AI summaries from git commits - built with GitHub Copilot CLI for the challenge

🚀 DevLog CLI - AI-Powered Development Journal

Built for the GitHub Copilot CLI Challenge

GitHub Repository: devlog-cli

💡 The Problem I Solved

As a developer, I constantly face this challenge: "What did I work on today?"

Whether it's for daily standups, weekly reports, or personal tracking, I often forget the details of my work. I'd scroll through git commits, check terminal history, and try to piece together what I accomplished. It was frustrating and time-consuming.

I needed a solution that:

Lives in the terminal where I already work
Takes seconds to log my progress
Automatically understands my git activity
Generates summaries for meetings

That's why I built DevLog CLI.

✨ What is DevLog CLI?

DevLog CLI is a command-line development journal that helps you:

📝 Log work instantly - Quick entries without leaving the terminal

👀 View your progress - See today's or this week's accomplishments

🤖 Generate AI summaries - Automatically analyze git commits

📄 Export to markdown - Ready for standups and reports

🎯 Key Features

1. Quick Logging

devlog add "Fixed authentication bug"
devlog add "Implemented user dashboard"

Simple, fast, and doesn't interrupt your flow.

2. Smart Viewing

# See today's work
devlog view

# Review the whole week
devlog view --week

Beautifully formatted output with timestamps and colors.

3. AI-Powered Summaries

devlog summary

This is the star feature! It:

Analyzes your git commits from today
Extracts what you accomplished
Generates a human-readable summary
Saves it to your devlog automatically

4. One-Click Export

devlog export

Exports everything to a markdown file, perfect for:

Daily standup notes
Weekly status reports
Project documentation
Performance reviews

🤖 How GitHub Copilot CLI Transformed My Development

GitHub Copilot CLI wasn't just helpful—it was game-changing. Here's exactly how I used it:

Phase 1: Architecture Design

My Question to Copilot CLI:

"I'm building a CLI tool in Node.js for logging development work. What packages should I use for commands, storage, git integration, and terminal colors?"

Copilot's Response:
It recommended the perfect stack:

commander for CLI framework
conf for local storage
simple-git for git operations
chalk for beautiful terminal output

This saved me hours of research and package comparison!

Phase 2: Storage Implementation

My Prompt:

"Help me implement a log storage system using the conf package that saves entries with timestamps, dates, and messages"

Copilot CLI provided:

Complete implementation code
Best practices for data structure
Error handling suggestions

Result: The storage system worked perfectly on the first try.

Phase 3: Git Integration (The Complex Part)

My Prompt:

"I need to use simple-git to get today's commits, analyze them, and generate a summary. Include error handling for when there are no commits."

This was the most challenging feature, but Copilot CLI:

Explained how to filter commits by date
Showed me async/await patterns
Suggested error handling for edge cases
Provided complete working code

Phase 4: Code Quality & Polish

Throughout development, I used Copilot CLI to:

Refactor repetitive code
Add proper error messages
Improve user experience
Optimize performance

Time Saved: Approximately 4-5 hours that would have been spent reading documentation, debugging, and trial-and-error.

🛠️ Technical Implementation

Tech Stack

Node.js - Runtime environment
Commander.js - CLI framework
Chalk - Terminal styling
Conf - Local data persistence
Simple-git - Git repository integration
GitHub Copilot CLI - Development assistant

Architecture

devlog-cli/
├── commands/
│   ├── add.js       # Log entry creation
│   ├── view.js      # Log viewing & filtering
│   ├── summary.js   # Git analysis & summary
│   └── export.js    # Markdown export
├── index.js         # Main CLI entry point
└── package.json     # Dependencies

Key Technical Decisions

1. Local-First Storage
I chose conf for storage because:

No database setup required
Fast read/write operations
Data stays on user's machine (privacy)
Cross-platform compatibility

2. Git Integration
Using simple-git allowed:

Native git repository detection
Efficient commit filtering by date
No external dependencies

3. Markdown Export
Markdown was perfect because:

Universal format for documentation
Easy to read and share
Compatible with all platforms

🎓 What I Learned

1. The Power of AI-Assisted Development

GitHub Copilot CLI accelerated my development by:

Reducing context-switching (stayed in terminal)
Providing instant expert guidance
Suggesting best practices I wasn't aware of

2. CLI Design Principles

Building a good CLI tool requires:

Clear, predictable commands
Beautiful, colored output
Helpful error messages
Comprehensive help text

3. Developer Experience Matters

The best tools are the ones you actually use. DevLog CLI succeeds because:

It's fast - no UI overhead
It's simple - four intuitive commands
It's integrated - works with your existing workflow

🚀 Try It Yourself!

Installation

git clone https://github.com/jahera-shaik/devlog-cli.git
cd devlog-cli
npm install
npm link

Quick Start

# Add your first log
devlog add "Started using DevLog CLI"

# View it
devlog view

# Get help
devlog --help

🎯 Use Cases

For Daily Standups:

devlog view
devlog export
# Share devlog-export.md with your team

For Weekly Reports:

devlog view --week
devlog export
# Perfect summary for your manager

For Personal Tracking:

# Log as you work throughout the day
devlog add "Fixed bug in payment processing"
devlog add "Reviewed pull requests"
devlog add "Updated API documentation"

# Generate AI summary at end of day
devlog summary

🔮 Future Enhancements

If this project continues, I'd love to add:

[ ] Search functionality - Find specific logs by keyword
[ ] Tags & categories - Organize logs by project or type
[ ] Statistics dashboard - Visualize productivity trends
[ ] GitHub Issues integration - Link logs to issues automatically
[ ] Team features - Share logs with collaborators
[ ] Cloud sync - Optional backup to cloud storage

🏆 Why DevLog CLI Stands Out

1. Solves a Real Problem
Every developer struggles with tracking their work. DevLog CLI makes it effortless.

2. Excellent GitHub Copilot CLI Integration
I didn't just use Copilot CLI—I leveraged it strategically throughout development, saving hours and improving code quality.

3. Production-Ready Quality

Clean, maintainable code
Comprehensive documentation
Professional polish
Ready to use daily

4. Practical Daily Value
This isn't a demo—it's a tool I (and others) will actually use every day.

🙏 Acknowledgments

Huge thanks to:

GitHub for Copilot CLI—it truly transformed how I develop
DEV Community for hosting this incredible challenge
Open Source Community for the amazing libraries used

👨‍💻 About Me

Shaik Bibi Jahera

I'm a passionate developer who loves building tools that make developers' lives easier. This project combines my interest in CLI tools, productivity, and AI-assisted development.

GitHub: @jahera-shaik
DEV.to: @jaherashaik

📝 Conclusion

Building DevLog CLI was an incredible learning experience. GitHub Copilot CLI proved to be more than just a code completion tool—it was a collaborative partner that accelerated development, suggested best practices, and helped me build something I'm truly proud of.

Whether you're preparing for standup, writing status reports, or just want to remember what you accomplished today, DevLog CLI has you covered.

⭐ Try it out and let me know what you think!

git clone https://github.com/jahera-shaik/devlog-cli.git
cd devlog-cli
npm install && npm link
devlog add "Discovered an amazing new CLI tool!"

I Was Scared of Copilot CLI — So I Built a Teacher For It 🤖

Shaik Bibi Jahera — Sun, 15 Feb 2026 12:56:11 +0000

I'll be honest.

GitHub Copilot CLI intimidated me.

The documentation felt technical.
The prompts looked like magic spells.
I didn’t know where to start.

So I did what any developer would do.

I built a tool to teach me — using Copilot CLI itself.

🚀 Introducing Copilot Coach

Copilot Coach is an interactive CLI that teaches GitHub Copilot through real-time feedback, prompt analysis, and personalized workflow suggestions.

Instead of reading documentation, you learn by doing.

It’s a hands-on training system for mastering Copilot CLI.

🎬 100-Second Demo

Watch here:
https://drive.google.com/file/d/1qFKFxj1SIpQqMqv6HSHeMFhqm5yoK4dC/view?usp=sharing

🧠 What Copilot Coach Does

1️⃣ Live Prompt Analyzer

Type any prompt → get instant clarity feedback.

Example:

You type:
fix the bug

Copilot Coach responds:

Clarity Score: 3/10

Issues:

Too vague
No language specified
Missing context

Improved prompt:
Debug this Python error: [paste error] in code: [paste code]

It teaches how to communicate effectively with AI.

2️⃣ Git Workflow Analyzer (⭐ Killer Feature)

Copilot Coach scans your git commit history to understand your coding patterns.

Then it generates personalized Copilot workflows.

Example output:

Profile: Bug Hunter
Languages: Python, JavaScript

Recommended prompts:

Debug error messages faster
Review code for bugs
Add defensive error handling
Generate unit tests

Workflows are exported to:

MY_COPILOT_WORKFLOWS.md

This connects Copilot learning directly to your real projects.

3️⃣ Before vs After Prompt Teaching

Bad prompt:
make function

Good prompt:
Create a Python function that reverses a string

Seeing both instantly teaches better prompting.

4️⃣ AI Cheat Sheet Generator

Copilot Coach generates a reusable guide:

COPILOT_TIPS.md

Includes:

Code generation prompts
Debugging strategies
Refactoring templates
Testing prompts
Documentation helpers

You keep this forever as a Copilot reference.

5️⃣ Guided Mini-Project

The tool walks you through building a CLI Todo app step-by-step.

You learn by doing — not just reading.

🤖 How GitHub Copilot CLI Built This

Every major feature was created using Copilot CLI prompts.

Example prompt:
Create a Python function that analyzes prompts, scores clarity, detects issues, and suggests improvements.

Result:
Working analysis system generated in minutes.

Another prompt:
Analyze git commits and generate personalized workflow suggestions.

Result:
Full git integration logic.

⏱️ Impact of Copilot CLI

Without Copilot: ~8 hours
With Copilot: ~2 hours

Copilot CLI reduced development time by 75%.

🧠 What I Learned

1️⃣ Teaching a tool helps you master it
2️⃣ AI removes boilerplate, not creativity
3️⃣ Personalized guidance beats generic tutorials
4️⃣ Real-time feedback beats static documentation

🔗 Try It Yourself

GitHub repo:
https://github.com/jahera-shaik/copilot-coach

Run locally:

git clone https://github.com/jahera-shaik/copilot-coach
cd copilot-coach
pip install -r requirements.txt
python coach.py

🏆 Built for the GitHub Copilot CLI Challenge

This project demonstrates:

Real Copilot CLI usage in feature development
A practical developer tool
A creative meta concept
Personalized workflow generation from git history

🤖 AI Tools Used (Full Transparency)

Primary Code Generation:

GitHub Copilot CLI (generated all Python code)

Strategic Assistance:

Claude (planning, structure, documentation)

My Contributions:

Conceived the concept
Designed all features
Wrote Copilot prompts
Tested and refined the system

❤️ Final Thought

I started intimidated by Copilot CLI.

I ended up building a teacher for it — using Copilot itself.

If this project helps you learn Copilot better,

⭐ consider starring the repo.

Built by: Bibi Jahera Shaik