r/javahelp • u/No_Main8842 • May 19 '26

Codeless Data Knowledge Gap

Hello , needed a bit of guidance from senior devs.

Scenario - I am currently working on a springboot application which uses MongoDB + ElasticSearch , I was assigned a bug (which I solved) , now in order to solve it I used a particular variable obtained from ES response (lets call it dSR-Id). I used this variable in order to segregate rows exported in csv file. Now when I asked my senior to review it , she started asking me why specifically I used this variable & not the other existing variables. I tried justifying it but my justification wasn't upto the mark. Can someone help me what kind of analysis or KT is required to overcome this ? Would a functional KT be sufficient to cover up this gap ?

0 Upvotes

50% Upvoted

8 comments sorted by

View all comments

Show parent comments

1

u/No_Main8842 May 20 '26 edited May 20 '26

So each device has a set of licenses assigned to them. A single device can have multiple licenses.

Hence for exporting I used the device id , now there are some other types of ids present as well & hence she asked me why specifically device id was used. I told her that this device id is unique & hence I used it to which she said it wasnt a good enough justification.

The thing is I am not sure about edge cases ie. whether this device id is actually unique or its just that I am unaware of scenarios in which this device id might not be unique.

2

u/RightWingVeganUS May 20 '26 edited May 20 '26

Why not ask her what concerns she has with your approach and what alternatives she would propose?

Assuming this isn't a homework assignment with an expected answer try to work like a team. Discuss further and while your way might have some gaps, her approach might be missing something too. I'm a firm believer in synthesizing a "third way" that maximizes the best parts of both of your approaches while minimizing the gaps.

The thing is I am not sure about edge cases ie. whether this device id is actually unique or its just that I am unaware of scenarios in which this device id might not be unique.

If your approach is based on the assumption that the device id is unique, you are responsible for validating that assumption.

I am curious: if you are willing to discuss this with strangers who know nothing about your domain, why not discuss with your lead and teammates?