Home » When I Worked At Chrysler I Kept A Glossary Of Ridiculous Corporate Terms Engineers Overused At Meetings. Here Is That Glossary

When I Worked At Chrysler I Kept A Glossary Of Ridiculous Corporate Terms Engineers Overused At Meetings. Here Is That Glossary

Dt Phrases Top
ADVERTISEMENT

When I became a full-time engineer at Chrysler at age 21, there were certain elements of the corporate environment that I found flat-out odd. Why were all the engineers working in gray cubicles while the designers and businesspeople were literally in their own, colorful, beautiful buildings? Why did designers and businessfolks have better lunchrooms than engineers? Why does everyone leave at exactly 4:30? Why are engineers not allowed to use tools without having getting union grievances filed against them? Why did so few employees actually love cars? I could go on and on, but the thing I want to talk about today is the corporate buzzwords/strange terms used in the hallowed halls of the Chrysler Technical center circa 2015. I kept a list.

You might have read our article “One Ford Executive Created A List Of Mixed Metaphors And Malaprops Heard Around The Office And It’s Hilarious,” which was based on a great find by the Wall Street Journal. It turns out, a Ford exec would meticulously document any time he heard some sort of tortured mixed metaphor, and the list he jotted down is fantastic.

Vidframe Min Top
Vidframe Min Bottom

This article reminded me of my own list of tortured terms that I heard in the engineering halls of a major automaker. Specifically, this was in the halls of the Chrysler Technical Center, a humongous building in Auburn Hills that was, at least when I was there between 2013 and 2015, occupied on weekdays by 15,000 people. It was a larger-than-life epicenter of automotive development, with everyone from technicians to engineers to execs to designers all in the second largest office complex in the U.S. (second to the Pentagon).

Zkuiko7qnzbxslnuvmcc

Chrysler felt old-school when I got there after college. Mostly middle-aged men would walk through the turnstiles everyday at 7:30 AM with the same lunch pail they’d carried the day before, eating the same lunch, going through many of the same routines. There was plenty of bureaucracy, folks all wore khakis and polo shirts/dress paints and button-downs, and in many ways it kinda felt like a movie scene of the corporate world from the 1950s. That’s not to say it wasn’t an amazing place to work, because in many ways it was, but again, the point here is that my 21 year-old self — with little industry experience — found some of the corporate-speak to be really, really fascinating.

ADVERTISEMENT

E7zy 1owqaazang

For some reason, I decided to jot some of that corporate-speak down, using a title page usually reserved for official, top-secret engineering documents. In this case, I was too lazy to change the title from “Alternator Performance Requirements — 12V.” (Unrelated: I was for a while trying to get the electrical team together to give a “load budget” so that we’d know if the Motor Generator Unit — MGU — we’d chosen for the Jeep Wrangler JL was sized appropriately. How can we know if we have the right “alternator” if we don’t know what our electrical load is? Why was I doing this as a cooling system engineer, you might wonder? Because I realized nobody else at the company was doing it. Yes, Chrysler was the wild west, and in a way, it was awesome).  Screen Shot 2025 03 29 At 10.20.04 Am

My document, titled COMMON ENGINEERING WORDS V13 (yes, apparently there were 13 versions of this. Or maybe that was a joke), begins with the Holy Grail of Chrysler corporate terms — one so overused that it drove my friends and me absolutely bonkers.

“To your point.”

What the hell even is this corporate phrase, grammatically? “To your point?” Why use the preposition “to?” This makes literally zero sense, and I’m not the only schmuck who thinks this.

ADVERTISEMENT
Screen Shot 2025 03 29 At 10.29.51 Am
Screenshot: Reddit

The way this would be used is, someone would say something at a meeting, then someone else who was trying to get some words in so as to appear contributory would need to make a transition. This is where they’d deploy the atomic bomb of transitions: “to your point.”

“To your point, Bob, we really need to make sure our electrical load budget accounts for accessories like winches and the like.”

This statement need not have anything whatsoever to do with what Bob said. Such is the magic of “to your point.” Some refer to it as an “active listening” phrase; it’s basically meaningless, and means “I’m gonna talk now.” And my god was it overused at Chrysler.

Screen Shot 2025 03 29 At 10.20.46 Am

“Deep dive” was also a heavily used phrase around Chrysler. It basically meant “let’s actually do some engineering. Let’s stop pulling stuff out of our arses, and let’s do a bit of digging.” I also liked the term “root cause,” because nobody ever said the silent “analysis” at the end. “Let’s do a root cause on that heater warmup issue on JL GME-T4,” one might say. It meant basically: “Let’s get all the nerds together and do a bit of investigating on the core of this issue.”

ADVERTISEMENT

“Due diligence” was another corporate term that was used all the time. It’s a term that sounds nice and makes the sayer seem like a real, thoughtful, hard-working engineer. Though what it ultimately means is: Don’t be lazy. Look at this issue from all possible angles. I have it on the list because it was way, way overused.

Bwziaslcaaapdjk

One of my favorite terms used at Chrysler was “let’s look at the data.” This would often be uttered immediately after someone made a major claim, especially if it was a dubious one. “We expect a 3 MPG increase from this Active Grille Shutter Strategy,” an engineer might say. Someone would express their doubts, there’d be an argument, and then the doubter would say: “Let’s look at the data.” It meant “I don’t believe you.” It was sometimes used as a trump card to shut someone up, because ultimately: Data don’t lie.

“Can you go back a slide?” was a classic. You see, at Chrysler, lots of folks were just on their laptops during meetings, many not paying any attention (I was on Jalopnik quite often, if I’m being honest). “Can you go back a slide?” was a frequently-used way to make it seem like you were actually listening.

El282s Xuaauef6 1536x1152

ADVERTISEMENT

“Directionally correct” was an absolute classic at Chrysler. It basically just meant “at least this thing is leading us closer to the outcome we want, and not further.” I’d never heard “directionally correct” in my whole life, but at Chrysler I’d hear it basically daily.

Another favorite was “high level,” which basically meant “dumbed down.” And “low hanging fruit,” which basically meant changes we can make easily to get us closer to the desired outcome.

A strange one was “This five minutes,” which was used a lot by the former MR (Model Responsible) of the Jeep Wrangler JL, but also by others. “Use the Samsung data because that’s who our supplier is this five minutes.” What a bizarre expression. Why not just say “at the moment”? I have no clue.

Screen Shot 2022 08 05 At 11.01.00 Am

A “recovery slide” was a thing I’d only ever heard at the Tech Center. It means: “Man, we are SCREWED. Put together a slide that we can show our bosses so they know we’re working on this because otherwise we’re getting yelled at.”

ADVERTISEMENT

“Plan of record” I had also never heard prior to Chrysler. It means “the official plan.” There might be a dozen different engineering designs/suppliers/product plans, but what was the official corporate plan for a vehicle program was what was referred to as “plan of record.” It was always exciting when some cool, advanced technology became plan-of-record (though often times it’d be cut later in the program).

Screen Shot 2025 03 29 At 10.20.57 Am

“Let’s circle back” meant “You guys go get the actual answer please and come back and tell me about it,” while having a “small circle” usually meant “I don’t want input from some of the folks in this meeting.” The use of “worst case” in my department was basically a way to figure out one single “worst-case” test that could be our sizing/design point. “Use Davis Dam J2807 as your worst case,” for example. Though I suspect in other departments it was used similarly to figure out the most adverse situation a given design might face.

Another weird one from a grammar standpoint was “I can speak to that.” Why? Because grammatically, if you can “speak to” something it means you can attest to it. “I can speak to his skills as a programmer, as I worked with him for years,” one might say. But at Chrysler, that’s not how engineers used this phrase. “I can speak to that” just meant “I have words I can say about this topic.”

Screen Shot 2025 03 29 At 11.52.25 Am
Image: Reddit/r/grammar

“I can speak to the water pump’s performance. It looks like, according to the data, our flow rates are too high in our aluminum lines, leading to erosion concerns, but I’ll pull up this recovery slide and show you the root cause, plus we can do a small-circle after this and discuss low-hanging fruit to get us back on track.”

ADVERTISEMENT

So many engineers used the phrase “relative to” in the strangest way. They’d go on and on about something, and then say “relative to alternator performance” or “relative to the transfer case” — all at the very end of the sentence. For what seemed like an eternity you’d have zero clue what the hell they were talking about until that “relative to” dropped at the end, and you’d have to try to remember what the speaker had been blabbering on about for 30 seconds.

20220804 154755 (1)

“The art of the possible” was used to try to understand what solutions were at our disposal, “got my steps in” meant “dang this meeting was far away from my desk,” and “eye chart” meant some kind of chart or graph or page that was difficult to see. What a weird phrase, right? “Yikes, what’s that say there on the Y-axis? This thing’s a bit of an eye-chart.”

Anyway, before I conclude I’d like to mention a few more phrases I heard during my time engineering at Chrysler (the list above isn’t my latest and greatest; that one is sadly lost to time). One is “this is invention.” This, usually said in a negative manner, literally meant “nobody else is doing this. Why the hell are we gonna be the first?” (Yes, that says a lot about Chrysler’s overall philosophy, but we won’t get into that). There was also “10 pounds of sh*t in a five pound bag,” which referenced a tight packaging situation (like when we put the relatively complex new turbo four-cylinder into the JL engine bay). Plus there was “let’s take this offline,” which meant “we gotta stop talking about this now. Let’s deal with it later.”

Then there was “Does the customer care/Will the customer notice?”

ADVERTISEMENT

This one is my favorite because I remember being in dozens of meetings in which engineers would spend ages poring through data, trying to solve a problem, and in the end one person would quip: “What does this mean to the customer?”

And then the room will go silent, and everyone will realize they just wasted two hours.

God I love engineers.

h/t: Clay Johnson!

Share on facebook
Facebook
Share on whatsapp
WhatsApp
Share on twitter
Twitter
Share on linkedin
LinkedIn
Share on reddit
Reddit
Subscribe
Notify of
195 Comments
Inline Feedbacks
View all comments
Scott Umbreit
Scott Umbreit
19 days ago

It’s nice to know that the Ford Technical Hotline was almost the exact same thing in the same time period. “Due diligence” was one of my manager’s “Go-To” phrases that he’d just throw into a sentence, even if it didn’t make sense. My favorite phrase at the time was “We do it right, because we do it twice”

Baja_Engineer
Baja_Engineer
19 days ago

This is quite relatable to me.
Showstopper and due diligence are quite common here.

But the most overused one has to be “I’ll follow up” and ” Let’s follow up” which pretty much mean I/we won’t do anything about it until you start nagging on me/us.

Alex Estill
Alex Estill
19 days ago

One is “this is invention.” This, usually said in a negative manner, literally meant “nobody else is doing this. Why the hell are we gonna be the first?”

I get the positive value of this – learn from others. No need to invent something new if the solution is already available, in other words – build on top of the best current method. Example of how not to do this – Cybertruck.

Eephus
Eephus
20 days ago

My favorite at work now is “Let’s not get wrapped around the axle”, meaning let’s not spend hours or days analyzing something that won’t make much difference in the end.

Also I like “directionally correct”, I think I’ll start using that

Nick Fortes
Nick Fortes
20 days ago

I work in finance, I see some similar phrases. Due diligence, speak to/to your point, etc., it all gets on my nerves

Dan Parker
Dan Parker
20 days ago

I work in biotech and hear/use very much the same vocabulary regularly. If I hear a lot I can pretty safely tune out, if I’m saying a lot I know either a.) I shouldn’t be in that meeting or b.) I screwed up and didn’t do my homework. Or maybe c.) all of the above.

Ron Gartner
Ron Gartner
20 days ago

Ahhh corporate speak, how I don’t miss it. After so many years of being under the big C and being forced into meetings I had no reason to be at, the buzzwords and job justification language was tiresome. I truly wonder if a company could run off of people just speaking like normal folks.

Hell, my current company just put up a new poster in our office area outlining our strategic economic plan for the year. It’s basically a Mad Libs game with our company name and buzzwords that don’t make any sense until they are dumbed down to common verbiage. Is it that hard to write “Work together as a team” instead of “Strategize and effectively communicate within the established business sectors for future collaboration” ?

Racecar_Steve
Racecar_Steve
20 days ago

This post is hilarious and triggering- I work as an aerospace design engineer and I hear 90% of these terms daily from project managers and coworkers. Clearly, all managers, engineering and beyond, go to the same jargon workshop.

PlatinumZJ
PlatinumZJ
20 days ago

At my first job, there was a project manager who would use “give ’em the pickle” multiple times during his weekly meetings. These meetings were to update him about projects, and required the presence of all engineers working on any project, whether or not the projects were related. Sometimes they did get interesting; I learned that one engineer based his completion estimates on who was scheduled to work in the electrical shop that week, since he had a good idea of how much rewiring each person’s work would require.

My company has a manager who very, very badly wants to be in engineering. He also has a military background. The combination has resulted in ‘hotwash’ meetings at the conclusion of projects, especially if something didn’t go exactly according to plan. (I think it’s the same concept as “lessons learned.”) Project was delivered on time, but there was a last-minute supplier change for a part due to a factory backlog? Hotwash! Someone at the vendor’s shop misplaced some bolts that were due to be replaced anyway? Hotwash! Customer keeps cutting open a cover that has ‘DO NOT CUT’ stenciled on it? Hotwash! And so on.

Fuller Name
Fuller Name
20 days ago

I had a coworker point out that one manager often said “At the end of the day…” That manager left the company but now I continue to hear it everywhere. Obviously, I know he didn’t invent it but I can’t help notice it more now. It’s similar to seeing a certain car model more frequently when someone else says nobody buys them.

Benny Butler
Benny Butler
20 days ago

I’m currently an IT manager at a VERY large healthcare company. I can say that +75% of this stuff is used daily.

And as for acronyms, jeeze. Healthcare + IT + Business acronyms.

NoMoreSaloons
NoMoreSaloons
20 days ago

Okay so I used one heavily in my engineering days with an automotive supplier. Action Items. Because nothing, I mean nothing irked me more than setting a critical meeting with no “action items” at the end. What, you wanted us all here to talk and make no decisions? We have no plan going forward except for another meeting next week? Great, let’s waste more time.

Wilbur
Wilbur
20 days ago
Reply to  NoMoreSaloons

I had a supplier that would end every meeting with “We will continue to study this”, which always meant “You haven’t agreed to let us half ass this, so lets try again in a month. We might make a new powerpoint slide, but probably not.”

AssMatt
AssMatt
20 days ago

“Speaks to” makes me furious.

Emil Minty
Emil Minty
20 days ago

Caption for the picture in the cubicle:

Not now Lumbergh, I’m kind of busy in fact I’m going to have to ask you to go ahead and just come back another time. I got a meeting with the Bobs in a couple of minutes.

Sivad Nayrb
Sivad Nayrb
20 days ago

…so you’ve worked in the inner bowels of the Automotive manufacturing realm and are at a loss as to why the organization is typically FUBAR?

GirchyGirchy
GirchyGirchy
20 days ago
Reply to  Sivad Nayrb

Nah, he was more design engineering than manufacturing, so higher up the digestive tract.

NoMoreSaloons
NoMoreSaloons
20 days ago
Reply to  GirchyGirchy

As someone who is in manufacturing engineering, (previously automotive adjacent), I can confirm there is a bit of a disconnect the further removed from the floor you are. We used to do Gemba Walks, which mean “Get off your ass, go on the floor and see the machine/process that’s causing issues.” So even in the corporate world it’s at least outwardly apparent that you have to be in the mess to see the mess.

GirchyGirchy
GirchyGirchy
20 days ago
Reply to  NoMoreSaloons

As a Manufacturing Engineer dweller, I’m very aware of that. We work with the design engineers during prototype programs, and are almost never brought in early enough to fix obvious problems. It would benefit everyone for them to at minimum send us a list of a few questions before embarking on a design we later shoot down in flames.

Gemba Walks are the best! We love it when HR or Finance turns in a finding for something like a 3-ring binder of help documents shoved in a machine frame weldment because the binder is “holding up the machine.” Um…no, it’s just shoved into a slot to get it out of the way.

NoMoreSaloons
NoMoreSaloons
20 days ago
Reply to  GirchyGirchy

Haha I used to work in tires, and they had some interesting rules there. When we did Gemba walks, any wood on the floor was to be confiscated as splinters couldn’t be picked up by our x-ray. However, one day we noticed an entire storage area with literal tons of equipment on wooden pallets. Corporate found a “loophole” in the standards that required the storage area rebranded as “temporary loading/unloading dock” which allowed them to keep the pallets of wood on the floor instead of investing in metal skids and spending months worth of labor to unload everything. But a 2×4 was to be confiscated immediately!

Hoser68
Hoser68
20 days ago

My favorite are acronyms.

See how long you can keep a conversation going without meaning by talking about the dangers of TLAs. Only when directly asked, define that as “Three Letter Acronyms” Very fun to do with IT people. “I had a TLA problem in DOS that impacted my RAM and ROM on my IBM.”

I had a coworker use a long term for something for 6 months before corporate decided to use an Acronym. Thus we had official e-mails with LOL, WTF, and TLDR in them. All of them standing for things my coworker had planted by using the same term over and over again before someone in corporate decided to use an acronym.

This cuts both ways. I had surgery last year and had to go on Short Term Disability. Having e-mails from HR about my STD felt weird.

Overall, engineers use Acronyms all the time as a way to show they are in the know.

But you do have to be careful. I was in an argument with a know-it-all coworker. The dude dropped a TLA to show our boss how he knew stuff I didn’t. He should have actually read the document that he got the TLA from. I’m one of the authors.

GirchyGirchy
GirchyGirchy
20 days ago
Reply to  Hoser68

We have a lot of fun with acronyms here in our automotive assembly plant, either coming up with new ones or inventing new meanings. We have a lot.

Or we see how many similar ones we can string together into a meaningful sentence…this was my favorite:

“Hey Tom, can you grab the PIV to pick up the VIP, and take them to see the VPI at IPV?”

TDI_FTW
TDI_FTW
20 days ago
Reply to  Hoser68

TLAs drive me crazy, but decidedly less so if there is a section in the document where all terms/acronyms are defined. NASA is at least very good about this in their public-facing documents.

I also like to pedantically point out that a TLA is more often actually a TLI in my experience, because NASA is an acronym but IBM is an initialism.

Last edited 20 days ago by TDI_FTW
Hoser68
Hoser68
20 days ago
Reply to  TDI_FTW

What if you have 5 different sections with definitions? And they aren’t the same in different parts of the document? Unfortunately, I’m on the author’s list for two documents like that.

NEVER let Engineers write stuff unsupervised.

TDI_FTW
TDI_FTW
20 days ago
Reply to  Hoser68

The whole document just has one overall section with definitions and then, while being several pages long, it’s not too bad.

Hoser68
Hoser68
19 days ago
Reply to  TDI_FTW

Must not have been written by multiple subcommittees. I work on Codes and Standards. The only thing worse than engineers writing to each other is when they think that what they write might be read by lawyers. They start using 10 dollar words.

When it gets really fun is that these are international standards. Some engineer years ago found one of those $30 words that describes exactly what we wanted to say without a full paragraph. When first introduced, everyone was like “huh” but after reading Websters, we loved it and it became a common term in meetings and used a lot in the Code. Unfortunately, it was one letter from a term that meant sexual relations, but since we had been using the clean version and it is pronounced differently, nobody took a second glance at it.

When translated into other languages, we got questions back about what the hell was wrong with American Engineers.

TDI_FTW
TDI_FTW
19 days ago
Reply to  Hoser68

That is incredibly fascinating and now I need to know more.
And yes, most of the documents I reference from NASA are extremely narrow in focus. And other documents just need one editor to come through and clean things up before they’re released to the masses – which is a good idea for any large effort.

Hoser68
Hoser68
18 days ago
Reply to  TDI_FTW

I work on an ASME Code and an ASME Standard. Both trace back to the big mamma jamma “ASME Code (the Boiler and Pressure Code).

This BPVC was first published in 1914 and a lot of states made it the law on how run a boiler. It’s now international and has expanded far behind the original intent which was “how to keep your building or train from vanishing randomly”.

Today, it’s 14 volumes, each over 3″ thick. About 900 engineers meet once a year for a week to work on updating it and answering questions (one of the volumes is nothing but responses to questions).

But they don’t have a 5 day long meeting with 900 engineers all at once. What they do is have sub-sub committees early in the week. A group of say 50 people will meet for an hour talking about say “welding rods” (Section II Part C). They will come up with revisions and answer submitted questions. Then the chairman will go to the Part II subcommittee (mid-week) and report on what they did and why. Then the chairman of Section II will go to the main committee meeting (likely on Friday) to talk about what was done.

The result is that because the scope is so insanely broad and each little subsection is written by a small group of experts, it is common for each sub-sub committee to come up with their own definitions and way to word things.

There is a lot of work to try to keep things consistent and ASME has a lot of technical writers trying to keep things understandable. But it’s like herding cats when you have 900 engineers from 4-500 different businesses each with their own way of seeing the world.

I’m work on a Code referenced in BPVC Section XI and Section III and on a different Standard (linked to Section III).

PS.

CODE. Rule that is not optional. Most US states and many foreign countries require the use of ASME CODE by law. NASA is one of those exceptions. They can (and do) built pressure vessels that are not to the ASME Code (Section VIII) and can do so because you would never get a Code Stamped vessel airborne (3:1 safety factor generally).

STANDARD. A way to do something. If the Standard is accepted, then you can use the methods in the Standard without having to re-invent the wheel.

PPS. Look for a four leaf clover on things. The four leaf clover design will have ASME in the leaves. The same document that covers how to build a nuclear power plants (Section III) also has a section (Section IV) on how to make a hot water heater.

TDI_FTW
TDI_FTW
17 days ago
Reply to  Hoser68

Wow, yeah I could see how in that particular instance things would get rather insane. A Code book is a completely different animal than the narrow NASA standards / technical memos when it comes to keeping it consistent. I’m sure that if you collected all of the NASA Standards/Technical Memos into one giant book it would look similar to what you are describing.
Trying to make your 14 volume code book be cohesive would take years of work and is probably not worth it typically.

Thank you for taking the time to type all that up, it was extremely fascinating to read how that works as someone who has to reference sections of codes/standards from time to time.

Hoser68
Hoser68
17 days ago
Reply to  TDI_FTW

I work well lower in the food chain. The Standards Committee I go to struggles to have 30 people to show up. I started working on joining a similar Code committee because they started using the same hotel. Maybe 150-200 people for that.

What’s fun is that on my tiny committee, there’s a game of musical chairperson. Every so many years, we have to draft a new sucker. There are term limits on this. Challenge one is that every single person on the committee has ADHD and every one of us could be in the HOF for talking to much. However, there is a benefit. My tiny committee has to report to the Bureau of Nuclear Codes and Standards (BNCS) twice a week to try to describe what the herd of hyperactive cats have been up to. One meeting is in America, the other is always overseas. It rotates, Asia one year, Europe the other.

And the promise of international travel on the company dime and having your name on the top of an important document lures these poor suckers in.

Because challenge 2 is convincing management for you to take an international trip on their dime to see people that aren’t your customers, but the regulators of your customer’s customer’s customers.

When management won’t pay for the trip, but they still have signed up to go. Which makes the volunteer part a LOT more painful.

Crimedog
Crimedog
20 days ago
Reply to  TDI_FTW

Glad I didn’t have to scroll far to find this. I commend you for your intellectual honesty.

Emil Minty
Emil Minty
20 days ago

Directionally Correct should be a weekly 3 hours podcast by Torchinsky on taillights.

1961ford
1961ford
20 days ago

Did you ever play “Bullshit Bingo” with your workmates?

KevinB
KevinB
20 days ago
Reply to  1961ford

I have. The winner exclaims “OUTSTANDING” when he or she wins.

John in Ohio
John in Ohio
20 days ago

A ton of this transfers over to the IT world as well. Honestly, probably just about any soul sucking corporate experience. It used to drive me nuts as well. The impression that I get from reading this great little piece is that Chrysler probably suffered from “We’ve always done it this way.” mentality as well.

Trust Doesn't Rust
Trust Doesn't Rust
20 days ago
Reply to  John in Ohio

I hear this stuff every goddamn day. Eventually someone is going to utter “To your point” and I’m going give ’em the old fork-in-the-eye.

Dennis Ames
Dennis Ames
20 days ago

did you not say ” Well that was one of the possible scenarios” when you meant ” I told you that this was going to happen months a go”?

Bryan921
Bryan921
20 days ago

With 17 years in the Information Systems sector I can also attest that these words are commonly used in the Computer Software world as well…”root cause” gives me chills…so does “drill down”.

Lava5.0
Lava5.0
20 days ago

I count 14 from your list that are prevalent across in the DoD engineering sector so you are not alone in this.

We also use “that being said…..” a bunch.

The Pigeon
The Pigeon
21 days ago

I’ve rediscovered my tic after seeing a PF spec cover sheet. So thanks for that.

Also I probably use every single one of these daily without even realizing it.

Last edited 21 days ago by The Pigeon
195
0
Would love your thoughts, please comment.x
()
x