<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Charlotte on Kailas Venkitasubramanian</title>
    <link>/tags/charlotte/</link>
    <description>Recent content in Charlotte on Kailas Venkitasubramanian</description>
    <generator>Hugo</generator>
    <language>en</language>
    <lastBuildDate>Thu, 10 Apr 2025 00:00:00 +0000</lastBuildDate>
    <atom:link href="/tags/charlotte/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Embracing multilingualism in data science</title>
      <link>/blog/series/reproducible-research-series/2025-04-10-multilingualism-in-data-science/</link>
      <pubDate>Thu, 10 Apr 2025 00:00:00 +0000</pubDate>
      <guid>/blog/series/reproducible-research-series/2025-04-10-multilingualism-in-data-science/</guid>
      <description>&lt;p&gt;Both of those efforts — reproducibility and pipelines — rest on a more basic question: which programming languages should a small research team actually use? In the previous posts of this series, I covered &#xA;&lt;a href=&#34;/blog/series/reproducible-research-series/2022-07-08-building-blocks-of-a-reproducible-research-framework/&#34;&gt;why reproducibility matters&lt;/a&gt; and how we are &#xA;&lt;a href=&#34;/blog/series/reproducible-research-series/2022-04-10-designing-reproducible-data-pipelines/&#34;&gt;designing reproducible data pipelines&lt;/a&gt; at the UNC Charlotte Urban Institute. This post is about the layer underneath both.&lt;/p&gt;&#xA;&lt;p&gt;Specifically, I want to argue that embracing &lt;em&gt;multilingualism&lt;/em&gt;&amp;mdash;fluency in both R and Python, rather than loyalty to one&amp;mdash;has quietly done more for our team&amp;rsquo;s output than almost any other choice we&amp;rsquo;ve made.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Changing CRDT operations under a Cloud</title>
      <link>/blog/series/crdt-telenovela-series/2023-06-09-making-sense-of-data-and-documenting-it/</link>
      <pubDate>Fri, 09 Jun 2023 00:00:00 +0000</pubDate>
      <guid>/blog/series/crdt-telenovela-series/2023-06-09-making-sense-of-data-and-documenting-it/</guid>
      <description>&lt;h2 id=&#34;the-promise-and-peril-of-a-large-contract&#34;&gt;The promise and peril of a large contract&#xA;  &lt;a href=&#34;#the-promise-and-peril-of-a-large-contract&#34;&gt;&lt;svg class=&#34;anchor-symbol&#34; aria-hidden=&#34;true&#34; height=&#34;26&#34; width=&#34;26&#34; viewBox=&#34;0 0 22 22&#34; xmlns=&#34;http://www.w3.org/2000/svg&#34;&gt;&#xA;      &lt;path d=&#34;M0 0h24v24H0z&#34; fill=&#34;currentColor&#34;&gt;&lt;/path&gt;&#xA;      &lt;path d=&#34;M3.9 12c0-1.71 1.39-3.1 3.1-3.1h4V7H7c-2.76.0-5 2.24-5 5s2.24 5 5 5h4v-1.9H7c-1.71.0-3.1-1.39-3.1-3.1zM8 13h8v-2H8v2zm9-6h-4v1.9h4c1.71.0 3.1 1.39 3.1 3.1s-1.39 3.1-3.1 3.1h-4V17h4c2.76.0 5-2.24 5-5s-2.24-5-5-5z&#34;&gt;&lt;/path&gt;&#xA;    &lt;/svg&gt;&lt;/a&gt;&#xA;&lt;/h2&gt;&#xA;&lt;p&gt;Much of the previous challenges in managing the technical operations at the data trust stemmed from a lack of understanding of the scope and extent of effort for a given piece of work and having no barometer to measure productivity (or the lack of it). This meant that everyone knew that a given piece of work took 1 month to complete, everyone agreed that this delay was not acceptable,but no one really could pinpoint where the bottlenecks were and why they existed.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Revamping the Charlotte Regional Data Trust - The story so far</title>
      <link>/blog/posts/2023-05-22-revamping-the-charlotte-regional-data-trust-the-story-so-far/</link>
      <pubDate>Mon, 22 May 2023 00:00:00 +0000</pubDate>
      <guid>/blog/posts/2023-05-22-revamping-the-charlotte-regional-data-trust-the-story-so-far/</guid>
      <description></description>
    </item>
    <item>
      <title>Plunging into the Data Trust black box, and Deep Cleaning the System</title>
      <link>/blog/series/crdt-telenovela-series/2023-05-20-plunging-into-data-trust/</link>
      <pubDate>Sat, 20 May 2023 00:00:00 +0000</pubDate>
      <guid>/blog/series/crdt-telenovela-series/2023-05-20-plunging-into-data-trust/</guid>
      <description>&lt;h2 id=&#34;diving-into-the-world-of-administrative-data-and-crdt&#34;&gt;Diving into the world of administrative data and CRDT&#xA;  &lt;a href=&#34;#diving-into-the-world-of-administrative-data-and-crdt&#34;&gt;&lt;svg class=&#34;anchor-symbol&#34; aria-hidden=&#34;true&#34; height=&#34;26&#34; width=&#34;26&#34; viewBox=&#34;0 0 22 22&#34; xmlns=&#34;http://www.w3.org/2000/svg&#34;&gt;&#xA;      &lt;path d=&#34;M0 0h24v24H0z&#34; fill=&#34;currentColor&#34;&gt;&lt;/path&gt;&#xA;      &lt;path d=&#34;M3.9 12c0-1.71 1.39-3.1 3.1-3.1h4V7H7c-2.76.0-5 2.24-5 5s2.24 5 5 5h4v-1.9H7c-1.71.0-3.1-1.39-3.1-3.1zM8 13h8v-2H8v2zm9-6h-4v1.9h4c1.71.0 3.1 1.39 3.1 3.1s-1.39 3.1-3.1 3.1h-4V17h4c2.76.0 5-2.24 5-5s-2.24-5-5-5z&#34;&gt;&lt;/path&gt;&#xA;    &lt;/svg&gt;&lt;/a&gt;&#xA;&lt;/h2&gt;&#xA;&lt;p&gt;Administrative data is messy is not much of an adage as much as it is a reality. When I took reins of managing the data infrastructure and analytical operations of Institute for Social Capital or ISC (now called the Charlotte Regional Data Trust) in the middle of 2021, messiness extended beyond data. The dysfunction was deep in how data was collected and organized, the way data operations and analyses were conducted, how information was collected from stakeholders, and how data was disseminated.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Making Data Pipelines for the Quality of Life Explorer seamless</title>
      <link>/blog/posts/2022-03-13-making-data-pipelines-for-the-quality-of-life-explorer-seamless/</link>
      <pubDate>Sun, 13 Mar 2022 00:00:00 +0000</pubDate>
      <guid>/blog/posts/2022-03-13-making-data-pipelines-for-the-quality-of-life-explorer-seamless/</guid>
      <description>&lt;h2 id=&#34;introduction&#34;&gt;Introduction&#xA;  &lt;a href=&#34;#introduction&#34;&gt;&lt;svg class=&#34;anchor-symbol&#34; aria-hidden=&#34;true&#34; height=&#34;26&#34; width=&#34;26&#34; viewBox=&#34;0 0 22 22&#34; xmlns=&#34;http://www.w3.org/2000/svg&#34;&gt;&#xA;      &lt;path d=&#34;M0 0h24v24H0z&#34; fill=&#34;currentColor&#34;&gt;&lt;/path&gt;&#xA;      &lt;path d=&#34;M3.9 12c0-1.71 1.39-3.1 3.1-3.1h4V7H7c-2.76.0-5 2.24-5 5s2.24 5 5 5h4v-1.9H7c-1.71.0-3.1-1.39-3.1-3.1zM8 13h8v-2H8v2zm9-6h-4v1.9h4c1.71.0 3.1 1.39 3.1 3.1s-1.39 3.1-3.1 3.1h-4V17h4c2.76.0 5-2.24 5-5s-2.24-5-5-5z&#34;&gt;&lt;/path&gt;&#xA;    &lt;/svg&gt;&lt;/a&gt;&#xA;&lt;/h2&gt;&#xA;&lt;p&gt;The idea of building a full-fledged data and computational infrastructure to support the &#xA;&lt;a href=&#34;https://mcmap.org/qol&#34; target=&#34;_blank&#34; rel=&#34;noopener&#34;&gt;Charlotte-Mecklenburg Quality of Life (QoL) Explorer&lt;/a&gt; didn&amp;rsquo;t start with an explicit demand for it. Rather, we were grappling with a deliverables backlog that had accumulated during the Covid-19 pandemic and needed to make up ground to keep the explorer up-to-date and meet deadlines.&lt;/p&gt;</description>
    </item>
    <item>
      <title>What&#39;s work like?</title>
      <link>/blog/posts/2021-04-18-what-s-work-like/</link>
      <pubDate>Mon, 12 Apr 2021 00:00:00 +0000</pubDate>
      <guid>/blog/posts/2021-04-18-what-s-work-like/</guid>
      <description>&lt;h2 id=&#34;dust-settles&#34;&gt;Dust Settles&#xA;  &lt;a href=&#34;#dust-settles&#34;&gt;&lt;svg class=&#34;anchor-symbol&#34; aria-hidden=&#34;true&#34; height=&#34;26&#34; width=&#34;26&#34; viewBox=&#34;0 0 22 22&#34; xmlns=&#34;http://www.w3.org/2000/svg&#34;&gt;&#xA;      &lt;path d=&#34;M0 0h24v24H0z&#34; fill=&#34;currentColor&#34;&gt;&lt;/path&gt;&#xA;      &lt;path d=&#34;M3.9 12c0-1.71 1.39-3.1 3.1-3.1h4V7H7c-2.76.0-5 2.24-5 5s2.24 5 5 5h4v-1.9H7c-1.71.0-3.1-1.39-3.1-3.1zM8 13h8v-2H8v2zm9-6h-4v1.9h4c1.71.0 3.1 1.39 3.1 3.1s-1.39 3.1-3.1 3.1h-4V17h4c2.76.0 5-2.24 5-5s-2.24-5-5-5z&#34;&gt;&lt;/path&gt;&#xA;    &lt;/svg&gt;&lt;/a&gt;&#xA;&lt;/h2&gt;</description>
    </item>
  </channel>
</rss>
