Skip to content
View its-spark-dev's full-sized avatar
1 follower · 2 following

Highlights

  • Pro

Organizations

@OSUDSL

Block or report its-spark-dev

Block user

Prevent this user from interacting with your repositories and sending you notifications. Learn more about blocking users.

You must be logged in to block users.

Maximum 250 characters. Please don't include any personal information such as legal names or email addresses. Markdown supported. This note will be visible to only you.
Report abuse

Contact GitHub support about this user’s behavior. Learn more about reporting abuse.

Report abuse
its-spark-dev/README.md

Exploring how software systems behave beyond the textbook 🌱

Computer Science student at The Ohio State University
Building systems, exploring ideas, and growing as a software engineer.

👋 About me

I’m a CS student interested in how software systems are built, scaled, and used in the real world.

Recently, I’ve been working as an undergraduate researcher in a Driving Simulation Lab, where I design and improve Python-based tooling for research workflows. Through this work, I’ve gained hands-on experience with data processing, testing, and performance trade-offs, but I don’t see myself as limited to any single niche.

I’m still exploring, learning, and expanding:
from backend systems and tooling
to performance, infrastructure, and developer-facing software.

🔍 What I’m exploring

  • 🧱 Software engineering fundamentals (data structures, design, testing)
  • ⚙️ Backend and systems-oriented development
  • 📈 Performance, scalability, and real-world trade-offs
  • 🛠 Tooling that helps people work more effectively
  • 🧪 Research-driven and user-centered engineering

(This list is intentionally open-ended.)

🧩 Selected work

  • OSU Driving Simulation Lab – pydre

    • Python tooling for processing large-scale driving simulation data
    • Contributed features, refactors, and test coverage improvements
    • Focus on correctness, maintainability, and practical performance

  • Parallelism Benchmark (pydre)

    • Explored how threading and multiprocessing behave under different workloads
    • Built reproducible benchmarks and analysis pipelines
    • Learned that performance is about trade-offs, not just “more parallelism”

  • CSV vs Parquet Benchmark

    • Investigated how data format choices impact real Python workflows
    • Compared readability, flexibility, and performance trade-offs
    • Used Polars to ground format decisions in measurement rather than assumptions

(More projects live in individual repositories.)

🌐 Beyond code

Outside of engineering, I care a lot about communication and people.

  • 🎨 Adobe Student Ambassador — leading hands-on workshops
  • 📹 Content creator with 13M+ views, explaining ideas to broad audiences
  • 🌍 Experience working across cultures and disciplines

I believe good software is built by people who can think clearly and communicate well.

🚀 Currently

  • 🎓 CS @ OSU (Class of 2027)
  • 🔍 Exploring Software Engineering Internships (Summer 2026)
  • 🛠 Building, learning, and staying curious

Building in progress

Activity Graph

Thanks for stopping by 🙂

Pinned Loading

  1. csv-vs-parquet-benchmark csv-vs-parquet-benchmark Public

    A rigorous benchmark comparing CSV and Parquet file performance using Polars in Python. Evaluates file loading speed, memory efficiency, and runtime profiling under cold and warm cache conditions.

    Python 1

  2. pydre-parallelism-benchmark pydre-parallelism-benchmark Public

    A systematic benchmark evaluating threading and multiprocessing strategies in the pydre analytics pipeline, with a focus on workload-dependent performance and practical default execution strategies.

    Python 1