<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Career on Ilscipio - Enterprise Commerce Experts</title>
    <link>https://www.ilscipio.com/en/tags/career/</link>
    <description>Recent content in Career on Ilscipio - Enterprise Commerce Experts</description>
    <generator>Hugo</generator>
    <language>en-US</language>
    <lastBuildDate>Tue, 06 Oct 2026 00:00:00 +0000</lastBuildDate>
    <atom:link href="https://www.ilscipio.com/en/tags/career/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>What Enterprise Consulting Taught Me About Building Products</title>
      <link>https://www.ilscipio.com/en/blog/enterprise-consulting-taught-me/</link>
      <pubDate>Tue, 06 Oct 2026 00:00:00 +0000</pubDate>
      <guid>https://www.ilscipio.com/en/blog/enterprise-consulting-taught-me/</guid>
      <description>&lt;p&gt;I spent a year at one client watching a large team hand-editing XML configuration files. No autocomplete, no validation, no navigation. They knew the schema by heart because they had to. It was 2015, and I thought, this cannot be the state of things.&lt;/p&gt;&#xA;&lt;p&gt;It was.&lt;/p&gt;&#xA;&lt;h2 id=&#34;the-pattern-was-always-the-same&#34;&gt;The pattern was always the same&lt;/h2&gt;&lt;p&gt;One internal commerce platform ran on custom template languages. The editors were plain text with maybe syntax coloring if you were lucky. In another place, the deployment configuration had its own DSL that no IDE recognized. Every large client had something like this - a language or a format that mattered to the business but was invisible to the tooling.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
