Welcome - idmontie's Portfolio

Keeping Humans in the Loop for Agent-Written Code

Extending the Domain of the Zeta Function

Are Crawlers Our Primary Consumers?

The Basel Problem

"use strict";
const {Fragment: _Fragment, jsx: _jsx, jsxs: _jsxs} = arguments[0];
function _createMdxContent(props) {
  const _components = {
    img: "img",
    p: "p",
    ...props.components
  };
  return _jsxs(_Fragment, {
    children: [_jsx(_components.p, {
      children: "During my time at Coushsurfing, I architected and built Couchsurfing’s next-generation web platform, establishing a modern React, TypeScript, Next.js, Nx, and Node/NestJS architecture to support the company’s transition from its legacy application stack."
    }), "\n", _jsx(_components.p, {
      children: "Couchsurfing is a global travel platform that connects travelers with local hosts who open their homes to guests for free, creating opportunities for cultural exchange and shared experiences. The platform supports real-time messaging, trip and stay management, host discovery, local events, and destination-specific community experiences. Users could communicate via real-time chat, powered by Stream. This was an enormous improvement over the legacy version of inbox style messaging."
    }), "\n", _jsx(_components.p, {
      children: _jsx(_components.img, {
        src: "/media/2026-08-24-couchsurfing/couchsurfing-location.png",
        alt: "Location page"
      })
    }), "\n", _jsx(_components.p, {
      children: "Location pages were powered by merging data from different data sources, including external APIs for weather, timezone, and safety information. We used Mapbox for maps, Flickr for images, and pulled together localized details from our headless-CMS. Users could use location pages to find hosts, travelers, local events, and related communities. Events included those hosted by Couchsurfing users, and those sourced from third-parties."
    }), "\n", _jsx(_components.p, {
      children: _jsx(_components.img, {
        src: "/media/2026-08-24-couchsurfing/couchsurfing-events.png",
        alt: "Events page"
      })
    }), "\n", _jsx(_components.p, {
      children: "Our events features allowed users to organize events at a given time and place, see who was going and who was interested, and have discussions about the events."
    }), "\n", _jsx(_components.p, {
      children: _jsx(_components.img, {
        src: "/media/2026-08-24-couchsurfing/couchsurfing-trips.png",
        alt: "Trips page"
      })
    }), "\n", _jsx(_components.p, {
      children: "All of the location details, host information, and events could be managed via trips."
    })]
  });
}
function MDXContent(props = {}) {
  const {wrapper: MDXLayout} = props.components || ({});
  return MDXLayout ? _jsx(MDXLayout, {
    ...props,
    children: _jsx(_createMdxContent, {
      ...props
    })
  }) : _createMdxContent(props);
}
return {
  default: MDXContent
};


During my time at Coushsurfing, I architected and built Couchsurfing’s next-generation web platform, establishing a modern React, TypeScript, Next.js, Nx, and Node/NestJS architecture to support the company’s transition from its legacy application stack.
Couchsurfing is a global travel platform that connects travelers with local hosts who open their homes to guests for free, creating opportunities for cultural exchange and shared experiences. The platform supports real-time messaging, trip and stay management, host discovery, local events, and destination-specific community experiences. Users could communicate via real-time chat, powered by Stream. This was an enormous improvement over the legacy version of inbox style messaging.
<img alt="Location page" loading="lazy" width="1" height="1" decoding="async" data-nimg="1" class="mx-auto block !h-auto !w-auto max-h-[500px] max-w-full" style="color:transparent;width:auto;height:auto;max-width:100%;max-height:500px;margin:auto" src="/media/2026-08-24-couchsurfing/couchsurfing-location.png"/>
Location pages were powered by merging data from different data sources, including external APIs for weather, timezone, and safety information. We used Mapbox for maps, Flickr for images, and pulled together localized details from our headless-CMS. Users could use location pages to find hosts, travelers, local events, and related communities. Events included those hosted by Couchsurfing users, and those sourced from third-parties.
<img alt="Events page" loading="lazy" width="1" height="1" decoding="async" data-nimg="1" class="mx-auto block !h-auto !w-auto max-h-[500px] max-w-full" style="color:transparent;width:auto;height:auto;max-width:100%;max-height:500px;margin:auto" src="/media/2026-08-24-couchsurfing/couchsurfing-events.png"/>
Our events features allowed users to organize events at a given time and place, see who was going and who was interested, and have discussions about the events.
<img alt="Trips page" loading="lazy" width="1" height="1" decoding="async" data-nimg="1" class="mx-auto block !h-auto !w-auto max-h-[500px] max-w-full" style="color:transparent;width:auto;height:auto;max-width:100%;max-height:500px;margin:auto" src="/media/2026-08-24-couchsurfing/couchsurfing-trips.png"/>
All of the location details, host information, and events could be managed via trips.


During my time at Coushsurfing, I architected and built Couchsurfing’s next-generation web platform, establishing a modern React, TypeScript, Next.js, Nx, and Node/NestJS architecture to support the company’s transition from its legacy application stack.

Couchsurfing is a global travel platform that connects travelers with local hosts who open their homes to guests for free, creating opportunities for cultural exchange and shared experiences. The platform supports real-time messaging, trip and stay management, host discovery, local events, and destination-specific community experiences. Users could communicate via real-time chat, powered by Stream. This was an enormous improvement over the legacy version of inbox style messaging.

![Location page](/media/2026-08-24-couchsurfing/couchsurfing-location.png)

Location pages were powered by merging data from different data sources, including external APIs for weather, timezone, and safety information. We used Mapbox for maps, Flickr for images, and pulled together localized details from our headless-CMS. Users could use location pages to find hosts, travelers, local events, and related communities. Events included those hosted by Couchsurfing users, and those sourced from third-parties.

![Events page](/media/2026-08-24-couchsurfing/couchsurfing-events.png)

Our events features allowed users to organize events at a given time and place, see who was going and who was interested, and have discussions about the events.

![Trips page](/media/2026-08-24-couchsurfing/couchsurfing-trips.png)

All of the location details, host information, and events could be managed via trips.


Architected and implemented the next-generation tech stack for Couchsurfing.com.


Couchsurfing

"use strict";
const {jsx: _jsx} = arguments[0];
function _createMdxContent(props) {
  const _components = {
    p: "p",
    ...props.components
  };
  return _jsx(_components.p, {
    children: "Dive into the dynamic world of the WAX blockchain with this comprehensive tutorial series. From creating unique non-fungible tokens (NFTs) using AtomicAssets and crafting simple \"Hello World\" contracts, to deploying intricate guestbook contracts both locally and on the testnet, these tutorials provide a step-by-step guide to harnessing the full potential of WAX. Whether you're a developer eager to explore decentralized applications or an enthusiast curious about digital assets, this series offers invaluable insights into the robust capabilities of the WAX platform."
  });
}
function MDXContent(props = {}) {
  const {wrapper: MDXLayout} = props.components || ({});
  return MDXLayout ? _jsx(MDXLayout, {
    ...props,
    children: _jsx(_createMdxContent, {
      ...props
    })
  }) : _createMdxContent(props);
}
return {
  default: MDXContent
};


Dive into the dynamic world of the WAX blockchain with this comprehensive tutorial series. From creating unique non-fungible tokens (NFTs) using AtomicAssets and crafting simple &quot;Hello World&quot; contracts, to deploying intricate guestbook contracts both locally and on the testnet, these tutorials provide a step-by-step guide to harnessing the full potential of WAX. Whether you&#x27;re a developer eager to explore decentralized applications or an enthusiast curious about digital assets, this series offers invaluable insights into the robust capabilities of the WAX platform.


Dive into the dynamic world of the WAX blockchain with this comprehensive tutorial series. From creating unique non-fungible tokens (NFTs) using AtomicAssets and crafting simple "Hello World" contracts, to deploying intricate guestbook contracts both locally and on the testnet, these tutorials provide a step-by-step guide to harnessing the full potential of WAX. Whether you're a developer eager to explore decentralized applications or an enthusiast curious about digital assets, this series offers invaluable insights into the robust capabilities of the WAX platform.

My e-book on WAX Smart Contract development that guides developers through the process of creating a non-fungible token (NFT) smart contract.


Interactive Smart Contracts on WAX

"use strict";
const {Fragment: _Fragment, jsx: _jsx, jsxs: _jsxs} = arguments[0];
function _createMdxContent(props) {
  const _components = {
    p: "p",
    ...props.components
  };
  return _jsxs(_Fragment, {
    children: [_jsx(_components.p, {
      children: "This is a 22 part series on DevTo that goes through the entire process of creating\na WAX Smart Contract that interacts with AtomicAssets and the WAX RNG Oracle."
    }), "\n", _jsx(_components.p, {
      children: "It is a great introduction to WAX smart contract development and the WAX ecosystem."
    })]
  });
}
function MDXContent(props = {}) {
  const {wrapper: MDXLayout} = props.components || ({});
  return MDXLayout ? _jsx(MDXLayout, {
    ...props,
    children: _jsx(_createMdxContent, {
      ...props
    })
  }) : _createMdxContent(props);
}
return {
  default: MDXContent
};


This is a 22 part series on DevTo that goes through the entire process of creating
a WAX Smart Contract that interacts with AtomicAssets and the WAX RNG Oracle.
It is a great introduction to WAX smart contract development and the WAX ecosystem.


This is a 22 part series on DevTo that goes through the entire process of creating
a WAX Smart Contract that interacts with AtomicAssets and the WAX RNG Oracle.

It is a great introduction to WAX smart contract development and the WAX ecosystem.


WAX smart contract development course that guides developers through the process of creating a non-fungible token (NFT) smart contract.


WAX C++ NFT Tutorial

"use strict";
const {Fragment: _Fragment, jsx: _jsx, jsxs: _jsxs} = arguments[0];
function _createMdxContent(props) {
  const _components = {
    img: "img",
    p: "p",
    ...props.components
  };
  return _jsxs(_Fragment, {
    children: [_jsx(_components.p, {
      children: "While at Lacework, I worked on implementing entire new product lines for their cloud security offerings. This included architecting, implementing, and continuously delivering new features for Alerting, Identity Management, Resource Management, and Vulnerability Management on the web UI."
    }), "\n", _jsx(_components.p, {
      children: "My work included revamping the entire web application from the old application design which was created ad-hoc, into a modern and more structured design created by our UX team. As a front-end team\nwe worked closely with the UX team to ensure the new design was implemented correctly and that the user experience was improved. The application was built with React and Typescript, and the component\nlibrary we build our design system on top of was Ant Design."
    }), "\n", _jsx(_components.p, {
      children: _jsx(_components.img, {
        src: "/media/2023-08-04-lacework/lacework-statistics.png",
        alt: "Lacework Statistics"
      })
    }), "\n", _jsx(_components.p, {
      children: "The landing page would show a summary of the user's cloud security posture, including a summary of the user's cloud security risks, and a summary of the user's cloud security compliance."
    }), "\n", _jsx(_components.p, {
      children: _jsx(_components.img, {
        src: "/media/2023-08-04-lacework/lacework-cloud-compliance.png",
        alt: "Lacework Cloud Compliance"
      })
    }), "\n", _jsx(_components.p, {
      children: "The Cloud Compliance page would show a summary grouped by different metrics, such as cloud, assessments, and compliance status. The top of the page would show a summary of that group, along with\nany filters that were applied to the data that the user can change."
    }), "\n", _jsx(_components.p, {
      children: _jsx(_components.img, {
        src: "/media/2023-08-04-lacework/lacework-cloud-assessments.png",
        alt: "Lacework Cloud Assessment"
      })
    }), "\n", _jsx(_components.p, {
      children: "Below the summary, we would show different assessments that the user can investigate to improve their cloud security posture.."
    }), "\n", _jsx(_components.p, {
      children: _jsx(_components.img, {
        src: "/media/2023-08-04-lacework/lacework-polygraph.png",
        alt: "Lacework Polygraph"
      })
    }), "\n", _jsx(_components.p, {
      children: "One of the first visualizations built at Lacework was the Polygraph, which was a visualization of all the different entities in a user's cloud environment, even across different cloud platforms and machines."
    })]
  });
}
function MDXContent(props = {}) {
  const {wrapper: MDXLayout} = props.components || ({});
  return MDXLayout ? _jsx(MDXLayout, {
    ...props,
    children: _jsx(_createMdxContent, {
      ...props
    })
  }) : _createMdxContent(props);
}
return {
  default: MDXContent
};


While at Lacework, I worked on implementing entire new product lines for their cloud security offerings. This included architecting, implementing, and continuously delivering new features for Alerting, Identity Management, Resource Management, and Vulnerability Management on the web UI.
My work included revamping the entire web application from the old application design which was created ad-hoc, into a modern and more structured design created by our UX team. As a front-end team
we worked closely with the UX team to ensure the new design was implemented correctly and that the user experience was improved. The application was built with React and Typescript, and the component
library we build our design system on top of was Ant Design.
<img alt="Lacework Statistics" loading="lazy" width="1" height="1" decoding="async" data-nimg="1" class="mx-auto block !h-auto !w-auto max-h-[500px] max-w-full" style="color:transparent;width:auto;height:auto;max-width:100%;max-height:500px;margin:auto" src="/media/2023-08-04-lacework/lacework-statistics.png"/>
The landing page would show a summary of the user&#x27;s cloud security posture, including a summary of the user&#x27;s cloud security risks, and a summary of the user&#x27;s cloud security compliance.
<img alt="Lacework Cloud Compliance" loading="lazy" width="1" height="1" decoding="async" data-nimg="1" class="mx-auto block !h-auto !w-auto max-h-[500px] max-w-full" style="color:transparent;width:auto;height:auto;max-width:100%;max-height:500px;margin:auto" src="/media/2023-08-04-lacework/lacework-cloud-compliance.png"/>
The Cloud Compliance page would show a summary grouped by different metrics, such as cloud, assessments, and compliance status. The top of the page would show a summary of that group, along with
any filters that were applied to the data that the user can change.
<img alt="Lacework Cloud Assessment" loading="lazy" width="1" height="1" decoding="async" data-nimg="1" class="mx-auto block !h-auto !w-auto max-h-[500px] max-w-full" style="color:transparent;width:auto;height:auto;max-width:100%;max-height:500px;margin:auto" src="/media/2023-08-04-lacework/lacework-cloud-assessments.png"/>
Below the summary, we would show different assessments that the user can investigate to improve their cloud security posture..
<img alt="Lacework Polygraph" loading="lazy" width="1" height="1" decoding="async" data-nimg="1" class="mx-auto block !h-auto !w-auto max-h-[500px] max-w-full" style="color:transparent;width:auto;height:auto;max-width:100%;max-height:500px;margin:auto" src="/media/2023-08-04-lacework/lacework-polygraph.png"/>
One of the first visualizations built at Lacework was the Polygraph, which was a visualization of all the different entities in a user&#x27;s cloud environment, even across different cloud platforms and machines.


While at Lacework, I worked on implementing entire new product lines for their cloud security offerings. This included architecting, implementing, and continuously delivering new features for Alerting, Identity Management, Resource Management, and Vulnerability Management on the web UI.

My work included revamping the entire web application from the old application design which was created ad-hoc, into a modern and more structured design created by our UX team. As a front-end team
we worked closely with the UX team to ensure the new design was implemented correctly and that the user experience was improved. The application was built with React and Typescript, and the component
library we build our design system on top of was Ant Design.

![Lacework Statistics](/media/2023-08-04-lacework/lacework-statistics.png)

The landing page would show a summary of the user's cloud security posture, including a summary of the user's cloud security risks, and a summary of the user's cloud security compliance.

![Lacework Cloud Compliance](/media/2023-08-04-lacework/lacework-cloud-compliance.png)

The Cloud Compliance page would show a summary grouped by different metrics, such as cloud, assessments, and compliance status. The top of the page would show a summary of that group, along with
any filters that were applied to the data that the user can change.

![Lacework Cloud Assessment](/media/2023-08-04-lacework/lacework-cloud-assessments.png)

Below the summary, we would show different assessments that the user can investigate to improve their cloud security posture..

![Lacework Polygraph](/media/2023-08-04-lacework/lacework-polygraph.png)

One of the first visualizations built at Lacework was the Polygraph, which was a visualization of all the different entities in a user's cloud environment, even across different cloud platforms and machines.



Keeping Humans in the Loop for Agent-Written Code

Latest Posts

Keeping Humans in the Loop for Agent-Written Code

Extending the Domain of the Zeta Function

Are Crawlers Our Primary Consumers?

The Basel Problem

Latest Projects

Couchsurfing

Interactive Smart Contracts on WAX

WAX C++ NFT Tutorial

Lacework