canyonwalker: Sullivan, a male golden eagle at UC Davis Raptor Center (Golden Eagle)
McDonald's announced this week that it plans to hire 375,000 people this summer. The news is being touted, politically, as evidence of President Trump's strong economy. But how significant is that figure of 375,000 in McDonald's overall picture? I mean, it sure looks like a big number, but is it, really? My conclusion after doing a bit of research is that it looks like Business As Usual that's being touted for political purposes. Here's my analysis:

The first question I considered is how many people work at McDonald's already. 375k is an increase of what percent? A quick search shows that McDonald's currently employs about 800,000 workers. In that sense, adding 375,000 new employees is a huge gain, nearly +50%. But that's not an accurate picture. 800k jobs is a corporate figure. Most McDonald's restaurants are run as franchises, and franchisees do their own hiring. McDonald's actually said in its press release that 375,000 will be hired by it and its franchisees. Added together they currently have an estimated 2 million employees today. So while 375,000 is still a big number it's less than a 20% increase.

My next question is what McDonald's turnover rate is. Hiring 20% new employees is a lot if it's all net growth, but if it's just replacing people who leave then it's nothing new. It turns out McDonald's turnover rate is pretty astonishing— it's 150% per year! That means that for every 100 jobs they have, they have to hire 150 new people every year. Even if we assume this 150% turnover figure applies to only the 1.2 million employees working at franchises, that means McDonald's has to hire at least 1.8 million people every year just to stay level. Dividing that by 4 for a very rough quarterly figure, that means 450,000 new hires every quarter, just to stay level. Viewed from that perspective this announcement of hiring 375,000 people looks like it's actually a staff reduction strategy.

So, is this supposedly positive economic news actually a stealthy way of announcing layoffs? I don't know. Technically, BTW, McDonald's wouldn't need to lay off workers as they have such a high turnover rate anyway. But the point is they could well be decreasing their staff overall.

The notion of a staff reduction makes sense if you look at what's happening at the restaurant level. In more and more places, ordering kiosks are being installed to replace human cashiers. It kind of sucks from a customer perspective, but hey, many restaurants are trying to replace people with self-service.

canyonwalker: wiseguy (Default)
Another week at work, another batch of rumors about who's leaving next. 😓

This week's rumored departures involve one of my immediate coworkers, "Abby", and a technical leader in an adjacent function, "Marty". Long story short, the rumor about Abby is not true— but also not 100% false; it was merely exaggerated— while the rumor about Marty has been confirmed, officially.

The rumor that Abby is leaving later this month really threw me for a loop. After my whole team was sacked four weeks ago and I was "last man standing" in the region, I was merged into another team. Then I learned that that team's top performer had just quit, because of reasons I totally agree with. That team's manager then quit, too, also for reasons I totally agree with. Now my new team, which used to be two full teams, is down to two engineers— myself and Abby— plus our acting manager. If Abby leaves I'm "last man standing"... again! Thus I'm glad the rumor I heard about Abby is not true. ...Well, not 100% true. 😥

I spoke to Abby today and found out that the person who shared the rumor with me misunderstood something Abby said in confidence. Normally I'm not one to traffic in rumors. I'm content to wait patiently, or perhaps check cautiously, to learn the truth of them. But with the raft of departures reaching crisis level in my department, I had to know. I asked Abby point-blank, explaining the above as the reason for my directness.

The truth is that Abby's not leaving. Yet. She hasn't accepted another job or given notice of departure. She merely told a mutual colleague, in confidence, that she's low-key looking for another job. "Low key" meaning she's now responding to cold calls and LinkedIn messages from recruiters instead of ignoring them. We chatted about her reasons for starting a job search and... unsurprisingly if you've read anything above... I totally agreed with her. 😓

The other rumored departure, the one confirmed by official announcement, is my colleague Marty. He's one of the leaders in an adjacent department. I haven't spoken to Marty yet about his reasons for leaving but I expect a lot of them will be the same as I've heard from everyone else. In addition to those, though, is an effective demotion. In the recent cuts and re-org Marty was shuffled down to a position I consider a dog house assignment. One of his peers was promoted to be his boss, others were promoted up next to him, and his direct reports were taken away from him and reassigned to new managers.

A year ago "quiet quitting" became a big term in Corporate America. What happened with Marty was, IMO, the role reversal of that: quiet firing. Marty retained his management title while his duties were reduced to those of a senior individual contributor. I call it quiet firing because across my career I've seen companies do it a variety of times but it's only ever worked out— as in, been mutually acceptable to employer and employee for more than a few weeks— once. Marty isn't success number two.


canyonwalker: wiseguy (Default)
Ever since my company made cuts and restructuring in parts of the sales and customer service organization last week Tuesday the situation has been getting worse day by day. I already gave up trying to call it worse, worse-er, worse-er-er and switched to mathematical notation like worse-(er)5 yesterday. A new day today brings yet-another increase in the exponent; i.e., a new, higher degree of worse.

Today's new degree of worse-ification comes in the form of something I heard yesterday but considered a rumor at the time now being confirmed as true. Yesterday when I was discussing problems in company strategy and execution with "Ike", a former a colleague who coincidentally quit just ahead of the staff cuts, he said, "I hear that John and Liz are leaving the company." I mentally filed it as rumor because I'd heard no official news of imminent departures and hadn't yet heard it unofficially from anyone else.

"John" is a manager within my organization, a peer of my boss; "Liz" is a VP in marketing. The news that either of them might be leaving is disappointing, as both are high performers in their jobs. Liz is the most engaged and industry savvy marketing leader we've had in years. John is relatively new as a manager but has really stepped up to lead not just his team of people but drive drive side projects that benefit everyone in the sales engineering function.

Well, today I saw confirmation that John is leaving. It was mentioned in an anonymous comment at the very end of a department-wide meeting. I haven't gotten confirmation yet of Liz resigning, though the fact that Ike was right about John makes it more likely he's right about Liz, too. Update: I got confirmation of Liz's departure a few days later.

Losing people like John and Liz is an example of brightsizing I first wrote about a few days ago. Simply put, brightsizing is when smart, successful people quit in a context of job cuts or reorganizations. When a company makes cuts it usually targets low performers termination. But when people subsequently quit because they no longer believe in or trust leadership, it's often the high performers, the best and the brightest, who leave first. That's why it's called bright-sizing.

High performers tend to leave quickly because they've got the strongest résumés and thus the greatest ability to get hired into a great new job right away. And as high performers they want to work in equally high-performing organizations. They're not going to squander their careers under executive leaders who demonstrate poorly thought-out strategy, unprofessional communication, and a growing record of insufficient results.

Brightsizing is a double-whammy for those of us who'd like to see it through. Not only is their departure another no-confidence vote in the leadership, the loss of high performers makes getting our job done well with who's left much harder.
canyonwalker: Uh-oh, physics (Wile E. Coyote)
I don't know what's going on with my job this morning. The company has whacked my whole team except for me. My boss and two immediate colleagues are out. There have been no communications about what happens next.

I only know this much because colleagues reach out to me via text message. It looked like their company comms were disabled early this morning. The texts started with a message from my boss at 7:20am.

Boss
It's been a pleasure guys. I have really enjoyed working with you guys and I wish you well going forward. Please keep in touch.

WTF? I wondered to myself. It sounds like he's quit— or been fired. But there's been no official communication.

I decided rather than send an alarmed response I'd hold off and see if he volunteered more info. Plus it was 7:20am, before my usual start of 8am. One of my two colleagues asked the obviously clarifying question, and our boss confirmed that he's no longer with the company.

Then came this:
Colleague 1
Just found out that I'm also no longer with the company It's been great working with everyone. Best wishes to you all. Keep in touch.

Wait, what? Now I'm afraid to read my email!

Colleague 2
I'm gone too.

Is this a joke? A glitch in our HR system?

It's no joke. It's not a software glitch, either. My boss and the rest of my (small) team have been let go.

At this point I'm wondering what I'm supposed to do. I will repeat, there have been no official communications. I can only surmise that I'll be merged in with the regional team covering the Central US. And whatever team I'm made part of, I hope they bring another colleague my way. Right now there are 4 account execs in the West, and only me left standing as a sales engineer to support them. There's no way, zero, I can cover all that work.

UpdateIt Gets Worse!


canyonwalker: Uh-oh, physics (Wile E. Coyote)
Yesterday I wrote about how my upcoming two+ week vacation will be the longest vacation from work I've taken. I suppose I should put an asterisk next to that claim. I actually took 3 weeks off from work once before. The asterisk is because it technically wasn't vacation time. It was a sabbatical.

20+ years ago I worked at a big company where sabbatical was one of the benefits. Sabbatical was 6 weeks of paid time off awarded every 4 years. Having 6 weeks off was close to incomprehensible to me at the time, plus Hawk had nowhere near that amount of time off available, so I split my sabbatical into two chunks of 3 weeks each, as company policy allowed.

The first week of those 3 weeks I actually had vacation with Hawk. We traveled together and did some backpacking. Then the next 2 weeks I spent on moving house. We'd just bought a new place! I spent a week cleaning up & packing up the old place for move out, then a week unpacking & arranging in the new place. Overall it was time well spent. But what happened next wasn't good.

In the US there's a broad misgiving about taking long vacations from work. "If you're gone too long, they'll realize they don't need you," the sentiment goes. Indeed, I came back from sabbatical— half a sabbatical— just to be laid off a week or two later. Yup, I had just demonstrated that I wasn't critical path to my company! 😰😱🤯

Let's hope a mere two weeks away from work hits the sweet spot of being long enough for overseas trip but not so long my company decides my employment is no longer consequential to them.

canyonwalker: wiseguy (Default)
Recently a few high profile tech companies have announced layoffs. Last week it was Twitter, with new boss Elon Musk quickly moving to fire 3,700 people, half the company. He moved so fast the company the next day tried to hire back some of the people it dismissed because they were critical to projects Musk still wanted to ship. Today Meta, the parent company of Facebook, announced layoffs of 11,000 staff, 13% of its workforce.

These layoffs concern me because they may indicate an emerging trend. And yes, it's more than just two companies. Twitter and Facebook are household names; but several other Bay Area tech companies (e.g., Lyft, Opendoor, and Stripe) announced layoffs last week, too. My own employer had a small round of layoffs last month.

People have been predicting a recession for most of 2022 already. In July the simplest technical definition of a recession was met. I pointed out at the time that it takes more than 2 quarters of minor economic contraction to really make a recession. In particular hiring and job growth were still going strong. If that's turning downward now, though we could be in for a real recession soon. And if we're headed into a real recession, cuts like that <10% layoff my employer had may just be the start.


canyonwalker: wiseguy (Default)
Trade Show Day 1 is in the books now. I got back to my hotel at almost 9pm. It was a long day! I was working already before 8am, trying to get a demo into shape. By 9:15 I was at the convention center. At 10:30am the exhibitor hall opened. And then it was almost nonstop until 8pm.

One amusing bit about the show today was that across from our booth is a job postings board. It's a white board where people (mostly) freehand notes about what they're looking to hire. I thought about going up there and writing

Do you ❤️ your job?
Good, because we're NOT HIRING!


See also: my company's small layoff a few weeks ago.

Keep reading: More humor from Day 2 at the show!


Layoffs

Oct. 3rd, 2022 09:27 pm
canyonwalker: wiseguy (Default)
There was a small round of layoffs at my company today. No, I was not impacted. But ironically I was thinking about the prospect of layoffs over the weekend. While many stories in the news the past several months have been about record employment and rare leverage in hiring favoring job seekers, articles in just that past few days have begun talking about layoffs. Meta, for example, which has apparently never had a layoff, just announced one.

The fact the tide of the business cycle is turning to layoffs now is unsurprising. Just over two months ago it was announced the technical definition of a recession, two consecutive quarters of economic contraction, had started earlier this year. (One of the problems with this definition is it only recognizes a recession ~8 months after it starts.) Perhaps even more important than that is the practical definition: most people believe we are in a recession. Since I wrote that two months ago the stock market has dropped further. Friday it closed down 25% YTD. Furthermore, bears are in the majority. Investor sentiment is that it will get worse before it gets better.

Fortunately for my company and those remaining with it, this was a small layoff. Company-wide, fewer than 10% of the staff were let go. Within my department of ~30 people, only 2 were dismissed. Both were people who've been with the company about 6 months.

Updatewith more perspective a day later the layoff decision looks worse. 😨

canyonwalker: wiseguy (Default)
Whew. This story about my first experience with a corporate layoff has grown to 6 entries. Well, that's really not surprising as it was an eventful and formative time for me. Really the biggest surprise is that I didn't set down in writing, except for a few emails to friends at the time, my thoughts about it until now, so many years later!

At the end of The Day of Truth, after The Aftermath, my colleagues and I went our separate ways. We did plan a lunch date to get back together a week or two later.

Our spirits were still high when we met back up for lunch. As I cast my memory back upon that time from my perspective today I still marvel at how optimistic we all were, at how optimistic I was. Of course, it wasn't just optimism. The job market was good, and our particular sector was hot. I'd interviewed with at least 5 companies and had verbal or written offers from two already.

Where to Go Next— or Not 

My former manager, a former colleagues, and I all had written offers from the same company. It's another major, name-brand tech company you'd recognize the name of today... though back then it was not yet a household name. The three of us met to discuss the prospect of working there. We agreed, "No." 

Why no? For me it was a stonewalling answer from the VP Engineering I'd be working under. "How do you manage a project that falls behind schedule?" I asked during our interview. He gave a blanket denial that projects ever run late. "That doesn't happen," he repeated as he refused to answer the question. That struck me as a) gross incompetence, b) outright dishonesty, or c) both.

My colleagues had observed an interaction between the CEO and his executive assistant... she flinched when he seemed upset, like she expected him to scream at her... or worse. FWIW I saw that interaction, too. I didn't realize, "OMG, she's afraid he's going to hit her!" until my colleagues challenged me to think about it again.

"Bert", the manager in our department who quit in protest on The Day of Truth, already had a job offer from a company in Chicago. They Fed-Exed him a deep dish pizza packed in dry ice with his offer letter to say, "Welcome to the team."

Bert also had one of our former colleagues practically sitting on his lap at lunch. They were dating. They had actually been dating several months but keeping it quiet since he was her manager and it was against company policy. Now they were "out" publicly and moving in together. She was still working at the company but planning to quit. The new department was in chaos.

Most of us took a bit of time to ourselves between jobs... except Bert, whose new employer wanted him to start right away. That was just as well for him, as he didn't get a severance package. Those of us laid off were given reasonably generous severance. I'd worked there less than a year, and my payout totaled to nearly 4 months salary.

I used that money to take two weeks to choose the right job offer (I chose wrong anyway— but that's another story!) and then relax two weeks before starting my new position. The rest I used, with a bit of existing savings once I got situated in my new job, to buy a new car.

canyonwalker: wiseguy (Default)
My 6-week odyssey with getting laid off from a job years ago culminated in The Day of Truth (previous entry). The actual moment of truth was surprisingly brief. But the... denouement... lasted the rest of the day.

Moving Out

After receiving formal notice of my termination in a morning meeting with my new boss— who both met me and fired me in the space of one short meeting!— I went back to my office to pack my things. Several of my colleagues were packing, too. A few of them had also gotten notice first thing in the morning. Of course, the funny thing was they actually knew five weeks earlier. That's the whole rub of this story: many of us on my team knew in advance. But people on other teams couldn't know we knew. We had to act outwardly like we didn't. That meant no packing up our offices ahead of time.

Packing up my office went quickly. I'd been there a short time, less than a year, so my "things" were two shelves of technical books and one box worth of personal mementos. Some of my colleagues had been there for 6-8 years, though. Their "things" were... basically their whole offices, minus the furniture and the computer. Back then people's offices looked lived in, often like college student dorm rooms but with way more expensive hardware. And a $300 nameplate next to the door.

The Aftermath

The nonchalance I'd practiced the 5 weeks leading up to that day cracked when it was finally real. I wasn't the only one. For my colleagues who'd been laid off, it was the end of an era. We loved what the company was even as we were frustrated with what it had become. But ironically the people hit hardest by the cuts were two of my colleagues who were not laid off.
  • "Kelly" was a young software developer, less than a year out of undergrad. His degree wasn't a strong one so landing this job at a storied tech company was the best thing that happened to him in his life. Moreover, the team had welcomed him in (he was a hard worker) and his boss, "Bert" had spent quality time with him to map out a career growth path. Kelly was so happy. His visible excitement just coming to work every day lifted the spirits of us around him. But with the layoff his cheer became visible despair. His project was gone, his boss was gone, his career path was likely gone, and the whole company was seen as circling the drain. He was still employed but everything had just disintegrated around him.
  • "Bert" was a sharp senior engineer with a few successful new product launches under his belt. He'd been newly minted as a manager— a position he actually didn't want but took as a defensive play to steer the project away from interference by his arch-nemesis, "Fabio", a goofball middle-manager at the company who'd reached lifer status. With that project canceled and more than half the department being laid off, Bert assumed he'd be dismissed, too. He wasn't. Instead he was retained and reassigned, with no management duties, reporting to Fabio. Bert was pissed. He submitted his resignation hours later.

There was actually one person laid off from our division who took it hard. It was a person who didn't see the ax coming. Fabio.

Fabio, my new boss as of 9am that morning and new ex-boss as of 9:05am, called me back to his office at 4pm. When I saw him for the second time that day his face was flushed as if he'd been struggling not to cry. Probably from having to fire people all day, I figured. But there was more. "I've just learned that I've been laid off, too," he explained.

At least there's some karmic justice in the world.

canyonwalker: wiseguy (Default)
Recently I've been writing a small series about a time when my work colleagues and I knew a layoff was coming weeks in advance (part 1). We partied and slacked (part 2). Except I wasn't certain I would be laid off— though I did stack the tea leaves (part 3). After six weeks it came down to the Day of Truth.

The Day of Truth

The Day of Truth came. It was a Monday. I remember years later it was a Monday only because I remember meeting friends that evening at a local pub, the Duke of Edinburgh, for weekly Monday night gathering. I had affixed a "NOT COMPANY PROPERTY" sticker, intended to distinguish personal items from company assets, to my shirt. It was worth a few laughs among people who knew what it signaled.

Anyway, the Day of Truth. I had a first-of-the-morning meeting with my new director, Fabio. Yes, amid all the wrangling about layoffs the company also reorged me. 🙄

As I've written previously I was in the "maybe layoff" portion of my team. During the long walk to my new boss's office in a neighboring building on campus I legit didn't know whether the conversation was going to be, "Welcome to my team, CW!" or "Hi, I'm your new boss, and BTW you're fired." 😨 This director was the head goofball in the neighboring department of goofballs I mentioned previously, so I hoped it was the latter. 😅

For all that I'd spent the previous 5-6 weeks being nonchalantly non-worried about being laid off, suddenly I felt anxious. The Day of Truth was becoming the Moment of Truth.

The conversation in my new boss's office was mercifully short. Fabio didn't try to get to know me; we barely even made smalltalk. We quickly got down to business, which was my dismissal from the company. I assured him I had prepared for this possibility, was not worried for myself or my family, and held no ill will toward him or the company. I think we were done in less than 10 minutes.

After getting my papers I walked back to my office, packed my things, and hung out one last time with my colleagues. I stayed much longer than I needed to. I know part of me didn't really want it to end.

Staying through the end of the day did bring one unexpected note of closure. Fabio called me again. "CW, please come back to my office."

"Uh-oh," I wondered, "Is something wrong with my discharge?" 😳

Stay tuned... The Aftermath!

canyonwalker: wiseguy (Default)
Recently I've been writing about a situation years ago when my work teammates and I slacked for 5 weeks knowing a layoff was coming. As I noted, though, not all of us knew we'd be laid off. I was one of the people for whom it could go either way.

During the weeks my team slacked waiting for the ax to fall, other teams were abuzz with speculation and worry about who'd be whacked. "Watch for where there's a big conference room booked solid all month and the windows are taped over," was a common item of rumor around the company. "If you see that in your building, it means there'll be a lot of layoffs there." 

While others were busy trying to read the tea leaves, I was in the unusual situation of being able to arrange the tea leaves... at least for myself. My department had a combination of hardware and software engineers. The hardware project was being canceled and, with it, everyone who was a hardware engineer was being laid off. Software people would likely be reassigned. I was actually a software person— but one with strong (if high level) understanding of hardware design. That left managers above the two on my team uncertain about what my skillset actually was. So they asked me.

Now, when they asked me, "Are you more hardware or software?" I knew the reality of that question was, "Should we lay you off or reassign you?" I had already considered which side of the falling ax I wanted to be on. I had been excited to join the company for the particular project and the particular team I worked on. With that project and at least half the team getting whacked the prospect of continued employment there was frankly uninspiring. I opted for getting laid off. That didn't mean I misrepresented my work, though. I explained to Management I was a software engineer but had worked exclusively on improving the hardware architecture and developing software drivers for it.

"Hmm," they collectively responded. My answer wasn't the strict is-you-is-or-is-you-ain't answer they were looking for. That meant they didn't know whether to lay me off or retain me. And it meant for all I behaved as though I were being laid off I didn't know for sure, either, until the Day of Truth.

Next: The Day of Truth....


canyonwalker: Hangin' in a hammock (life's a beach)
In a recent blog I recalled a work situation years ago when my team and I knew we were getting laid off well ahead of time. Well, not all of would get laid off (plot twist!), but pretty much all of us knew we'd leave the company one way or another when the ax fell.

What, Me Worry?

"Aren't you worried?" my friends and relatives asked. I really wasn't. A big part of it was certainty vs. uncertainty. Many in the company were worried, because they didn't know what would happen to their jobs. But for me and my colleagues, we knew. And thus we could plan.

Another part of it was the situation didn't totally suck. The job market was strong, and we were all young enough in our careers that we hadn't become Company Men/Company Women who could no longer imagine— or, in some cases, qualify— for comparable jobs anywhere else. Don't get me wrong; staying at the company would've been our first choice. Staying at the company with an intact team and project, that is. But that option was already off the table. Senior management had already decided to cancel our project and dismiss at least half the team. So we started looking for our next gigs. And slacking.

Like an In-Office Vacation

We went into "marking time" mode for the next 5 weeks. My colleagues would drift in a bit after 9am, we'd take lunch together at 11:30, then a leisurely team coffee break for at least 45 minute in the afternoon, and we'd all leave a bit after 5. I was generally in at 8am, but I routinely spent the first hour or so surfing the web until my colleagues arrived.

In between all this we were still working, but barely. Email, we'd answer promptly, but little else had a sense of urgency. Mixed in with work we polished our resumes and reviewed them with each other, searched job boards, and did phone interviews in our offices. Oh, we still did work; we just didn't do it fast. Our work output slowed to about 1/3 normal.

One eerie thing— to me, anyway, as this was early in my career— was that our work slowed down for over a month, and nobody higher up cared. They all either a) knew that we were getting whacked and thus didn't care we were slacking, or b) were too worried about their own jobs and those of their favorites (many of them were Company Men/Women terrified by the prospect of having to find work anywhere else) to care about us. Or c) both. Yay, the reality of Corporate America.

Next up: Stacking the Tea Leaves



canyonwalker: wiseguy (Default)
A recent discussion elsenet about bosses who expect you to work after firing you reminded me of a situation I faced several years ago. This was sort of the reverse of that, though. Teammates and I enjoyed a semi-vacation because we knew we were getting laid off weeks before it was official.

I was working at a major company, a name brand absolutely everyone would recognize. I won't name it here. Though the company has had many successful years in its history, the time when I was there was... not the best. Our market share was dwindling as we delivered new products that were only incremental improvements in an otherwise competitive market.

We had some revolutionary products... well, revolutionary product ideas... in development but couldn't deliver them due to a combination of technical complexity and weak leadership. Weak leaders were fearful of investing the money necessary to bring them the products in development to fruition. One of those products was a game-changer that had been been promised for so long without being finished that it had become something of a joke, both internally and externally.

With market share dwindling, profits dwindling, and stock price dwindling, the company decided on a layoff. A big layoff. 30% of the workforce.

Six Weeks?

The company announced this huge layoff well in advance of the details of who would be laid off. Final determination of which employees were being whacked would take 6 weeks. At the time that delay seemed crazy to me, though as I've gained experience with the business world I've seen it's par for the course.

Standard or not, the delay was demoralizing. The impending huge layoff cast a pall over much of the company. Teams were wondering, "Are we going to be hit? How badly?"

Not my team, though. Our boss found out early in the cycle that our project was being canceled, and told us. She told us that one portion of the team would definitely be laid off and the other portion was TBD. I was in the TBD half. Either we'd get laid off, too, or reassigned to another department— under managers we thought were doofuses. 😨 So all of us took the mindset of "We're out of here in 5 weeks," and we acted accordingly.

Continued in Part 2: It was like an in-office vacation!

Profile

canyonwalker: wiseguy (Default)
canyonwalker

June 2025

S M T W T F S
1 2 3 4567
891011121314
15161718192021
22232425262728
2930     

Syndicate

RSS Atom

Most Popular Tags

Style Credit

Expand Cut Tags

No cut tags
Page generated Jun. 5th, 2025 02:28 pm
Powered by Dreamwidth Studios
OSZAR »