Meta is expected to begin cutting about 8,000 jobs this week as it pours more money into AI infrastructure and looks to "offset" other investments, with additional layoffs reportedly possible later this year. According to CNBC, the morale has worsened inside the company. "Internally, there's an emerging sense of dread across wide swaths of the company," the report says, citing current and former Meta employees. "That's in part because more cuts are expected this year, including a potential round of layoffs in August, followed by another round later in the year, some of the sources said." From the report: [...] Whatever anxiety investors are experiencing, the feelings inside the company are more intense, with some longtime staffers questioning Meta's AI pursuits under AI chief Alexandr Wang, while also weighing if now is the time to leave for opportunities at other companies in the AI race, according to current and former employees. Data aggregated by Blind, an anonymous professional network that requires users to verify their employment with a work email address, reveals some of the internal malaise. Meta's overall rating by employees on Blind has declined 25% from a peak in the second quarter of 2024 to the current period, with a 39% drop in its culture rating. In every category other than compensation, Meta has seen a ratings decline and dramatically underperforms rivals Amazon, Google and Netflix, the Blind data reveals. The company's full-court press with AI included the recent debut of an employee tracking tool intended to collect data from staffers' actions, such as mouse movements and keystrokes on their work computers. The Model Capability Initiative, or MCI, as it's called, is part of Meta's efforts to train AI models to power digital agents that can perform various coding and white-collar tasks. Employees have characterized the data tracking tool as "dystopian," according to messages viewed by CNBC, with some workers expressing fear that personal information could be leaked. Some Meta workers have noted that their workplace computers appear slower since the company initiated the project, adding to their frustration, sources said. Meta workers responded by creating an online petition that urges Zuckerberg and leadership to shutter the project. "Collecting and repurposing this kind of data raises serious concerns around privacy, consent, and trust in the workplace," the petition says. "It should not be the norm that companies of any size are permitted to exploit their employees by nonconsensually extracting their data for the purposes of AI training." Further reading: NYT: 'Meta's Embrace of AI Is Making Its Employees Miserable'

Read more of this story at Slashdot.

Stainless, a New York-based startup, founded in 2022, rose to prominence in the emerging AI industry for automating the creation and maintenance of software development kits, or SDKs — the libraries developers use to interact with APIs.

The fundamental value of multiplatform development with Flutter lies in building apps that support multiple platforms with just a single, shared source codebase, allowing developer teams to work in unison across all platforms.

This is crucial in an AI-driven world where enhanced consistency, reduced token usage, and fast market reach become vital. By maintaining a single codebase, builders can focus their AI assistants on one unified context, drastically reduce token overhead, and minimize AI hallucinations. Instead of asking AI to translate features across fragmented, platform-specific languages, builders can leverage AI to write it once in Dart and instantly deploy it everywhere.

The existing value proposition

Multiplatform development relies on enabling a single, shared source codebase. In our first-party Flutter apps, between 95% and 99% of the source code is shared. This massive code reuse unlocks several benefits:

• Faster time to market across multiple platforms because a team only needs to maintain one codebase.
• Guaranteed consistency across platforms, giving companies a single, consistent feature set to support across all their customers, regardless of their platform of choice.
• Native performance and stability because Flutter code is compiled to each platform’s native machine code.
• Semantic guardrails increase security because the Dart language is strongly typed.

The agentic value proposition

While LLMs are good at translating requirements into code, using them to build separate native apps for each platform scales poorly. Replicating features across different languages using LLMs multiplies generation time and token usage, and can quickly lead to implementations drifting apart.

Flutter’s single-source solution eliminates these problems. But beyond just code sharing, Flutter’s specific architecture makes it the ideal framework for agent-driven development. This emerging value proposition is driven by several key advantages:

• Token reduction: By generating your app once in Dart, you drastically reduce token overhead compared to using AI to translate features across platform-specific languages. This eliminates the need to replicate logic across different codebases, which scales poorly and multiplies token usage.
• Consistency: Flutter provides a unified experience because a single source codebase ensures the feature set remains identical across all platforms. This prevents platform drift that occurs when LLMs hallucinate and implementations drift apart.
• Self-correcting agents: Flutter has strong semantic guardrails due to Dart’s strongly typed language, and rich developer tooling. When an AI agent generates code, the strict type system, exposed through flexible tools and MCP servers, acts as an immediate feedback loop to catch errors instantly.
• Predictable code generation: LLMs excel at generating hierarchical, structured data. Flutter’s compositional, declarative UI aligns with this strength. It is much easier for an agent to reason about and reliably generate a single Dart widget tree than to manage the fragmented logic of other platform-specific frameworks.
• High-speed validation with Hot Reload: In an agentic workflow, the bottleneck is often verifying the AI’s output. Flutter’s hot reload feature provides a workflow where any change made by the agent is viewable instantly in the running app during development.

The Flutter advantage

Flutter’s support for a single shared codebase targeting multiple platforms, paired with a strongly typed language and powerful tooling, makes it a great companion to agent-driven development. In summary, the future looks bright! With Flutter, expect your agentically developed apps to result in low token usage, faster multi-platform development cycles, strong semantic guardrails, app consistency across platforms, and native performance. Happy building!

---

Flutter’s multiplatform value for agentic development was originally published in Flutter on Medium, where people are continuing the conversation by highlighting and responding to this story.

---

---

Topics covered in this episode:

• Using Django Tasks in production
• Co-authored with Claude?
• PyPI packages are increasing rapidly
• httpx2
• Extras
• Joke

Watch on YouTube

About the show

Sponsored by us! Support our work through:

• Our courses at Talk Python Training
• The Complete pytest Course
• Patreon Supporters Connect with the hosts
• Michael: @mkennedy@fosstodon.org / @mkennedy.codes (bsky)
• Brian: @brianokken@fosstodon.org / @brianokken.bsky.social
• Show: @pythonbytes@fosstodon.org / @pythonbytes.fm (bsky) Join us on YouTube at pythonbytes.fm/live to be part of the audience. Usually Monday at 11am PT. Older video versions available there too. Finally, if you want an artisanal, hand-crafted digest of every week of the show notes in email form? Add your name and email to our friends of the show list, we'll never share it.

Brian #1: Using Django Tasks in production

• Tim Schilling shares how the Djangonaut Space website has been using Django’s new tasks framework and some of the info missing from the official Django docs.
• Tasks require a third party package, django-tasks-db to actually run the tasks.
• Article walks through all changes necessary to get an email process running to notify admins of new testimonials. Cool simple example.
• With the db backend, you can monitor progress of tasks in the admin, to see which tasks are scheduled, completed, or have errors.
• Some wishes for the community to implement
  • new tutorial in the Django docs
  • Django Debug toolbar panel for tasks
  • test/mock backend
• Great title for wish list: Thinks I’d like to see, but I’m too lazy to implement myself.

Michael #2: Co-authored with Claude?

• Via Nik T.
• We don’t put “executed on macOS”, “edited with PyCharm”, etc. in our commits. Why Claude?
• Seems like a growth hack to me, that I don’t really care to participate in.
• Some projects that have formalized their thoughts on this: The Generative AI Policy Landscape in Open Source
• Adjust to turn off in ~/.claude/settings.json see the docs.

  {
     "attribution": {
        "commit": "",
         "pr": ""
     }
  }
  

Brian #3: PyPI packages are increasing rapidly

• Artem Golubin
• There’s been an increase of published packages per week on PyPI
• A pretty big increase in the last handful of months.
• 30% increase since 2025, clearly due to AI
• Artem is building hexora, a malicious Python code detector.
• Cool package too, it can:
  • Audit project dependencies to catch potential supply-chain attacks
  • Detect malicious scripts found on platforms like Pastebin, GitHub, or open directories
  • Analyze IoC files from past security incidents
  • Audit new packages uploaded to PyPi.
• Artem is using hexora to analyze recently published pypi packages and many are obviously vibecoded and trigger false positives for abuses of eval, exec, and subprocess
  • Side note: I don’t think that’s necessarily a false positive. Not malicious, but maybe a stupid-code-detector?
• Lots are LLM related, Lots have bots contributing code
• Publishing rate is crazy, dozens to hundreds of published versions in a day is a bug, not a feature
• Brian’s proposal, PyPI should limit releases per day for any package to something a sane human would do, even if they make a mistake on a release, to maybe like 2-3, definitely under 10, in a day. And if the repo has obvious agent contributors listed, maybe lower to the limit to 1-2 a day? Honestly, “move fast and break things” doesn’t apply to breaking the commons.

Michael #4: httpx2

• More on the httpx, httpxyz, etc changes: Pydantic people started their own fork, httpx2.
• Michiel says “while we think httpxyz was definitely needed, we welcome httpx2 and think it should be the ‘blessed’ fork.”
• Kludex, who is among other things maintainer of Starlette, was considering a fork
• As it stands, httpx2 is lacking the performance improvements they added to httpxyz. But it will not be long before they will add those, too.
• Also they already made some smart decisions:
  • they are switching from certifi to truststore
  • they are switching to compression.zstd on Python 3.14+, enabling zstd compression by default
  • they merged httpcore and vendored it in their repository
• Discussion on Hacker News

Extras

Brian:

• The Four Horsemen of the LLM Apocalypse - Anarcat
• Django/JetBrains 2026 developer survey is open
• Pyrefly 1.0 : “meaning we are confident that Pyrefly is ready for production use.” Michael:
• Just about ready to release Python Web Security: OWASP Top 10 with Agentic AI course. Be sure to be on the courses newsletter to get notified.

Joke: Proud Parents

Download audio: https://pythonbytes.fm/episodes/download/480/proud-parents.mp3