Some times when you are working with fellow developers, they can use some terminology or design pattern which you either don't know or can't remember, this results in a conversation where you aren't quite understand their point.
This happened to me recently when a developer mentioned the Gateway pattern. Design patterns in coding terms are standard/best practice for reusable code for common design problems. You can compare (ish) design patterns to cookery books, it you wanted to cook a shepherds pie you would use a recipe from a chef in their latest cookbook. If you want to learn more about design patterns start with this Wiki article
This can be a bit awkward because you can feel like a bit of an idiot and the other person was talking about it like it's something everyone knows.
Don't be embarrassed about not knowing something
There is nothing wrong with not knowing something, it will happen often in life, so get used to it and embrace it.
If you don't something grab the opportunity to learn something from someone who knows about it. They won't look down on you and 99 percent of people will be happy to help and explain it to you (because it makes them feel great being the teacher/master). If they do look down on you, so what, you will be learning more knowledge and improving your value to the company and yourself.
One benefit of a person explain a topic, is it can be easier to understand in comparison to reading it from a book/article and you have the benefit of asking questions and clarify points you are unsure of.
One of my core beliefs is too constantly keep learning and improving, if you don't understand something, don't sit quietly, hiding in the corner, be proactive and learn that piece of information, you never know when it may come in useful in the future (when you really need it).
Don't stay quiet
If you choose to nod your head and try and bluff your way through the conversation, not really understanding what they are talking about then you are losing out on an opportunity to learn and grow.
It's a similar situation to a class or talk when the speakers asks if there are any questions, there is something you really want to know but you think you would look like an idiot if you asked that question.
If you are thinking that question, probably a number of other people are thinking it as well and they will be glad you asked it. Work out the logical outcomes of asking and not asking
Ask (potentially) stupid question
You will get an answer from the speaker
Some people may think you are stupid
Some people may think, great question I was thinking that myself but I was too scared to ask.
People will know of your existence
You learn a bit more
You are interacting with the discussion, this will make it easier for you to remember the details of the point being discussed at a later date.
Don't ask (potentially) stupid question
You learn nothing more
No one notices you
Nothing else happens
I added people notice you as a benefit because this could be used by someone to strike up some small talk with you later, it also shows people you are a proactive person
Back to the Gateway pattern.
The gateway pattern is a lot simpler than it sounds, but sometimes it takes great skill to describe things simply and concisely
Microsoft has a great description of the Gateway pattern, which you can find in full here
aGatewaycomponent that abstracts the access to the external resource. The gateway presents a single interface to the integrated applications while hiding the external resource interface. In addition, the gateway encapsulates any protocol translation that may be necessary to communicate with the external resource.
pictures can often set the idea in the mind
So you can see the Gateway pattern creates a single source of access (a single interface), behind it, it can offer lots of different methods.
You could consider paying for an item on amazon/ebay. The seller only wants to be paid but behind the payment there are lots of different methods of paying likecredit card, debit card, paypal etc.