Visualização normal

Received before yesterdayAll Content from Business Insider

I was using Anthropic's Fable when it disappeared mid-project. It taught me a lesson about AI and business.

A man looking frustrated in front of a desktop computer
Business owner Sean McDonnell said he tries to remain prepared for unforeseen circumstances with using AI.

dikushin/Getty Images;

  • UK-based business owner Sean McDonnell relies on AI for his web design business and SaaS website.
  • The White House ordered Anthropic to cut foreign access to Fable 5 while McDonell was mid-task.
  • McDonnell emphasizes importance of backup plans due to AI tool disruptions like the Fable incident.

This as-told-to essay is based on a conversation with Sean McDonnell, 43, who lives in England. McDonnell is the founder of the web design company Kaizen and the SaaS website Consigns. The following has been edited for length and clarity.

Developing my website would not have been possible without AI.

I started my web design business earlier this year, which also led me to create a website that provides software to help companies track their waste. I run both of these ventures with my partner, and we enlist contractors for some operations and software development.

We're a small team, and AI tools are a big help. Last week, I saw a few posts online showing the amazing things that Anthropic's new Fable model can do.

I was keen to try this new technology, but didn't get much of a chance to use it. A few hours in, I was mid-task when the US government forced Anthropic to cut off foreign access to Fable with little to no notice.

The rug got pulled from under me pretty quickly, but because I was well-prepared, it didn't have a hugely disruptive impact on my business. It's a reminder that you can't rely too heavily on AI as a founder, and you should always have a backup plan in case of unforeseen circumstances.

I was keen to give Fable a try, but it was short-lived

I like using OpenAI's Codex for repetitive, code-intensive work, and Claude for tasks that help design the product's aesthetics. AI has been able to completely change the architecture of our codebase in a day, whereas a task like that would've taken a developer weeks to do manually.

After seeing so much about it online, I wanted to use Fable to conduct a full review of our product for safety and security flags. The model was in the middle of making some key changes to our codebase when it got shut off instantly with a notice saying, "Claude Fable 5 is currently unavailable."

I didn't realize until the next day that this had happened because the US government ordered Anthropic to block foreign access to the model. It's been a bit of a bummer, and I feel bad for the people at Anthropic for making a brilliant product and having the rug pulled from under them, too. I'm also quite annoyed we didn't get to do more with Fable. I think it could've propelled us so much further.

Being prepared helped us avoid a huge disruption

This isn't the first time we've had issues with using Claude. In the past, when we used Opus 4.6, it would stop mid-task because it hit the token limit so quickly. We didn't realize how token-heavy the tool was, and it left our codebase in a bit of a mess.

Because we'd learned this lesson with 4.6, we made sure we were more prepared for unforeseen circumstances with using AI.

When we started our product review last week, I asked Fable to create a guide that both Claude or other AI models could follow. This enabled us to pass the remaining tasks to other agents when we lost access to Fable. We passed some to Codex and others to Claude 4.8. If we hadn't been prepared this way, the Fable issue could've resulted in lots of work being out the window.

Fable getting pulled didn't have a major impact because we were ready for it, but it ruined our momentum. We're working on a deadline, and every minute counts, so delays like this can be quite disruptive.

Always have a plan B

This Anthropic incident has solidified my conviction that you can't depend completely on AI.

If the government were to shut off AI access completely, our business wouldn't end, because we've already built out our platform, but we are quite dependent on AI. A situation like that would likely increase our costs, partly because we'd have to switch to the old-school method of hiring developers.

In today's AI era, it's important to always have a plan B. Don't just rely on one AI tool. It's good to understand the strengths of different models.

Make sure you're documenting things as you go by keeping records that exist outside your AI tool. If Claude knows all about our code base, but it gets pulled tomorrow, would I be able to give that over to a developer? At this stage, I think I could, because I've been documenting everything as I go. It's a fail-safe.

A spokesperson from The White House told Business Insider, "The Trump administration is collaborating with AI industry leaders to balance cutting-edge innovation with national security concerns that affect both the United States and our allies."

Anthropic did not immediately respond to requests for comment.

Do you have a similar story to share? If so, you can reach out to one of the reporters at aapplegate@businessinsider.com and ccheong@businessinsider.com.

Read the original article on Business Insider

I'm an editor at Google. AI has taken over some of my work, but my humanities degree gave me an unexpected edge.

23 de Março de 2026, 06:11
A person with short pink hair looks at the camera in front of a bookshelf filled with novels.
Marie Pabelonio is an editorial lead at Google.

Courtesy of Marie Pabelonio

  • Marie Pabelonio, a Google editorial lead, graduated from college with an English degree in 2009.
  • She highlights the value of her English degree in adapting to AI's impact in the tech industry.
  • AI helps her meet deadlines and focus on the bigger picture, but a human touch is still essential.

This as-told-to essay is based on a conversation with Marie Pabelonio, a 38-year-old editorial lead at Google, based in the Bay Area. This story has been edited for length and clarity.

I've been at Google since 2019, and as a writer, I knew AI would affect my role.

Looking back on my career trajectory, it feels like nothing short of a miracle that I ended up where I am. I graduated with an English degree in 2009, right after the financial crisis, and I'm now an editorial lead in people operations at Google, where I co-lead a small team that drafts and editorializes about 4,500-plus pages of HR policies. I've used AI to automate processes, refine drafts, templatize, and meet deadlines that would be impossible otherwise.

At this point, anyone, regardless of whether they're a writer or not, has felt it: Is AI going to automate me? Is it going to eventually just replace my job? I don't think I work more or less because of AI; I just work very differently.

I was a humanities major and fell into Big Tech

The job market felt very volatile when I entered it, which I think a lot of young people entering the workforce today feel.

I didn't have a career plan. I was an English major because I loved reading and writing, and if I found a job where I could do that and build a specific skill set on top of it, I would be OK.

My first job was as a fact-checker for the publishing arm of an industrial supply company, and then I became a copywriter in the advertising and marketing space. In 2016, I moved from Chicago to the Bay Area and became an editor at Amazon's subsidiary, Goodreads. I stayed in the Bay Area and made my way to Google by 2019.

I wasn't surprised that AI changed my job right away

We've heard the word "unprecedented" so much in the last six years or so that nothing surprises me anymore, including AI.

My team works with stakeholders and policy designers to interpret and draft policies, whether they're return-to-office, hybrid work, or immigration policies. There are areas where AI is useful in our work, and the tool has helped us regain more strategic time by automating tactical parts of our process.

This includes training the AI on standard article structure, to include four sections like background, key details, process, and related resources, formatting consistencies, including where headlines, a bulleted list, or a table would be used, and five to seven non-negotiable details the user needs to know from the policy.

I think there's still a lot of room for that human touch in that process. Once I have the output, I spend my time on the more strategic pieces, like verifying tone and voice, determining whether the article actually achieves the user goal, and how it fits with the broader content strategy of other articles.

In our writing, the goal is to inject humanity and warmth as much as possible, especially when explaining human resources topics like an employee's health insurance, compensation, performance reviews, and career growth. AI can't do that by itself.

AI saved me when I had a tight deadline

Around the time we started using AI, I had a big project to update existing policies, and I was on a tight deadline. I spent a lot of time upfront strategizing about how I could use AI to accelerate my work and meet my goals.

To address the overwhelming number of first drafts, I used AI to template a structure for readability, created a checklist for tone, style, and quality, and because of that was able to focus more on streamlining stakeholder reviews to check for accuracy. I met my deadline with a few days to spare. This was when it clicked for me that AI was changing things in a huge way, when this deadline looked really impossible, and then it wasn't.

Still, there were many times I had to validate and tweak the outputs. I never felt I could use AI as my secretary and leave it alone to do whatever it wanted.

Studying the humanities gave me a particular edge in the AI job market

I think there will be more of a premium on how we think, not what we know.

When it comes to writing, it's about being able to articulate the reasons behind your choices. Why this phrase and not that? Why put this insight here and not there? There's a rationale behind your judgment.

In job interviews, the question of how you use AI at work will inevitably come up now, and your AI output is only as good as your input. Good writers can get better, but bad writers can get worse, and just because you're writing fluently doesn't mean you're writing well. Studying literature so closely helped me reflect more on questions instead of answers.

This is the time to brag about how you develop your own sound judgment and how you use that judgment in your AI inputs. As good as it is to develop hard skills, it's just as important, now more than ever, to focus on soft skills too.

Do you have a story to share about your writing job in tech or AI? Contact this reporter, Agnes Applegate, at aapplegate@businessinsider.com.

Read the original article on Business Insider

❌