---
title: "Jay K Shenawy (@thinkodeai) | Hashnode"
description: "Jay K Shenawy (@thinkodeai) writes on Hashnode. Read their latest articles and follow their work."
url: "https://hashnode.com/@thinkodeai"
---

@thinkodeai

# Jay K Shenawy

@thinkodeai · Joined October 2025

### [Solving the Post-Launch Problem: Distributing SaaS Across 237+ Niche Channels](https://thinkreview.hashnode.dev/solving-the-post-launch-problem-distributing-saas-across-237-niche-channels?utm_source=hashnode&utm_medium=feed)

Shipping code is only half the battle. Here is how to tailor every release for different communities and track search visibility. Like many software engineers and indie founders, I ran into the same s

3 min read · [thinkreview.hashnode.dev](https://thinkreview.hashnode.dev/solving-the-post-launch-problem-distributing-saas-across-237-niche-channels?utm_source=hashnode&utm_medium=feed)

[1d ago](https://hashnode.com/posts/solving-the-post-launch-problem-distributing-saas-across-237-niche-channels/6afc96a450e37838c24bf921)

### [Running a second reader on agent-written code, before it merges](https://thinkreview.hashnode.dev/running-a-second-reader-on-agent-written-code-before-it-merges?utm_source=hashnode&utm_medium=feed)

The slow part of agent coding moved to the other side of the pull request An agent can write the branch in minutes. Someone still has to decide whether it should merge. Generating code is now the easy

5 min read · [thinkreview.hashnode.dev](https://thinkreview.hashnode.dev/running-a-second-reader-on-agent-written-code-before-it-merges?utm_source=hashnode&utm_medium=feed)

[Oct 25](https://hashnode.com/posts/running-a-second-reader-on-agent-written-code-before-it-merges/6ade4a2189002dfe5f3199d6)

### [AI Code Review for Bitbucket Cloud Pull Requests](https://thinkreview.hashnode.dev/ai-code-review-for-bitbucket-cloud-pull-requests?utm_source=hashnode&utm_medium=feed)

How are you running AI reviews on Bitbucket Cloud without a CI pipeline?

2 min read · [thinkreview.hashnode.dev](https://thinkreview.hashnode.dev/ai-code-review-for-bitbucket-cloud-pull-requests?utm_source=hashnode&utm_medium=feed)

[Oct 4](https://hashnode.com/posts/ai-code-review-for-bitbucket-cloud-pull-requests/6ac2e5b990937930534fde45)

### [How do you detect overlapping PRs before they collide in CI?](https://thinkreview.hashnode.dev/how-do-you-detect-overlapping-prs-before-they-collide-in-ci?utm_source=hashnode&utm_medium=feed)

We've been hitting a recurring problem on our team: two open PRs touching the same module land around the same time, and the review bot only sees the diff in isolation. By the time someone notices the

2 min read · [thinkreview.hashnode.dev](https://thinkreview.hashnode.dev/how-do-you-detect-overlapping-prs-before-they-collide-in-ci?utm_source=hashnode&utm_medium=feed)

[Oct 2](https://hashnode.com/posts/how-do-you-detect-overlapping-prs-before-they-collide-in-ci/6abf8e20526f50e54f7d4c63)

### [How to setup AI code reviews without feeling like generated by AI ?](https://thinkreview.hashnode.dev/how-to-setup-ai-code-reviews-without-feeling-like-generated-by-ai?utm_source=hashnode&utm_medium=feed)

There is a small moment in every code review where the finding is useful, but the act of sharing it is friction. You read it, you agree with it, and then you highlight, copy, switch tabs, open the con

4 min read · [thinkreview.hashnode.dev](https://thinkreview.hashnode.dev/how-to-setup-ai-code-reviews-without-feeling-like-generated-by-ai?utm_source=hashnode&utm_medium=feed)

[Sep 20](https://hashnode.com/posts/how-to-setup-ai-code-reviews-without-feeling-like-generated-by-ai/6aafa961acc2a0d410653bcb)
