Maryland lawmakers demand accountability over Towson closure


Apple Towson employees. Credit: IAMAW

Maryland lawmakers have penned a delegation letter to Apple, asking the tech giant to ask if there were any other paths forward other than closing Apple Towson.

Apple’s battle with its Towson location continues, with Maryland lawmakers stepping in to “express serious concern” over Apple’s choice to close the store. On May 4, lawmakers penned a congressional delegation to Apple, which reads:

“We urge Apple to reconsider whether there are viable paths forward that would preserve jobs and maintain a retail presence in the region,” said the signing members in a letter to Apple.

“Maryland residents value employers who invest in their workforce and demonstrate a sustained commitment to the communities they serve,” the lawmakers said. “We stand ready to engage constructively with Apple to better understand this decision and to explore potential solutions.”

Lawmakers are asking Apple to explain the factors that led to the closure and what research it did on how the closure would affect the employees. It also wants to know what Apple plans to do to help employees who will soon lose their jobs.

The International Association of Machinists and Aerospace Workers (IAM) Union, along with Towson employees, has thanked lawmakers standing with workers.

What led to the charge in the first place

Apple recently announced that it would be closing three of its stores, Apple Trumbull, Apple North County, and Apple Towson. The Towson location was Apple’s first unionized store.

For its part, Apple cited declining conditions and the loss of retailers as the primary reasons for closing. But Towson employees, as well as the IAM Union, don’t think that’s the whole story.

That’s why in late April, IAM filed an unfair labor practice (ULP) charge against Apple. The union has suggested that the closure was retaliatory in nature.

However, the charge isn’t centered around the closing, but rather what happens next.

It claims that Apple unlawfully discriminated against unionized workers, denying them the same job placement rights that the non-unionized stores would receive. Trumbull and North County employees had the option to transfer to other locations.

Towson employees, on the other hand, were invited to apply for open roles at other stores, the same as any other non-employee seeking employment.

Apple would later go on to say that Towson’s union accepted specific rules for rehire under closure. If Apple were to open a new store within 50 miles, Towson would have right of refusal. Otherwise, Apple claims, the employees are to get severance pay only.

Apple’s history with Towson

While it’s not likely that Apple closed the store solely because of the union, it doesn’t mean that Apple didn’t reap the benefits, either. Apple hasn’t hidden the fact that it wants workers to avoid unionization.

The company had went out of its way to ensure that unionized stores didn’t receive benefits it conveniently rolled out while it stalled contract negotiations. Apple’s own retail chief Deirdre O’Brien had released a video directly telling employees that unionization was a net negative, and encouraged workers to seek in-house solutions.



Source link

Leave a Reply

Subscribe to Our Newsletter

Get our latest articles delivered straight to your inbox. No spam, we promise.

Recent Reviews


Vibe coding has taken the development world by storm—and it truly is a modern marvel to behold. The problem is, the vibe coding rush is going to leave a lot of apps broken in its wake once people move on to the next craze. At the end of the day, many of us are going to be left with apps that are broken with no fixes in sight.

A lot of vibe “coders” are really just prompt typers

And they’ve never touched a line of code

An AI robot using a computer with a prompt field on the screen. Credit: Lucas Gouveia / How-To Geek

Vibe coding made development available to the masses like never before. You can simply take an AI tool, type a prompt into a text box, and out pops an app. It probably needs some refinement, but, typically, version one is still functional whenever you’re vibe coding.

The problem comes from “developers” who have never written a line of code. They’re just using vibe coding because it’s cool or they think they can make a quick buck, but they really have no knowledge of development—or any desire to learn proper development.

Think of those types of vibe coders as people who realize they can use a calculator and online tools to solve math problems for them, so they try to build a rocket. They might be able to make something work in some way, but they’ll never reach the moon, even though they think they can.

Anyone can vibe code a prototype

But you really need to know what you’re doing to build for the long haul

For those who don’t know what they’re doing, vibe coding is a fantastic way to build a prototype. I’ve vibe coded several projects so far, and out of everything I’ve done, I’ve realized one thing—vibe coding is only as good as the person behind the keyboard. I have spent more time debugging the fruits of my vibe coding than I have actually vibe coding.

Each project that I’ve built with vibe coding could have easily been “viable” within an hour or two, sometimes even less time than that. But, to make something of actual quality, it has always taken many, many hours.

Vibe coding is definitely faster than traditional coding if you’re a one-man team, but it’s not something that is fast by any means if you’re after a quality product. The same goes for continued updates.

I’ve spent the better part of three months building a weather app for iPhone. It’s a simple app, but it also has quite a lot of complex things going on in the background.

It recently got released in the App Store—no small feat at all. But, I still get a few crash reports a week, and I’m constantly squashing bugs and working on new features for the app. This is because I’m planning on supporting the app for a long time, not just the weekend I released it, and that takes a lot more work.

Vibe coders often jump from app to app without thinking of longevity

The app was a weekend project, after all

A relaxed man lounging on an orange beanbag watches as a friendly yellow robot works on a laptop for him, while multiple red exclamation-mark warning icons float around them. Credit: Lucas Gouveia/How-To Geek | ViDI Studio/Shutterstock

I’ve seen it far too often, a vibe coder touting that they built this “complex app” in 48 hours, as if that is something to be celebrated. Sure, it’s cool that a working version of an app was up and running in two days, but how well does it work? How many bugs are still in it? Are there race conditions that cause a random crash?

My weather app has a weird race condition right now I’m tracking down. It crashes, on occasion, when opened from Spotlight on an iPhone. Not every time does that cause a crash, just sometimes.

If a vibe coder’s only goal is to build apps in short amounts of time so they can brag about how fast they built the app, they likely aren’t going to take the time to fix little things like that.

I don’t vibe code my apps that way, and I know many other vibe coders that aren’t that way—but we all started with actual coding, not typing a prompt.


Anyone can be a vibe coder, but not all vibe coders are developers

“And when everyone’s super… no one will be.” – Syndrome, The Incredibles. It might be from a kids’ movie, but it rings true in the era of vibe coding. When everyone thinks they can build an app in a weekend, everyone thinks they’re a developer.

By contrast, not every vibe coder is actually a developer, and that’s the problem. It’s hard to know if the app you’re using was built by someone who has plans to support the app long-term or not—and that’s why there’s going to be a lot of broken apps in the future.

I can see it now, the apps that people built in a weekend as a challenge will simply go without updates. While the app might work for the first few weeks or months just fine, an API update comes along and breaks the app’s compatibility. It’s at that point we’ll see who was vibe coding to build an app versus who was vibe coding just for online clout—and the sad part is, consumers will lose out more often than not with broken apps.



Source link