DEV Community: Rachit Sharma

I Built Two Python Libraries to Fix Everyday Developer Frustrations

Rachit Sharma — Sun, 25 May 2025 06:42:21 +0000

Ever wished Windows had a built-in terminal-based text editor?

Or found yourself Googling “100 km/h in m/s” again mid-code?

I felt that pain too — so I built something about it.

Meet pytedit and unitmaster, two lightweight Python libraries designed to solve annoying little developer problems we often overlook but deal with daily.

🔧 pytedit: A Terminal Text Editor for Windows and Beyond

pytedit is a cross-platform terminal-based text editor that just works.

Windows users (like myself) don’t get native terminal editors like Vim or Nano out of the box. So pytedit fills that gap — clean UI, keyboard-friendly, and zero dependencies outside Python.

pip install pytedit

📐 unitmaster: A Dev-Focused Unit Conversion Library

We’ve all written quick one-liners or hit up Google to convert things like:

Fahrenheit to Celsius

km/h to m/s

bytes to megabytes

unitmaster puts all that inside Python with zero distractions. Just import and convert — no mental context switch.

pip install unitmaster

🌦 How I’m Using These in My Upcoming Weather Dashboard

One of my current projects is a terminal-based weather dashboard, and unitmaster is already powering all the conversions — temperature, windspeed, pressure — right in the terminal. The dashboard itself will be released later this week.

🔗 Wheel Downloads

pytedit.whl

unitmaster.whl

🌍 A Small Global Contribution to Open Source

These might seem like small tools, but I genuinely believe they reduce friction in the dev loop. That’s why I’m proud to call them my global contribution to the open-source Python ecosystem.

Made with care by me, along with two of my close friends who contributed throughout development.

If you find these tools useful, please consider giving them a star on GitHub or just spreading the word. Feedback and ideas are always welcome!

More coming soon. 🛠️

Mastering the Art of Code Reviews: A Guide for Developers at Every Level

Rachit Sharma — Sun, 18 May 2025 09:58:09 +0000

Code reviews are more than bug hunts—they're how teams grow, collaborate, and ship better software.

🧭 Why Code Reviews Matter

Whether you're a junior dev submitting your first pull request or a senior reviewing architecture changes, code reviews are one of the highest-leverage activities in a software team.

Done right, they:

Improve code quality
Spread knowledge
Catch bugs early
Align team practices
Foster collaboration and mentorship

But done wrong? They cause delays, miscommunication, and unnecessary friction.

Let’s break down how to make your code reviews effective, respectful, and impactful.

🔍 As a Reviewer: What to Look For

Before you comment on variable naming, zoom out. Focus on these layers:

1. Correctness

Does the code do what it's supposed to?
Are edge cases handled?
Does it break any existing functionality?

2. Readability

Can someone new to the codebase understand this?
Are names, functions, and logic intuitive?
Is it unnecessarily complex?

3. Performance & Scalability

Are there any obvious inefficiencies?
Will this scale if input grows or usage spikes?

4. Security & Validation

Are inputs sanitized?
Are sensitive operations or data properly protected?

5. Consistency

Does it follow team or project conventions?
Is it consistent with existing architecture and patterns?

🧠 As a Submitter: Make Reviewing Easy

Code reviews aren't just for others—they reflect your thinking too.

✅ Tips for great pull requests:

Break large changes into small, logical chunks.
Write a clear PR description. Explain what you did and why.
Link related tickets or discussions.
Test your changes and mention what was tested (manually, unit tests, etc.).
Be open to feedback. Code is not identity—feedback is collaboration, not criticism.

🤝 Review Culture: Keep It Respectful, Keep It Constructive

A great review isn't just about what's wrong—it’s about how to improve.

Instead of:

“This is wrong. Use a different method.”

Try:

“Have you considered using dict.get() here to avoid a KeyError? Might make the logic a bit safer.”

Always default to empathy. We’re all learning.

🛠️ Tools to Help

Linting & Formatting: Tools like Prettier, Black, ESLint automate low-value comments.
CI Tests: Automate regression checks so reviewers focus on logic.
Review Templates: Use GitHub PR templates to structure the information.

🎯 The Goal: Shared Understanding, Better Software

A codebase is a shared language. Reviews are the conversations that shape it.

Code reviews aren't just about code—they’re about people. When done well, they create a culture of trust, growth, and continuous improvement.

💬 What’s the best (or worst) code review feedback you’ve ever received? Share your stories and tips below!

Hello DEV Community 👋

Rachit Sharma — Sat, 17 May 2025 04:17:00 +0000

Hey there, fellow devs!

I’m Rachit, a Python-obsessed engineer who likes building intelligent tools that do more than just show to-do lists and toast messages.

I recently joined DEV to share my journey, projects, and ideas — and connect with folks who enjoy building things that solve actual problems (with a little sarcasm on the side).

🧠 What I Do

🧰 I build modular AI assistants that talk back — literally. My project JargonAI is a sarcastic butler AI that can control systems and Android devices.
💰 I’m also making a beautiful expense tracker using Flet.
🕵️‍♂️ Currently working on a Scam & Phishing Detector using ML.
🧪 On the side, I’ve dabbled in game dev with Pygame, AI + YARA antivirus, and ML-powered fake review detection.

🛠 Tech Stack

Languages: Python (favorite), JavaScript (basic)
Tools: Flet, Pygame, Scikit-learn, Git
Concepts: AI Agents, System Control, ML, OOP

🔭 What’s Next?

I plan to explore:

Reinforcement Learning – because what’s better than training an agent to make bad decisions before it learns not to?
More work on open-source tools that think (or at least pretend to).

Let’s Connect!

💻 GitHub
🌐 Portfolio
🧠 LinkedIn

If you’re into AI, Python, or building tools that bite back — hit follow, drop a comment, or just say hi!

“Adaptability and consistency are my strengths. Ignorance is a bug — and I’m debugging it every day.”