DEV Community: VINAYAK GOTE

My First Merged PR in Zalando Logbook: What I Built and What the Review Taught Me

VINAYAK GOTE — Mon, 02 Nov 2026 02:21:15 +0000

In my last post I wrote about why I started open source. This post is about the first PR that got merged for me in a big project: Zalando Logbook.

What is Logbook?

Logbook is a Java library from Zalando that logs HTTP requests and responses. If you work with REST APIs, you know why this matters. When something breaks in production, the first thing you want to see is what request came in and what response went out.

What I worked on

My PR added two things to Logbook:

StatusCodeBasedSink: a sink that makes decisions based on the HTTP status code of the response.
LevelBasedHttpLogWriter: a log writer that uses the status code to pick the log level.

The simple idea behind both: a 200 response and a 500 response should not be treated the same. Errors should stand out, and normal traffic should not fill your logs with noise.

It got merged in May 2026. You can see the full PR, the code and the review here: zalando/logbook #2301

How I approached it

I did not start by writing code. I started by talking to the maintainers on the issue, so I knew what they wanted before I built anything. Then I kept the change small and focused, wrote tests, and signed my commits.

Looking back, that order saved me a lot of pain. Writing code first and asking later is how PRs get stuck.

What the review taught me

Maintainers read very carefully. They do not only check if your code works. They ask:

Does this fit the style of the project?
Will this break anyone who is already using the library?
Is the naming clear for someone who has never seen this code?

Answering those questions made my code better than my first version. Reviews are slow sometimes, but they are free teaching from people who know the codebase far better than I do.

The part I did not expect

After my PR was merged, another contributor found a gap in my own work. The ECS sink did not follow the same status code behavior, so he opened an issue and then a PR to fix it.

My first feeling was a little embarrassing. But then I thought about it properly: this is exactly how open source works. Nobody ships perfect code. So instead of rushing to send a competing PR, I reviewed his one and left comments on the threshold behavior and on the docs checklist. You can read that discussion here: zalando/logbook #2379

That was a good lesson for me: reviewing someone else's PR is also a contribution, and it teaches you how others think.

What I would tell someone starting out

Read the issue and talk to the maintainer first.
Keep your PR small. A small diff gets reviewed faster.
Take every review comment seriously, even when it feels strict.
If someone finds a gap in your work later, treat it as part of the process, not as a failure.

What is next

In the next post I will write about my PR in the Adyen Java API Library, which shipped in SDK v42.0.0, and how it felt to see my change in a real release.

Proof of my work

Everything I write about here is public, so you can check it yourself:

zalando/logbook #2301: StatusCodeBasedSink and LevelBasedHttpLogWriter (merged)
adyen/adyen-java-api-library #1952: shipped in SDK v42.0.0 (merged)
PicnicSupermarket/error-prone-support #2275: merged after review
Sionna Visualizer: my side project, a 6G + AI dashboard (live demo)
My GitHub: all my repos and contributions

If you are a maintainer, a recruiter or a team looking for someone who learns in public and likes to collaborate, my DMs are open. Tell me in the comments if you work with Logbook or want to contribute to it, I am happy to share what I learned.

Why I Started Contributing to Open Source (and What Happened in the First Few Months)

VINAYAK GOTE — Sun, 01 Nov 2026 07:25:02 +0000

A few months ago, I made a decision. I wanted to start contributing to open source.

I work as a Java backend developer at Wipro, building REST APIs with Spring Boot. I like my work, but there is one problem with it: the code is private. Nobody outside my team can see what I build. I wanted a place where I could write real code, get it reviewed by strangers, and prove to myself that I could work on a codebase I did not write.

So I picked a few Java projects and started.

It was not easy at the start

I thought I would find an issue, fix it, send a PR, and done. It did not go like that.

Finding an issue that nobody was already working on took time. Many good issues already had someone on them.
Reading a big codebase for the first time is confusing. You open one file and it leads to ten more.
Maintainers are busy. Some reply in a day, some take weeks.

The most useful thing I learned early: talk to the maintainer before writing any code. It saves time for both sides, and it tells you quickly if the issue is worth your effort.

How I work now

I keep it simple.

One issue at a time.
Small, focused changes. A small diff is easy to review.
I write the code myself and I understand every line I send.
I take review comments seriously, even when they are strict. Those reviews taught me more than many tutorials.

What came out of it

Till now I have had PRs merged in:

Zalando Logbook: I worked on the status-code based sink and log writer.
Adyen Java API Library: my change shipped in SDK v42.0.0.
Picnic error-prone-support: my PR got merged after review.

I will write about each of these in separate posts, because each one taught me something different.

What I am building on the side

Along with open source, I am building Sionna Visualizer, a visual dashboard on top of NVIDIA Sionna (6G + AI). It is a different area from my day job, and I wanted to see if I can bring my backend skills into it. You can try it here: https://sionna-visualizer.vercel.app

What you can expect from me here

I am going to write about my work step by step:

the PRs I made and what happened in the reviews
the mistakes I made and what I learned
my daily work and small lessons from Java and Spring Boot
progress on Sionna Visualizer

If you are a Java developer who wants to start open source, I hope my posts help you start sooner than I did.

And if you are a maintainer or a team looking for someone who learns in public and likes to collaborate, my DMs are open. You can also find me on GitHub: https://github.com/Vinu2111

Next post: my Zalando Logbook PR, what the issue was, and what the review taught me.

Leveling Up Daily 💪 | Java, SpringBoot & GoLang

VINAYAK GOTE — Sat, 24 May 2025 03:43:42 +0000

Hey Dev.to Friends! 👋

I'm Vinayak Gote, a Computer Engineering graduate (2024) with a 9.3 CGPA, currently on a mission to become a remote Full Stack Java Developer — and crack a ₹10+ LPA job within 6 months! 🌍💻

📅 What I Worked On Today:
Practiced Java DSA (binary search and recursion problems)

Built a SpringBoot API with service-layer separation

Learned about GoLang interfaces and how they compare to Java interfaces

Cleaned up my backend project files and improved code structure

Each small effort is helping me understand clean coding and better backend design.

🛠️ Projects in Progress:
Crop Monitoring System – added exception handling for better API reliability

Blog App – improved JWT-based login, starting frontend integration soon

Thinking of building a mini GoLang API for learning-by-doing

🧠 Learnings of the Day:
Binary Search logic can be applied in more real-world problems than I thought

SpringBoot's @Service layer is key for cleaner and testable code

GoLang’s interface system is simple, but super powerful!

🌐 Why I'm Sharing This:
To track my journey

To connect with other learners and backend folks

To create opportunities for remote backend roles

And to inspire others to stay consistent 🚀

Let’s connect and grow together! Your feedback, ideas, or even a quick “Hi” are always welcome. 🙌

🔗 GitHub: https://github.com/Vinu2111
🔗 LinkedIn: https://www.linkedin.com/in/vinayakgote

Thanks for reading! Catch you tomorrow with more progress 💙

Building Daily, One Commit at a Time 🔁

VINAYAK GOTE — Thu, 15 May 2025 02:19:20 +0000

Hey Dev.to Fam! 👋

I’m Vinayak Gote, a Computer Engineering graduate (2024) with a 9.3 CGPA and 2nd rank in my class.

Today was all about staying consistent and sharpening the skills that matter in backend development and remote tech roles. 💻🌍

✅ What I Did Today:
Solved 2 Java DSA problems (focusing on recursion and sliding window)

Practiced writing SpringBoot controller + service layer for clean separation

Explored GoLang structs and slices – still early, but exciting!

Organized GitHub with updated README files for my projects

Bit by bit, I’m refining how I write, debug, and deploy code.

🔨 Current Focus:
Crop Monitoring System – improving modularity and API responses

Blog App – preparing for deployment and writing documentation

Started brainstorming a GoLang microservice idea for fun!

💡 Key Takeaways:
Consistency compounds. Even 1-2 tasks a day move the needle.

Learning multiple backend languages expands your thinking.

A well-structured GitHub profile acts like a resume!

🧭 Why I’m Posting Daily:
To stay accountable

To connect with other backend learners

To get noticed for remote Java/Golang roles

To document the journey from beginner to backend pro 🚀

Let’s connect, collaborate, and grow together! 🙌

🔗 GitHub: https://github.com/Vinu2111
🔗 LinkedIn: https://www.linkedin.com/in/vinayakgote

Daily Progress: DSA, SpringBoot & GoLang

VINAYAK GOTE — Mon, 12 May 2025 01:18:31 +0000

Hey Dev.to Community! 👋

I'm Vinayak Gote, a Computer Engineering graduate (2024) with a 9.3 CGPA and 2nd rank in my class.

Today was another solid step in my journey toward becoming a remote Full Stack Java Developer. I’m staying consistent, learning, and pushing myself to get better each day. 🚀

💻 What I Did Today:
Practiced Java DSA: Solved problems on arrays and recursion

Worked on a SpringBoot API – implemented GET/POST endpoints

Studied GoLang basics – data types, functions, and goroutines

Cleaned up my GitHub and committed project updates

These small wins are helping me build a strong backend foundation while exploring new tech.

🔧 Project Progress:
Crop Monitoring System: Refactored API logic, added response models

Blog Application: Integrated user authentication with JWT

Pushing everything on GitHub for transparency and consistency 💪

🧠 Key Learning:
Writing clean, modular Java code saves a lot of debug time

SpringBoot simplifies REST API design but demands good planning

GoLang's concurrency model is powerful and fun to learn!

📌 Why I Post Daily:
To stay accountable

To connect with devs on the same path

To document the small steps that lead to big results

To build visibility for remote job opportunities

Let’s keep growing together. Drop your daily dev updates too! 🙌

🔗 GitHub: https://github.com/Vinu2111
🔗 LinkedIn: https://www.linkedin.com/in/vinayakgote

Thanks for reading — consistency beats perfection 💙

Sharpening My Backend Skills

VINAYAK GOTE — Mon, 05 May 2025 01:32:49 +0000

Hey Dev.to Community! 👋

I’m Vinayak Gote, a Computer Engineering graduate (2024) with a 9.3 CGPA and ranked 2nd in my class.

Right now, I’m focused on becoming a remote Full Stack Java Developer, and every day I’m pushing myself to improve in backend development, system design, and problem-solving. 🚀

💡 What I’m Working On:
Solving Java DSA problems daily (arrays, strings, recursion)

Deep diving into SpringBoot – building and testing REST APIs

Learning GoLang basics (syntax, goroutines, concurrency)

Optimizing MySQL queries and understanding indexing

These tasks are part of my strategy to build real-world developer skills.

🔨 Current Projects:
Crop Monitoring System – REST APIs with SpringBoot + MySQL

Blog App – Login system, JWT auth, role-based routing

Each project helps me strengthen clean architecture, API structuring, and backend best practices.

🌐 Why I’m Sharing This:
To document my journey publicly

To connect with devs building similar stuff

To stay consistent and accountable

To increase visibility for remote job opportunities

🗓️ Coming Up:
Share Java concepts in a beginner-friendly way

Post GoLang progress with real code examples

Weekly GitHub contributions and project updates

Resume building and remote job strategies

If you're also learning backend tech or aiming for remote roles, let’s stay connected and grow together! 🙌

🔗 GitHub: https://github.com/Vinu2111
🔗 LinkedIn: https://www.linkedin.com/in/vinayakgote

Thanks for reading! Let’s crush it together 💙

My Remote Dev Journey Begins 🚀

VINAYAK GOTE — Mon, 21 Apr 2025 06:50:42 +0000

Hey Dev.to Community! 👋

I’m Vinayak Gote, a Computer Engineering graduate (2024) with a 9.3 CGPA and ranked 2nd in my class.

I’m on a mission to become a remote Full Stack Java Developer, and I’m aiming for a ₹10 LPA job within the next 6 months. This blog will be my space to share everything I learn and build along the way. 💻✨

💡 My Core Skills:

Java (OOPs, Core Concepts, and DSA)

SpringBoot (Building REST APIs and scalable backend systems)

MySQL (Efficient database design and optimization)

Frontend: HTML, CSS, JavaScript, React (basic to intermediate)

I’m currently upgrading these skills in the AccioJob Full Stack Java Developer program and applying them through real projects.

🚀 Ongoing Projects:

Crop Monitoring System – Backend with SpringBoot + MySQL

Blog Application – Full user authentication & role-based access

These projects help me practice clean code, REST API design, and database structuring.

🌐 Why I Joined Dev.to:

To post what I learn (Java, SpringBoot, DSA)

To meet other devs who are learning or building

To build a strong portfolio and developer network

To attract remote job opportunities and mentorship

📅 What You’ll See From Me:

Java and SpringBoot breakdowns

Beginner-friendly DSA explanations

Weekly progress logs

Tips for interviews and backend development

Let’s grow and support each other on this journey. 🙌

🔗 GitHub: https://github.com/Vinu2111
🔗 LinkedIn: https://www.linkedin.com/in/vinayakgote

Thanks for stopping by! 💙

My Remote Dev Journey Begins 🚀

VINAYAK GOTE — Sat, 19 Apr 2025 13:44:17 +0000

Hey Dev.to Fam! 👋

I'm Vinayak Gote, a Computer Engineering graduate (2024) with a 9.3 CGPA and 2nd rank in my class. I'm starting this blog to document my path toward becoming a remote Full Stack Java Developer — and hopefully cracking a ₹10 LPA job in the next 6 months. 💼💻

👨‍💻 What I'm Learning:
Java (Core + OOPs + DSA)

SpringBoot (REST APIs, Backend Services)

MySQL (Database Design & Optimization)

HTML, CSS, JavaScript & React (Frontend Basics)

I'm enrolled in a Full Stack Java Developer course by AccioJob and building projects to improve daily.

🌱 Projects I'm Working On:
Crop Monitoring System (SpringBoot + MySQL)

Blog Application (User Auth + Role-based Access)

📌 Why I’m on Dev.to:
To share what I learn

To connect with other developers

To grow my online presence

And to get noticed for remote job opportunities 🌍

🔜 Coming Soon:
Java/SpringBoot tutorials

DSA problem breakdowns

Weekly learning updates

Interview prep tips

Let’s connect and grow together! 🙌

GitHub: github.com/Vinu2111
LinkedIn: linkedin.com/in/vinayak

Thanks for reading! 💙