<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:dc="http://purl.org/dc/elements/1.1/">
  <channel>
    <title>DEV Community: AllRox</title>
    <description>The latest articles on DEV Community by AllRox (@allrox).</description>
    <link>https://dev.to/allrox</link>
    <image>
      <url>https://media2.dev.to/dynamic/image/width=90,height=90,fit=cover,gravity=auto,format=auto/https:%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Fuser%2Fprofile_image%2F2430828%2F898d7ade-6447-48f6-bcd6-85190163f819.jpg</url>
      <title>DEV Community: AllRox</title>
      <link>https://dev.to/allrox</link>
    </image>
    <atom:link rel="self" type="application/rss+xml" href="https://dev.to/feed/allrox"/>
    <language>en</language>
    <item>
      <title>Lex Sentinel: what I learned taking an AI legal monitor from its first client to its second</title>
      <dc:creator>AllRox</dc:creator>
      <pubDate>Tue, 10 Nov 2026 15:03:15 +0000</pubDate>
      <link>https://dev.to/allrox/lex-sentinel-what-i-learned-taking-an-ai-legal-monitor-from-its-first-client-to-its-second-lbl</link>
      <guid>https://dev.to/allrox/lex-sentinel-what-i-learned-taking-an-ai-legal-monitor-from-its-first-client-to-its-second-lbl</guid>
      <description>&lt;p&gt;&lt;strong&gt;How Lex Sentinel monitors public legal sources, why its AI is selective, and what broke when it stopped serving a single client&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;&lt;a href="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Fip6b15rw0cwbl5rjmdc9.jpg" class="article-body-image-wrapper"&gt;&lt;img src="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Fip6b15rw0cwbl5rjmdc9.jpg" alt="Two connected AI network hubs in a courtroom, representing Lex Sentinel's expansion" width="800" height="447"&gt;&lt;/a&gt;&lt;br&gt;
&lt;strong&gt;Lex Sentinel&lt;/strong&gt;, the legal monitoring service I build, now serves judges' associations in two Brazilian states, Rio de Janeiro and São Paulo. The São Paulo deployment was the first that required adapting the platform to a set of sources different from the one it was born with.&lt;/p&gt;

&lt;p&gt;This post is not the announcement. It is the product from the inside: the problem, the architecture decisions, and what changed when it stopped serving a single client.&lt;/p&gt;

&lt;h2&gt;
  
  
  The problem
&lt;/h2&gt;

&lt;p&gt;Judges' associations need to know, ahead of time, what is going to be judged, voted on or published that affects their members. That information is scattered across courts, judicial councils and legislative houses, each with its own format, calendar and publishing rhythm.&lt;/p&gt;

&lt;p&gt;Done by hand, it is a daily routine of opening websites, comparing against what has already been seen, and hoping not to miss an extraordinary session agenda or a late amendment.&lt;/p&gt;

&lt;h2&gt;
  
  
  The flow at a high level
&lt;/h2&gt;

&lt;p&gt;&lt;a href="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Fxx7ggw5w2lxeb9gwkqba.png" class="article-body-image-wrapper"&gt;&lt;img src="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Fxx7ggw5w2lxeb9gwkqba.png" alt="Lex Sentinel flow: public sources are checked every ~30 minutes, collected, filtered to new items, routed to AI analysis or a direct link depending on the source, delivered by email, WhatsApp and Telegram, and confirmed by a daily verification report" width="800" height="1438"&gt;&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;Four principles shape the design:&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;1. Only what is new triggers an alert.&lt;/strong&gt; The value of the service lies in what has changed. Re-sending what the recipient already got trains people to ignore alerts, and an ignored alert is worse than no alert.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;2. Silence also has to be proven.&lt;/strong&gt; If nothing arrived, was it because nothing changed or because the monitor broke? That is why there is an end-of-day report confirming each source was checked, with or without news, plus a public status page.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;3. You don't own the source.&lt;/strong&gt; Public websites change structure, go offline and publish late without notice. The system has to treat this as the normal state, not as an exception: detect the break, flag it, and make it quick to adapt the monitor.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;4. A managed service, not a tool.&lt;/strong&gt; The association operates nothing. It receives information. All configuration lives on the operator's side.&lt;/p&gt;

&lt;h2&gt;
  
  
  The most counterintuitive decision: when not to use AI
&lt;/h2&gt;

&lt;p&gt;The temptation in an AI product is to run everything through the model. Testing with real sources, the result was clear:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;Session agendas and orders of the day&lt;/strong&gt; benefit a lot. The AI identifies the cases, summarizes what each judgment is about, and highlights points of attention. It turns a document into a fast decision.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Full official gazettes&lt;/strong&gt; don't. They are long, cumulative documents. The model produces a generic summary that helps no one decide, and cost grows with document size.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;So pre-processing is selective, decided source by source. A gazette becomes an alert with a direct link; an agenda becomes an alert with analysis. Less AI in the right place delivered more value than AI everywhere.&lt;/p&gt;

&lt;h2&gt;
  
  
  What changed after the first client
&lt;/h2&gt;

&lt;p&gt;Lex Sentinel was born inside one association's routine. The second deployment exposed what was coupled without my noticing:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;Sources per instance.&lt;/strong&gt; The set of sources, the delivery type for each one, and the recipients became per-association configuration, not assumptions in the code.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;New sources, new formats.&lt;/strong&gt; Each new source brought a different publishing structure. That reinforced the split between a source-specific collector and the rest of the pipeline, which is shared.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Configuration as a deliverable.&lt;/strong&gt; Deployment became a stage of its own: configure monitors, sources and channels, validate against real data, and only then go live.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;The good side effect: the platform became more robust for the third association than it was for the second.&lt;/p&gt;

&lt;h2&gt;
  
  
  Cognitive infrastructure
&lt;/h2&gt;

&lt;p&gt;The way I think about Lex Sentinel is as a layer of cognitive infrastructure: something that continuously watches sources, organizes signals, and delivers information ready for whoever has to decide. The AI does not replace the professional who interprets the agenda. It takes away the digging.&lt;/p&gt;




&lt;p&gt;If you work on public-source monitoring, resilient scraping, or selective use of LLMs in pipelines, I'd like to hear how you handle "proven silence" and source breakage. Let me know in the comments.&lt;/p&gt;

&lt;p&gt;Learn more: &lt;a href="https://lexsentinel.allrox.com.br" rel="noopener noreferrer"&gt;lexsentinel.allrox.com.br&lt;/a&gt;&lt;/p&gt;

</description>
      <category>ai</category>
      <category>automation</category>
      <category>legaltech</category>
      <category>showdev</category>
    </item>
    <item>
      <title>Building a Legal Monitoring Platform for Brazilian Courts: Lessons from the AMAERJ Case</title>
      <dc:creator>AllRox</dc:creator>
      <pubDate>Fri, 06 Nov 2026 00:57:08 +0000</pubDate>
      <link>https://dev.to/allrox/building-a-legal-monitoring-platform-for-brazilian-courts-lessons-from-the-amaerj-case-4lnh</link>
      <guid>https://dev.to/allrox/building-a-legal-monitoring-platform-for-brazilian-courts-lessons-from-the-amaerj-case-4lnh</guid>
      <description>&lt;p&gt;Tracking dozens of official legal sources by hand doesn’t scale. Every court publishes in its own format, on its own schedule, and missing a single agenda item can be costly. This is how I approached the problem with Lex Sentinel, now adopted by the Rio de Janeiro State Magistrates Association (AMAERJ).&lt;/p&gt;

&lt;h2&gt;
  
  
  The problem
&lt;/h2&gt;

&lt;p&gt;Legal professionals spend a large share of their time on repetitive search and verification: checking agendas, gazettes and judgment lists across multiple institutions. The work is necessary, but it is not where their judgment adds the most value.&lt;/p&gt;

&lt;h2&gt;
  
  
  The approach
&lt;/h2&gt;

&lt;p&gt;Lex Sentinel is a continuous monitoring pipeline, not a one-off script:&lt;br&gt;
&lt;/p&gt;

&lt;pre data-lang="mermaid"&gt;&lt;code&gt;flowchart TD
  A[Sources] --&amp;gt; B[Verification cycles] --&amp;gt; C[Normalization] --&amp;gt; D[Dedup &amp;amp; relevance] --&amp;gt; E[Alerts] --&amp;gt; F[Daily proof of operation]&lt;/code&gt;&lt;/pre&gt;



&lt;p&gt;The design goal was simple to state and hard to meet: never lose an important publication, and be able to prove it.&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Recurring verification: official sources are checked in regular cycles throughout the day, with no manual intervention.&lt;/li&gt;
&lt;li&gt;Noise-free alerts: only genuinely new items trigger a notification. Already registered items are identified and discarded automatically.&lt;/li&gt;
&lt;li&gt;Individual delivery: each recipient gets their own message, with no data exposure between clients.&lt;/li&gt;
&lt;li&gt;Multi-channel: email, WhatsApp and Telegram, with channel redundancy so alerts arrive reliably.&lt;/li&gt;
&lt;/ul&gt;

&lt;h2&gt;
  
  
  What it monitors
&lt;/h2&gt;

&lt;ul&gt;
&lt;li&gt;CNJ (National Council of Justice): in-person and virtual judgment agendas, plus the DJe (Electronic Judicial Gazette)&lt;/li&gt;
&lt;li&gt;STF (Supreme Federal Court): judgment agendas&lt;/li&gt;
&lt;li&gt;TJRJ (Rio de Janeiro State Court of Justice): DJe publications and the Council of the Magistracy&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;New courts can be added on demand.&lt;/p&gt;

&lt;h2&gt;
  
  
  Reliability as a feature
&lt;/h2&gt;

&lt;p&gt;In monitoring, silence is ambiguous: no alert can mean nothing happened, or that something broke. So the system closes the loop:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Daily operation report: at the end of the day, a report confirms that every source was checked, with or without new publications. Each run is logged with timestamp and result.&lt;/li&gt;
&lt;li&gt;
&lt;a href="https://lexsentinel.allrox.com.br/status" rel="noopener noreferrer"&gt;Public status page&lt;/a&gt;: system health is visible at any time.&lt;/li&gt;
&lt;li&gt;Failure handling: failures are detected and reported immediately, with automatic recovery and no gaps in the history.&lt;/li&gt;
&lt;/ul&gt;

&lt;h2&gt;
  
  
  LexIA: interpretation on top of detection
&lt;/h2&gt;

&lt;p&gt;Detecting a publication is only half the job. LexIA is the AI layer that generates a structured report for each item: case identification, subject of the judgment, relevance to the recipient’s operation and points of attention to follow. It is delivered in the same monitoring cycle, so the alert arrives already interpreted.&lt;/p&gt;

&lt;h2&gt;
  
  
  The design principle: AI as infrastructure, not replacement
&lt;/h2&gt;

&lt;p&gt;Lex Sentinel is part of a broader idea: a &lt;a href="https://dev.to/allrox/cognitive-infrastructure-the-missing-layer-between-ai-and-real-impact-2ehp"&gt;cognitive infrastructure&lt;/a&gt; that supports human work. AI is not a replacement for qualified professionals. It is a continuous support layer that observes sources, organizes signals and expands an institution’s capacity to respond, while people keep the central role of interpretation and judgment.&lt;/p&gt;

&lt;h2&gt;
  
  
  Why the AMAERJ adoption matters
&lt;/h2&gt;

&lt;p&gt;Instead of a generic, experimental tool far from daily routine, AI can be applied in an objective, discreet and useful way, supporting recurring tasks inside real institutional workflows. That is the shift this case shows.&lt;/p&gt;

&lt;p&gt;Lex Sentinel does not replace human intelligence. It gives it a better organized foundation to act on.&lt;/p&gt;

&lt;h2&gt;
  
  
  About Lex Sentinel
&lt;/h2&gt;

&lt;p&gt;&lt;a href="https://lexsentinel.allrox.com.br" rel="noopener noreferrer"&gt;Lex Sentinel&lt;/a&gt; is a legal monitoring solution that tracks official sources, identifies new publications and sends automated alerts by email, WhatsApp and Telegram, with daily proof that every source was checked.&lt;/p&gt;

&lt;p&gt;Originally published on LinkedIn.&lt;/p&gt;

</description>
      <category>ai</category>
      <category>automation</category>
      <category>legaltech</category>
      <category>productengineering</category>
    </item>
    <item>
      <title>Cognitive Infrastructure: the missing layer between AI and real impact</title>
      <dc:creator>AllRox</dc:creator>
      <pubDate>Sun, 03 May 2026 23:30:33 +0000</pubDate>
      <link>https://dev.to/allrox/cognitive-infrastructure-the-missing-layer-between-ai-and-real-impact-2ehp</link>
      <guid>https://dev.to/allrox/cognitive-infrastructure-the-missing-layer-between-ai-and-real-impact-2ehp</guid>
      <description>&lt;p&gt;Artificial Intelligence is everywhere. But meaningful results are not.&lt;/p&gt;

&lt;p&gt;We reached a point where access is no longer the problem. Tools are abundant. Content is abundant. “AI-powered” workflows are everywhere. Even so, most professionals are still thinking and operating at the same level as before.&lt;/p&gt;

&lt;p&gt;Something is off.&lt;/p&gt;

&lt;p&gt;The issue is not the technology itself. It is how it is being used.&lt;/p&gt;

&lt;p&gt;Right now, most people interact with AI as if it were a smarter search engine. You ask something, you get an answer, and then everything disappears. The next time, you start again from zero. No memory, no continuity, no accumulation of knowledge.&lt;/p&gt;

&lt;p&gt;It feels powerful in the moment, but it does not compound.&lt;/p&gt;

&lt;p&gt;This is where the idea of cognitive infrastructure comes in.&lt;/p&gt;

&lt;p&gt;Cognitive infrastructure is not another tool. It is a way of structuring how information flows, evolves, and becomes usable over time. Instead of treating AI as something you consult occasionally, you build a layer that continuously captures signals, processes them, and turns them into insights you can actually use.&lt;/p&gt;

&lt;p&gt;The shift is subtle, but it changes everything.&lt;/p&gt;

&lt;p&gt;When you rely only on prompts, you are constantly rebuilding context. Every interaction depends on what you remember to ask. That creates friction and inconsistency. You might get good answers, but they are isolated. They do not build on each other.&lt;/p&gt;

&lt;p&gt;With a cognitive infrastructure in place, the dynamic changes. Information is not just consumed. It is organized, interpreted, and connected. Over time, patterns start to emerge without you needing to chase them.&lt;/p&gt;

&lt;p&gt;That is where real leverage begins.&lt;/p&gt;

&lt;p&gt;To make this more concrete, I built an internal system called Cortex. It is not a product and it was not designed to be one. It is simply an extension of how I think and work.&lt;/p&gt;

&lt;p&gt;Instead of waiting for me to search for information, Cortex continuously monitors sources that matter to my work. It filters what is relevant, processes it, and transforms it into structured insights. Not summaries for the sake of summarizing, but interpretations that highlight what actually matters.&lt;/p&gt;

&lt;p&gt;As this runs over time, it creates a layer of context that I can rely on. When I sit down to write, plan, or make a decision, I am not starting from zero. There is already a base of organized thinking behind it.&lt;/p&gt;

&lt;p&gt;This has a practical effect. Decisions become faster, but more importantly, they become more consistent. It is easier to connect ideas, to spot trends earlier, and to avoid getting lost in noise.&lt;/p&gt;

&lt;p&gt;Most people compete on execution. They try to do more, faster.&lt;/p&gt;

&lt;p&gt;Very few invest in improving how they see.&lt;/p&gt;

&lt;p&gt;Cognitive infrastructure is about improving perception. It reduces the effort required to stay informed and increases the quality of the decisions that follow. It does not just help you produce more. It helps you move in the right direction.&lt;/p&gt;

&lt;p&gt;And direction is where most people fail.&lt;/p&gt;

&lt;p&gt;It is possible to execute perfectly in the wrong direction for a long time. In fact, that is what happens more often than not. The problem is not lack of effort. It is lack of clarity.&lt;/p&gt;

&lt;p&gt;What we are starting to see now is the emergence of something different. Not just tools, not just assistants, but personal systems built around how each individual thinks and works.&lt;/p&gt;

&lt;p&gt;In these systems, AI is just one component. The real value comes from how information is captured, processed, and reused. The advantage is no longer in having access to a model. It is in having a system that evolves with you.&lt;/p&gt;

&lt;p&gt;That is what I mean by cognitive infrastructure.&lt;/p&gt;

&lt;p&gt;If you are still using AI as a better way to get answers on demand, you are only scratching the surface. The real shift happens when answers stop being something you request and start being something that is already in motion, shaped by a system that learns with you over time.&lt;/p&gt;

&lt;p&gt;That is when AI stops being a tool and starts becoming part of how you think.&lt;/p&gt;

</description>
      <category>cognitiveinfrastructure</category>
      <category>ai</category>
      <category>productengineering</category>
      <category>digitalthinking</category>
    </item>
    <item>
      <title>Why I Open-Sourced The LProject: A Sustainable Framework for Landing Pages</title>
      <dc:creator>AllRox</dc:creator>
      <pubDate>Sun, 24 Aug 2025 20:37:51 +0000</pubDate>
      <link>https://dev.to/allrox/why-i-open-sourced-the-lproject-a-sustainable-framework-for-landing-pages-4koj</link>
      <guid>https://dev.to/allrox/why-i-open-sourced-the-lproject-a-sustainable-framework-for-landing-pages-4koj</guid>
      <description>&lt;p&gt;&lt;a href="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.amazonaws.com%2Fuploads%2Farticles%2Ftf4s6fwmw6wejtxdgnfw.png" class="article-body-image-wrapper"&gt;&lt;img src="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.amazonaws.com%2Fuploads%2Farticles%2Ftf4s6fwmw6wejtxdgnfw.png" alt="The LProject Arcticle cover" width="800" height="533"&gt;&lt;/a&gt;&lt;/p&gt;

&lt;h2&gt;
  
  
  The Turning Point
&lt;/h2&gt;

&lt;p&gt;Not long ago, a client asked me a seemingly simple question:&lt;br&gt;
&lt;em&gt;“Could The LProject be delivered at a lower cost?”&lt;/em&gt;&lt;/p&gt;

&lt;p&gt;At first, it sounded like a routine negotiation. But that question triggered something bigger: if the market is driven only by price, where does the real value of digital products go?&lt;/p&gt;

&lt;p&gt;That was the moment I decided to open-source &lt;strong&gt;The LProject&lt;/strong&gt;.&lt;/p&gt;

&lt;h2&gt;
  
  
  The Problem with Today’s Market
&lt;/h2&gt;

&lt;p&gt;We’ve all seen it: websites and landing pages built on heavy CMS platforms, stacked with plugins and scripts. The result?&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Slower experiences,&lt;/li&gt;
&lt;li&gt;Higher energy consumption,&lt;/li&gt;
&lt;li&gt;Greater environmental impact,&lt;/li&gt;
&lt;li&gt;And an endless race to the bottom on price.
In the end, nobody wins: users, businesses, and not even the planet.&lt;/li&gt;
&lt;/ul&gt;

&lt;h2&gt;
  
  
  What is The LProject?
&lt;/h2&gt;

&lt;p&gt;The &lt;strong&gt;LProject&lt;/strong&gt; was created to break this cycle.&lt;br&gt;
It’s an &lt;strong&gt;open-source framework built on Next.js, optimized for Vercel&lt;/strong&gt;, designed to bring structure, performance, and sustainability into web development.&lt;/p&gt;

&lt;p&gt;The difference lies in its purpose: not just delivering a functional page, but ensuring that page is &lt;strong&gt;lighter, faster, and up to 96% less polluting in CO₂ emissions&lt;/strong&gt; than traditional solutions like WordPress or Magento.&lt;/p&gt;

&lt;p&gt;This commitment is backed by the certification seal:&lt;br&gt;
✔️ SUSTAINABLE TECHNOLOGY — BUILT WITH UP TO 96% LESS CO₂ EMISSIONS&lt;/p&gt;

&lt;h2&gt;
  
  
  Why Open Source?
&lt;/h2&gt;

&lt;p&gt;By open-sourcing The LProject, I’m making a clear statement:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;The code itself is not the final value.&lt;/li&gt;
&lt;li&gt;The value lies in the architecture, the sustainability seal, the user experience, and the product vision behind it.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;Open source allows anyone to use, test, and contribute to the framework. And for those seeking differentiation, the true advantage remains in what cannot be commoditized: design expertise, consulting, and the strategic guidance that leads to real impact.&lt;/p&gt;

&lt;h2&gt;
  
  
  The Expected Impact
&lt;/h2&gt;

&lt;ul&gt;
&lt;li&gt;For society: a lighter, more sustainable web, with reduced emissions and optimized energy use.&lt;/li&gt;
&lt;li&gt;For developers and agencies: a solid foundation that speeds up projects, reduces rework, and ensures consistency.&lt;/li&gt;
&lt;li&gt;For me, as a professional: a way to reinforce my position as both a UX Engineer and a Product Designer — someone who connects experience, engineering, and sustainability into meaningful digital solutions.&lt;/li&gt;
&lt;/ul&gt;

&lt;h2&gt;
  
  
  Take a look
&lt;/h2&gt;

&lt;p&gt;The LProject is now open and available on GitHub:&lt;br&gt;
👉 &lt;a href="https://github.com/allrox/thelproject-opensource" rel="noopener noreferrer"&gt;github.com/allrox/thelproject-opensource&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;If you believe technology can be a force for positive transformation, join me in this initiative. Contribute, test, evolve. Open source only makes sense when it becomes community.&lt;/p&gt;

&lt;blockquote&gt;
&lt;p&gt;“Code can be open, but purpose cannot be copied.&lt;br&gt;
The LProject is an invitation to build a more sustainable web — together.”&lt;/p&gt;
&lt;/blockquote&gt;

</description>
      <category>opensource</category>
      <category>uxengineering</category>
      <category>sustainability</category>
      <category>business</category>
    </item>
  </channel>
</rss>
