#developer-relations — Public Fediverse posts

Your developer community now has members who cannot read your content.

AI coding agents integrate with your platform before a human writes a line. When they get it wrong, developers leave. No ticket. No post. Silently.

That gap has a name.

Agentic Relations.

https://agenticairelations.com

#DevRel #DeveloperRelations #AgenticRelations #AI

Do I have any developer relations people in my network? Is anyone, or your professional acquaintance looking for work as DevRel at a (EU) developer tooling start-up? #remote #devrel #developerrelations

Microsoft’s “Microslop” Discord Ban Backfires: What AI Builders Can Learn from This Epic Moderation Fail

2,644 words, 14 minutes read time.

The “Microslop” Catalyst: When Automated Moderation Becomes a PR Liability

The recent escalation on Microsoft’s official Copilot Discord server serves as a stark reminder that in the high-stakes world of generative AI, the community’s perception of quality is as vital as the underlying architecture itself. In early March 2026, what began as a routine effort to maintain decorum within a product-support hub rapidly spiraled into a live case study of the Streisand Effect. Reports from multiple industry outlets confirmed that Microsoft had implemented a blunt, automated keyword filter designed to silently delete any message containing the term “Microslop.” This derogatory portmanteau has been increasingly used by developers and power users to describe what they perceive as low-quality, intrusive, or “sloppy” AI integrations within the Windows ecosystem. While the corporate intent was likely to prune what a spokesperson later categorized as “coordinated spam,” the execution triggered a tidal wave of digital civil disobedience. Instead of silencing the critics, the automated system provided a focal point for them, validating the sentiment that the tech giant was more interested in brand preservation than addressing the technical grievances that birthed the nickname.

Analyzing the root of this frustration reveals that the term “slop” is often an emotional reaction to a very real technical burden placed on the developer community. For instance, attempting to upgrade a SharePoint Framework (SPFx) project from version 1.14.x to the recently released 1.22.x is frequently described by those in the trenches as a “blood bath” of error messages and cryptic warnings. The transition is not merely a version bump; it is an overhaul of the build toolchain that often leaves developers debugging deep-seated errors that appear to stem from AI-generated or “slop-induced” bugs within M365 and community plug-ins. When a developer spends three days chasing an error only to find it buried in a low-quality, automated code suggestion or a poorly integrated community tool, the “Microslop” label stops being a joke and starts being an accurate description of a broken workflow. This disconnect between Microsoft’s “AI-first” marketing and the gritty, error-prone reality of its development frameworks is precisely why a simple keyword filter was never going to be enough to contain the community’s mounting resentment.

The Streisand Effect: How Censorship Becomes a Signal

The failure of the “Microslop” ban is a textbook example of how heavy-handed moderation can amplify the very information it seeks to suppress. In the context of AI builders, this incident highlights the danger of using automated tools to sanitize discourse, as it inadvertently creates a “badge of resistance” for the user base. Every bypassed filter and every subsequent ban on the Copilot Discord became a signal to the broader industry that there was a significant rift between Microsoft’s narrative of AI “sophistication” and the community’s lived experience with the product. Furthermore, by escalating from keyword filtering to a full server lockdown, Microsoft effectively confirmed the power of the “Microslop” label. This elevated the term from a minor annoyance to a headline-grabbing symbol of corporate insecurity, demonstrating that the more a corporation tries to hide a piece of information, the more the public will seek it out and amplify it.

This phenomenon is particularly dangerous for AI-centric companies because the technology itself is already under intense scrutiny for its reliability and ethical implications. If a builder cannot manage a community hub without resorting to blunt-force censorship, it raises uncomfortable questions about how they manage the more complex, nuanced guardrails required for the Large Language Models (LLMs) themselves. The internet rarely leaves such attempts at suppression unpunished; in this case, the ban led to the creation of browser extensions and scripts specifically designed to spread the nickname across the web. This demonstrates that in 2026, community management is no longer just an administrative task; it is a critical component of brand integrity that requires a much more sophisticated approach than a simple “find and replace” blocklist. Builders must recognize that transparency is the only effective dampener for the Streisand Effect, as any attempt to use automation to hide dissatisfaction only serves to validate the critics.

Why the “Slop” Narrative Resonates: The Technical Quality Gap

At the heart of the “Microslop” controversy lies a deeper, more substantive issue regarding the growing perception that AI integration has entered a period of diminishing returns, often referred to as the “slop” era. The term “slop” gained significant cultural weight after major linguistic authorities and industry analysts began using it to specifically define the flood of low-quality, mass-produced AI content clogging the modern internet. When users apply this term to a tech giant, they are not merely engaging in schoolyard insults; they are expressing a technical frustration with the way generative AI features have been integrated into a legacy operating system. Analyzing the user feedback leading up to the Discord lockdown reveals a clear pattern of “quantity over quality” in the deployment of Copilot. Developers and power users have documented numerous instances where AI components were perceived as being forced into core OS functions like Notepad, File Explorer, and Task Manager, often at the expense of system latency and overall stability.

This quality gap is precisely what gave the “Microslop” nickname its viral potency, as it hit upon a verifiable truth regarding the current state of the software. If the AI integration were universally recognized as seamless, high-value, and technically flawless, the derogatory label would have failed to gain traction among the engineering community. However, because the term captured a widespread sentiment that the software was becoming bloated with unrefined, “sloppy” code that prioritizes corporate AI metrics over actual user utility, the attempt to ban the word felt like an attempt to ban the truth itself. For AI builders, this serves as a critical warning that one cannot moderate their way out of a fundamental quality problem. If a community begins to categorize a product’s output as “slop,” the correct response is not to update the server’s AutoMod settings to include the word on a prohibited list; the solution is to re-evaluate the product roadmap and address the technical regressions causing the friction.

Root Cause Analysis: The Failure of Brittle Automation in Community Governance

The technical root cause of the Discord meltdown can be traced back to the implementation of “naive” or “brittle” automation—a common pitfall for organizations that treat community management as a purely administrative task. Microsoft’s moderation team relied on a basic fixed-string match filter, which is the mos

Furthermore, the automation failed to account for context, which is the most vital component of any successful moderation strategy. The bot reportedly flagged every instance of the word “Microslop,” regardless of whether the user was using it as an insult, asking a question about the controversy, or providing constructive criticism. By labeling a corporate nickname with the same “inappropriate” tag usually reserved for hate speech or harassment, the automated system actively insulted the intelligence of the user base. This lack of nuance in the AI-driven moderation stack created a pressure cooker environment where every automated deletion was viewed as an act of corporate censorship. For AI builders, the lesson is that any automation deployed for community governance must be as sophisticated as the product it supports. Relying on 1990s-era keyword filtering to manage a 2026-era AI community is a recipe for disaster, as it signals a lack of technical effort that only further reinforces the “slop” narrative the organization is trying to escape.

The Strategic Shift: Moving Beyond Blunt Force Suppression

The failure of the “Microslop” ban highlights a critical strategic inflection point for AI builders who must navigate the increasingly volatile waters of developer communities. Relying on blunt-force suppression as a first-line defense against product criticism is a strategy rooted in legacy corporate communication models that are incompatible with the transparent, decentralized nature of modern technical hubs. When a tech giant attempts to scrub a derogatory term from its digital ecosystem, it effectively abdicates its role as a collaborator and assumes the role of an adversary. This shift in posture is particularly damaging in the context of generative AI, where the success of a platform like Copilot is heavily dependent on the feedback loops and integrations created by the very developers who feel alienated by such heavy-handed moderation. Instead of viewing these “slop” accusations as a nuisance to be silenced, sophisticated AI organizations should view them as high-fidelity data points indicating where the gap between marketing hype and functional utility has become too wide to ignore.

Consequently, the move toward resilient community management requires a transition from “policing” to “pivoting.” Analyzing the fallout from the March 2026 lockdown reveals that the most effective way to neutralize a pejorative nickname is to address the technical deficiencies that gave the name its power. For instance, if users are labeling an AI integration as “slop” due to high latency, resource bloat, or inconsistent output, the strategic response should involve a public-facing commitment to performance benchmarks and a transparent roadmap for optimization. By engaging with the substance of the criticism rather than the semantics of the label, a builder can naturally erode the legitimacy of the mockery. Microsoft’s decision to hide behind a locked Discord server suggests a lack of preparedness for the “friction” that inevitably accompanies the rollout of transformative technologies. To avoid this pitfall, builders must ensure that their community teams are empowered with technical context and the authority to translate community outrage into actionable product requirements, rather than being relegated to the role of digital janitors tasked with sweeping dissent under the rug.

Building Resilience: Lessons in Context-Aware Governance

For AI startups and established enterprises alike, the “Microslop” debacle provides a definitive masterclass in the necessity of context-aware governance. The primary technical takeaway is that community moderation in 2026 must be as intellectually rigorous as the models being developed. A sophisticated governance stack would utilize sentiment analysis and intent recognition to differentiate between a user engaging in harassment and a user expressing a legitimate, albeit sarcastically phrased, grievance. By failing to integrate these more nuanced AI capabilities into their own moderation tools, Microsoft inadvertently signaled a lack of confidence in the very technology they are asking the world to adopt. If an AI leader cannot trust its own systems to handle a Discord meme without resorting to a total server blackout, it becomes significantly harder to convince enterprise clients that the same technology is ready to handle mission-critical business logic or sensitive customer interactions.

Furthermore, building a resilient community requires a fundamental acceptance of the “ugly” side of product development. In the age of social media and rapid-fire developer feedback, mistakes will be memed, and failures will be christened with catchy, derogatory nicknames. Attempting to legislate these memes out of existence is a losing battle that only serves to accelerate the Streisand Effect. Instead, AI builders should focus on creating “high-trust environments” where users feel that their feedback—no matter how unpolished or “sloppy” it may be—is being ingested as a valuable resource. This involves maintaining open channels even during a PR crisis and resisting the urge to implement “emergency” filters that treat your most vocal users like hostile actors. By prioritizing stability, transparency, and technical excellence over brand hygiene, organizations can transform a potential “Microslop” moment into a demonstration of corporate maturity and a commitment to long-term product quality.

From Damage Control to Product Discipline: Reclaiming the Narrative

The ultimate fallout of the Microsoft Discord lockdown serves as a definitive case study in why AI builders must prioritize technical discipline over narrative control. When a corporation attempts to “engineer” a community’s vocabulary through restrictive automation, it inadvertently signals a lack of confidence in the underlying product’s ability to speak for itself. Analyzing the broader industry trends of 2026, it becomes clear that the “slop” label is not merely a social media trend but a technical critique of the current state of LLM integration. For a developer audience, the transition from “Microsoft” to “Microslop” in common parlance was a direct reaction to perceived regressions in software performance and the intrusion of non-essential AI telemetry into stable workflows. By focusing on the removal of the word rather than the remediation of the code, Microsoft missed a critical opportunity to demonstrate the “sophistication” that CEO Satya Nadella has publicly championed. Builders must realize that in a highly literate technical ecosystem, the only way to effectively kill a derogatory meme is to make it irrelevant through superior engineering and undeniable user value.

Furthermore, the “Microslop” incident underscores the necessity of a unified strategy between product engineering and community management. In many large-scale tech organizations, these departments operate in silos, leading to situations where a community manager implements a blunt-force keyword filter without realizing it contradicts the broader corporate message of AI-driven nuance and intelligence. This strategic misalignment is what allowed a minor moderation decision to balloon into a global PR crisis that dominated tech headlines for a week. To build a resilient AI brand, organizations must ensure that their automated governance tools are reflective of their core technological promises. If your product is marketed as an “intelligent companion,” your moderation bot cannot behave like a primitive 1990s-era blacklist. Moving forward, the industry must adopt a “feedback-first” architecture where automated tools are used to categorize and elevate user frustration to engineering teams, rather than acting as a digital firewall designed to protect executive sensibilities from the harsh reality of user sentiment.

Conclusion: The Lasting Legacy of the “Slop” Era

The March 2026 Discord lockdown will likely be remembered as the moment “Microslop” transitioned from a niche joke to a permanent fixture of the AI era’s vocabulary. Microsoft’s attempt to use automated moderation as a shield against criticism backfired because it ignored the fundamental law of the digital age: the more you try to hide a grievance, the more you validate its existence. For those of us building in the AI space, the lessons are clear and uncompromising. We must build with transparency, moderate with context, and never mistake a blunt-force keyword filter for a comprehensive community strategy. If we want our products to be associated with innovation rather than “slop,” we must earn that reputation through technical excellence and genuine engagement, not through the silent deletion of our critics’ messages. In the end, Microsoft didn’t just ban a word; they inadvertently launched a movement, proving that even the world’s most powerful tech companies remain vulnerable to the power of a well-timed, nine-letter meme and the undeniable force of the Streisand Effect.

Call to Action

If this breakdown helped you think a little clearer about the threats out there, don’t just click away. Subscribe for more no-nonsense security insights, drop a comment with your thoughts or questions, or reach out if there’s a topic you want me to tackle next. Stay sharp out there.

D. Bryan King

Sources

• PCMag: Microsoft Effort to Ban ‘Microslop’ on Copilot Discord Didn’t Go As Planned
• Windows Latest: Microsoft Locks Copilot Discord After Moderation Backlash
• Futurism: Microsoft Bans “Microslop” on Discord, Gets So Humiliated It Locks Server
• Gizmodo: Microsoft Bans Term ‘Microslop’ From Official Discord Server
• PC Gamer: Microsoft banned the word ‘Microslop’ in its Copilot Discord server
• It’s FOSS: Microsoft Locks Down Discord Server Over “Microslop” Posts
• Slashdot: Microsoft Bans ‘Microslop’ On Its Discord, Then Locks the Server
• Ground News: Microsoft Locks Down Discord Server After Microslop Ban Backfires
• Mysterium VPN: Microsoft Banned “Microslop” on Discord, Then Panicked
• Kotaku: Flood Of ‘Microslop’ Messages Forces Microsoft’s Official Copilot AI Discord Into Lockdown
• WinBuzzer: Microsoft Bans ‘Microslop’ on Discord, Locks Server After Backlash
• NIST: AI Risk Management Framework
• CISA: Secure by Design Principles for AI

Disclaimer:

The views and opinions expressed in this post are solely those of the author. The information provided is based on personal research, experience, and understanding of the subject matter at the time of writing. Readers should consult relevant experts or authorities for specific guidance related to their unique situations.

Related Posts

Rate this:

"Over the years, we’ve had the pleasure of hosting many exceptional speakers on the Nordic APIs stage. Our most memorable talks span architectural deep dives, anti-patterns, emerging trends, personal journeys, and hard-earned lessons on what it takes to build great API platforms.

To the audience, these presentations often look effortless. But the truth is, there’s a lot of preparation that goes on behind the scenes. This is especially true for the talks that resonate with the audience the most. So what separates an average tech talk from a standout one?

We checked in with a few of our most well-regarded speakers to pull the curtain back on their process, from originating an idea, all the way through to rehearsing it and nailing it with confidence on the day. The result is a set of practical tips for crafting tech talks that land. While the tips come from the API community and are geared toward tech talks, much of the wisdom applies to any public speaking engagement, whether you’re a first-time speaker or industry veteran.

And if reading these conference speaking tips leaves you inspired to take the stage yourself, we’d love to hear from you. Consider submitting a talk proposal for Platform Summit."

https://nordicapis.com/10-tips-on-giving-standout-talks-at-developer-conferences/

#DeveloperRelations #DeveloperExperience #DX #Presentations #TechnicalCommunication #APIs

Did we get ahead of ourselves by focusing purely on Generative AI before perfecting the robust data fundamentals that the best AI workloads are built on? 🤔

My keynote from @allthingsopen "AI Should Not Replace Well-Built Data Fundamentals," argues that true AI innovation comes from workloads built ON TOP of strong data fundamentals, not in place of them.

I dive into how you can use AI tools (like #GeminiCLI) alongside foundational #OpenSource tools (like ASF's #Iceberg) to establish the essential scalability, flexibility, and interoperability required for modern, large-scale AI success.

You can't have an effective AI strategy without a well-built data strategy.

Watch the full talk here: https://youtu.be/y4Hp5mEtukg

#DataEngineering #AI #GenAI #ApacheSoftwareFoundation #DeveloperRelations

Reflections on 2 Years Running Developer Relations

https://databased.pedramnavid.com/p/reflections-on-2-years-running-developer

#HackerNews #Reflections #DeveloperRelations #TwoYears #TechCommunity #Growth

This writeup by @pedramnavid.com is easily one of my favourite texts on DevRel (and the mythological reference didn't go unnoticed) Central argument: DevRel is just Marketing, for developers, with a feedback loop to the product. Do you agree? #devrel #developerrelations

Reflections on 2 Years Running...

#LinuxFoundation Announces the Formation of the #DeveloperRelations Foundation

https://www.linuxfoundation.org/press/linux-foundation-announces-the-formation-of-the-developer-relations-foundation

She is Still Looking For Work - Celeste Seberras, Tech Writer / Content Strategist / Developer Relations with a Infosec and entrepreneurial background. http://resume.hakr.gg http://lnkd.in/gYRfjTcB #AI #Blockchain #Infosec #Cybersecurity #TechnicalWriting #developerrelations

The AAARRRP #DeveloperRelations #Strategy Framework

https://www.leggetter.co.uk/aaarrrp/

A great read for anyone who isn't sure about what value #DevRel really has at an organization.

> What value is DevRel bringing? DevRel is the only team at your company that can speak the engineer’s language, provide regular feedback to the product team, function as a marketing team, and grow the community as the face of your company.

https://buff.ly/4bncBXu

#tech #developerrelations #developeradvocate #communitybuilding #marketing #developermarketing #devmar

As of January, I was effectively laid off from my loved Developer Advocate job.

If anyone needs a Swiss army knife with excellent soft skills that work well in a team. That's me.

I would prefer Softwarearchitecture and DevRel again. Everything where I get to work with people would be nice.

If anyone can point me to something or could make an introduction, I would be deeply grateful!

Location: Remote, hybrid (Würzburg and/or train reachable)

#FediHire #DeveloperRelations #Softwaredevelopment

🚀 NEW on We ❤️ Open Source 🚀

From #Fintech to #DevRel, Angie Jones shares how AI & open source empower developers! 🤖 Learn about JWTs, AI-generated content, and her passion for simplifying complex tech.

Watch now: https://buff.ly/3DbgBwU

#WeLoveOpenSource #AI #DeveloperRelations

You probably shouldn't hire a Developer Advocate yet

https://lengrand.fr/you-probably-shouldnt-hire-a-developer-advocate-yet/

#developerrelations #developerexperience #developerexperience

Don’t miss out—grab a coffee and listen in as we dive into Brian’s journey and what Open Sauced is cooking up next: https://voxgig.com/podcast/brian-douglas-2-founder-ceo-open-sauced
#TechPodcast #OpenSource #DevTools #FiresideWithVoxgig #AI #CodeQuality #devrel #developerrelations

@jessie is one of my favourite people in the world - and she has some additional time in her schedule for #DevOps #DeveloperRelations #OpenSource #Strategy work - so if that's the skillset you need, she's the person you want.

#FediHired

https://mastodon.social/@jessie/113040335595143377

One of my freelance roles at the moment is as Developer Relations lead on the Mastodon project. It is a project and platform I’m really passionate about – I use it every day, it is Open Source and based on an open standard, and I strongly feel that federated platforms like this are the key to enabling everyone to own their own content, networks, and experiences beyond the direct reach of commercial interests.

At this stage in its history, Mastodon would I think count as an established and mature OSS project. It has been around since 2016, there are over 10,000 running instances / servers with the software, and over a million regular active users of the platform (plus, it interoperates with a much wider set of other platforms in the Fediverse, and carries posts and content from them as well). There are a number of large repositories that make up the GitHub organisation. There’s a – in my opinion – healthy and diverse set of third party apps that plug in to the network.

One of the things that some folks would say that the project has not always been great at, is communicating with the broader developer community. My own observation is that this is a large and widely-deployed codebase, and at a certain scale, stability and reliability become paramount, and it can be less straightforward to accept pull requests for new features (over prioritising security reports, for example). It is a small team supporting this project, largely underfunded1 if you look at the need to maintain the code, and to pay at least some of the folks involved to work on things full-time so that they can get by day-to-day, and that the core functionality gets the attention it deserves. When you’re coding, you may not have time to do other things like writing documentation, discussing roadmaps, and answering general questions – that’s partly where I come in, but even then, I still need to get help from the core developers to understand some of the questions…

I started working part-time with the core Mastodon team last year, with the goal to improve the experience for developers building on the platform, and also to bring my experience in working with diverse OSS projects and communities to support the Mastodon core team. As an example, last year I overhauled the existing list of known third party API libraries on the documentation site, and also updated the third party client apps page. Towards the start of this year, we started to make a few choices to improve the cadence and – I hope – quality of our external conversations further: we brought the whole team to meet the community at FOSDEM for the first time, for instance, which was a big step for the project.

Visit us at #FOSDEM, building H, level 1! You can say hi to our team or tell us what you’d like to see in Mastodon next. Mugs, t-shirts, enamel pins, and even free stickers available! #Merchtodon

— Mastodon (@Mastodon) 2024-02-03T08:56:41.576Z

Eugen and I also had the opportunity to meet with a few folks working on related Fediverse projects, as well as some Mastodon contributors and instance owners, during a whirlwind visit to the Bay Area back in May.

In the last 4 months, Renaud (Mastodon’s CTO) and I have been collaborating on an engineering blog series called Trunk & Tidbits. We both strongly believe that explaining what we are working on is an important element in building greater engagement and community around the project. I chose the title for the series as (what I thought was) a clever play on words, but maybe you need to be old enough to remember when source control systems like CVS used “trunk” as in tree trunk as terminology, that we now tend to call “main” in the world of Git! The name is supposed to point to the blog series content being about what we have worked on and merged into the trunk of the code, and some “tidbits” or bits and pieces of other news from around the developer community – plus, of course, our mascot The Mastodon has a trunk of its own… 🦣 😄

Here are links to the April, May, and June posts, if you missed them and want to catch up. We post retrospectively, looking back at progress each month.

One thing to note from these past editions is that I also posted a completely rewritten and overhauled Contributing guide in the past couple of months (mentioned in Trunk & Tidbits); this lives at the organisation-level in our GitHub setup, and is intended as the main starting point if you want to contribute to the code.

Today, we published the July edition of Trunk & Tidbits. tl;dr we’re a bit behind where we had hoped to be towards releasing the next version of Mastodon, v4.3 – but we are really close to getting the beta out, and the “delay”2 is because of some feedback and performance improvements identified in early testing on our own instances, so we’re hoping that when the beta is released, things should be in pretty good shape.

I’m hoping that with more regular communications via the blog; interactions with the community via the Fediverse itself and at events (I’ll once again be at Fediforum in September, for example); one-to-one conversations; and a willingness to engage in more discussions where time and resources allow – we can help folks to feel more informed about what we’re working on. It is still a small core team, and it is a busy time as the Fediverse grows… we need to keep things running, stable, and reliable… and there are always going to be features and changes that we cannot get to, or requests we cannot support at short notice… but I can assure you that it is a team effort, we discuss what’s possible, and that, I believe, we’re moving things forward3.

That’s all a personal perspective on what I’ve found, in working with the Mastodon project and team. Let me know if you have feedback on the Trunk & Tidbits series, as I’d love to keep improving these posts, and learning from the folks that read them.

1. I am also pretty happy with the fact that the project has made a conscious decision to not go down a road of accepting capital investment, and remains a not-for-profit funded by donations. YMMV, this is a personal opinion. ↩︎
2. Note “delay” against an undated release schedule; the release will ship when it is ready to ship. ↩︎
3. A footnoted mea culpa / things I personally wish were better if I had more time on the project / there was more scope for them more quickly! I’d prefer it if there was a machine-parseable API specification, and that more Fediverse formats / standards / protocols might be supported in future, and that the developer documentation was even more complete and nicer and better etc etc.. Hopefully, we’ll get nearer to some of those in the future, as time and resources allow. ↩︎

Like it? Share it -

• Click to share on Mastodon (Opens in new window)
• Click to share on Threads (Opens in new window)
• Click to share on Bluesky (Opens in new window)
• Click to share on LinkedIn (Opens in new window)
• Click to share on Facebook (Opens in new window)
• Click to email a link to a friend (Opens in new window)

https://andypiper.co.uk/2024/08/13/the-trunk-line/

#Blaugust2024 #100DaysToOffload #activitypub #Coding #community #developerRelations #developers #devrel #fediform #fediverse #mastodon #openSource #oss #projectManagement #trunkTidbits

Today, I received some fun post from some lovely people in New York City.

Those in the know, may recognise these stickers as the logos of Glitch and Fastly.

I’ve been using Glitch to write and host web apps for quite a few years now – it is super helpful when working in a role like developer relations, needing to rapidly spin up demos, examples, or to demonstrate new features. A couple of years ago, Glitch came together with Fastly, and in the past couple of months their new developer platform vision really started to come together.

If you haven’t been keeping up with what they have been up to, and were not able to be at their recent special developer event in NYC (don’t worry, I couldn’t get there either), there’s a helpful ~6 minute video that summarises the announcements. I’m particularly interested and excited about this because I know and respect the folks involved – Anil Dash, Jenn Schiffer, Hannah Aubry, many others across their teams – and I know that they get and they care about developer experience, Open Source, and the free and open web. I’m talking about the big stuff, the infrastructure, the stuff that needs to invisibly just work in order for the web to run; and also the smaller things, the quirky indie little pieces, the fun and new experiences, helping people to learn to code and to be creative. It’s no exaggeration to say that Fastly’s Fast Forward program is a massive supporter of Open Source, open standards and the Fediverse. All of these things are reasons why I love Glitch & Fastly.

I’ve been running my main profile links page on Glitch in Bio for several years now (it’s a bit like a Linktree/link in bio page, but better than one of those closed platforms). Beyond that, I also host some Fediverse examples such as my own Postmarks instance, and a gallery of examples of Mastodon embeds; and also pages that add resources to my recent talks. With Fastly, I can also run things on my own domains, and make sure that things are cached and perform well.

[ if you’re curious about the sorts of things I’ve been building or working on from a code and web perspective, I’ve also spruced up my GitHub bio, and I have a more general gallery page on GitHub that has links to the source and deployments of different projects – some of which are links to those Glitch apps above ]

Thank you for the stickerage, Glitch friends! And, congratulations on the new Fastly Developer Platform! I’m looking forward to continuing to use your cool technologies 👍🏻

Like it? Share it -

• Click to share on Mastodon (Opens in new window)
• Click to share on LinkedIn (Opens in new window)
• Click to share on Facebook (Opens in new window)

https://andypiper.co.uk/2024/07/24/glitchy-love/

#100DaysToOffload #Coding #developerExperience #developerRelations #devrel #fastly #glitch #stickers #Technology #webapps

I’ve been a regular podcaster for, wow, around 15 (!) years now. More or less…[1]

After some occasional guest appearances early in the run of on a show called “Dogear Nation”, back in 2009 I moved up to a regular slot as a co-host, with my friends (and, at that time, IBM colleagues) Michael Martine and Michael Rowe. That show ran for 200 episodes in total, and then after a short break, the same group of folks (more or less) rebooted as Games at Work dot Biz… and we just released episode 473 of that podcast. There’s no special milestone number there apart from the fact that that’s a lot of weeks we’ve been recording, I was just inspired to mention it on my blog since it hasn’t come up for a long time!

We record Games at Work dot Biz together weekly on a Friday, and release on the Monday. Each week, we talk about what’s new in tech, running through stories and links shared in the preceding week by our listeners and also amongst the three of us co-hosts. We originally focused on the intersection of gaming technology and business productivity tools, but have a broad perspective across all things collaborative, social, immersive, and more (plus, LEGO, because, that’s always cool…!).

You can find us on all podcasting apps – here’s a handy jumping off page to your platform of choice, thanks to Episodes.fm which is a really neat way to reach a podcast on your preferred app. We’re currently having a bit of a challenging time getting all three of us together to record at once, but that’s OK – life happens, and there are different dynamics and topics we tend to get into, depending on which of us is reviewing the week’s links!

I also want to give a shout out to Michael and Michael – two dear friends I’m grateful to have made, with connections we’ve maintained, through all these years. They’ve been huge supporters of the things I’ve done, and I appreciate these two humans a lot. I recorded a solo episode of the podcast back in November with a “Thanksgiving” moment, saying the same thing. Thank you, guys!

If you’re interested, I also sometimes pop up in the monthly Techgrumps shows, although that tends to be determined much more by availability – always a fun one, though, so worth checking out if you want to listen to a bunch of folks getting grumpy / cynical about tech! I’ll try to get back to that one sometime soon.

Finally, I’m also always delighted to be invited to be a guest on other shows! Recently, I’ve recorded a couple – only one of them is available right now, and the other one will arrive when it’s ready! This was a panel conversation about Developer Relations in Open Source – you can find that in audio form as well, or a video is available to watch on YouTube if you prefer.

https://www.youtube.com/watch?v=4oeRxM1X4U4

[1] well, I’m being a little inaccurate here, as there was a whole swathe of time when I wasn’t able to take part in Games at Work dot Biz, so I (re?)-joined the Michaels as a co-host some way into the run! However, I was also occasionally guesting on the Ubuntu UK Podcast back then. It’s complicated!

Like it? Share it -

• Click to share on Mastodon (Opens in new window)
• Click to share on Threads (Opens in new window)
• Click to share on Bluesky (Opens in new window)
• Click to share on LinkedIn (Opens in new window)
• Click to share on Facebook (Opens in new window)
• Click to email a link to a friend (Opens in new window)

https://andypiper.co.uk/2024/07/22/podcast-adventures/

#100DaysToOffload #audio #developerRelations #devrel #dogearNation #gamesAtWorkDotBiz #interview #media #openSource #podcast #podcasting #techNews #techgrumps #YouTube

Automation Advocates Meetup time again for January. You know what that means?

Correct -> Another sketchnote from Dylan Pierce talk about "Replacing your Smoke Test Selectors with AI.

Enjoy!

#AutomationAdvocates #Meetup #Sketchnote #DevRel #DeveloperRelations

One of the most painful aspects of DevRel is witnessing all the opportunities lost 🎋

#DeveloperRelations