<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0" xmlns:cc="http://cyber.law.harvard.edu/rss/creativeCommonsRssModule.html">
    <channel>
        <title><![CDATA[Stories by Yanai Ron on Medium]]></title>
        <description><![CDATA[Stories by Yanai Ron on Medium]]></description>
        <link>https://medium.com/@yanairon?source=rss-f60ce30ae8a9------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*qTthSosgmae1DqbjUpjeSA.jpeg</url>
            <title>Stories by Yanai Ron on Medium</title>
            <link>https://medium.com/@yanairon?source=rss-f60ce30ae8a9------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Mon, 16 Nov 2026 18:23:06 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@yanairon/feed" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[I replaced coding-agent orchestration with Git worktrees and one Python file]]></title>
            <link>https://medium.com/@yanairon/i-replaced-coding-agent-orchestration-with-git-worktrees-and-one-python-file-10fb0eadf70e?source=rss-f60ce30ae8a9------2</link>
            <guid isPermaLink="false">https://medium.com/p/10fb0eadf70e</guid>
            <category><![CDATA[git]]></category>
            <category><![CDATA[programming]]></category>
            <category><![CDATA[developer-tools]]></category>
            <category><![CDATA[artificial-intelligence]]></category>
            <category><![CDATA[open-source]]></category>
            <dc:creator><![CDATA[Yanai Ron]]></dc:creator>
            <pubDate>Wed, 16 Sep 2026 18:57:28 GMT</pubDate>
            <atom:updated>2026-09-16T19:05:56.369Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*CG6y0eNiyyQFPsPl.png" /></figure><p>When I started running more than one coding agent against the same repository, the first problem was not model quality. It was filesystem state.</p><p>Two agents in one checkout can overwrite each other’s files, change the same index, switch branches underneath each other, and leave a working tree that no longer explains which task produced which change. The obvious response is to add orchestration: a daemon, a task database, a process manager, or a UI.</p><p>I wanted to see how far plain Git could go first.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*7VVtGdXDovov755vYr2NAw.gif" /></figure><h3>The isolation primitive was already there</h3><p>A Git worktree gives one repository several working directories. Each worktree has its own checked-out branch and index, while the object database is shared.</p><p>That maps cleanly to a coding-agent task:</p><ul><li>one task name</li><li>one worktree</li><li>one branch</li><li>one agent process</li><li>one reviewable diff</li></ul><p>I turned that mapping into <strong>taskpods</strong>, a small Python CLI with no runtime dependencies.</p><pre>pip install taskpods</pre><p>From inside a Git repository:</p><pre>taskpods start tests --agent codex exec --sandbox workspace-write &quot;add API tests&quot;<br>taskpods start docs --agent claude -p &quot;improve the docs&quot;</pre><p>The first command creates .taskpods/tests on pods/tests. The second creates .taskpods/docs on pods/docs. Each agent runs with its worktree as the current directory.</p><p>The agents do not need a taskpods integration. Everything after --agent is passed through as the command to execute. That means the same mechanism works with Claude Code, Codex CLI, Gemini CLI, opencode, aider, or a local script.</p><h3>The pod is disposable, but the result is not</h3><p>An agent process exiting does not delete its worktree. The pod stays in place so I can inspect the actual diff:</p><pre>taskpods list<br>git -C .taskpods/tests diff main<br>git -C .taskpods/docs diff main</pre><p>If i want the change, i finish the pod:</p><pre>taskpods done tests -m &quot;Add API tests&quot; --remove</pre><p>done stages and commits the worktree, pushes its branch, and uses the GitHub CLI to open a pull request when gh is available. --remove removes the worktree after the branch is safely on the remote.</p><p>If I do not want the change:</p><pre>taskpods abort tests</pre><p>The abort path checks whether the branch exists on the remote. If it does, taskpods refuses to delete it automatically. That guard matters because “disposable” should describe the local environment, not already-pushed work.</p><p>There is also a cleanup command:</p><pre>taskpods prune</pre><p>It removes pods whose branches have already been merged upstream.</p><h3>Why I kept it small</h3><p>There are good tools for supervising fleets of agents, managing terminal sessions, assigning tasks, and reviewing results. taskpods is intentionally below that layer.</p><p>It does not schedule agents or coordinate their reasoning. It does not maintain a database. It does not run a daemon. It makes one narrow guarantee: each task gets a separate Git worktree and branch, and the lifecycle from start to review to PR or abort is explicit.</p><p>The current release is one Python file, supports Python 3.9+, and has no runtime package dependencies. Git remains the source of truth.</p><p>That small surface also makes it composable. A shell script, CI job, task runner, or higher-level orchestrator can call taskpods without adopting another state model.</p><h3>What I am testing next</h3><p>The current release is <strong>v0.4.0</strong>. PePy reports 2,117 cumulative downloads, which is enough to start seeing whether the worktree model survives use outside my own setup but far too early to declare the interface settled.</p><p>The cases I want to learn more about are:</p><ul><li>several long-running agents against one repository</li><li>interrupted agent processes</li><li>branch cleanup after manual merges</li><li>repositories whose default branch is not main</li><li>teams that want task isolation without a permanent control plane</li></ul><p>The code and issue tracker are here:</p><p><a href="https://github.com/yanairon/taskpods">https://github.com/yanairon/taskpods</a></p><p>If you use Claude Code specifically, I maintain claude-hookbook separately: reviewed hooks for formatters, guardrails, and notifications. I kept it separate because hooks configure one agent, while taskpods isolates any agent at the Git layer.</p><p>If taskpods saves you time, the repository has optional GitHub Sponsors and Ko-fi links.</p><p><em>Originally published at </em><a href="https://dev.to/yanairon/i-replaced-coding-agent-orchestration-with-git-worktrees-and-one-python-file-4gj2"><em>https://dev.to</em></a><em> on September 16, 2026.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=10fb0eadf70e" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[I got tired of my AI agents fighting over one repo, so I built taskpods]]></title>
            <link>https://medium.com/@yanairon/i-got-tired-of-my-ai-agents-fighting-over-one-repo-so-i-built-taskpods-4fdaf14e4296?source=rss-f60ce30ae8a9------2</link>
            <guid isPermaLink="false">https://medium.com/p/4fdaf14e4296</guid>
            <category><![CDATA[artificial-intelligence]]></category>
            <category><![CDATA[developer-tools]]></category>
            <category><![CDATA[open-source]]></category>
            <category><![CDATA[programming]]></category>
            <category><![CDATA[python]]></category>
            <dc:creator><![CDATA[Yanai Ron]]></dc:creator>
            <pubDate>Thu, 10 Sep 2026 14:41:45 GMT</pubDate>
            <atom:updated>2026-09-10T14:55:45.713Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*VhRJzruuQe93LaMb.png" /></figure><p>A few months ago I started running AI coding agents in parallel: one fixing a bug, one updating docs, one trying a refactor. The agents were fine. My repo was not.</p><p>Every agent CLI works in your working tree. Two agents on the same repo means they edit the same files, stage each other’s changes, and occasionally commit on top of one another. The “solution” I kept seeing was manual git worktrees: create one per agent, remember the branch names, remember where you put them, clean them up later. It works, but it’s fiddly enough that I kept not doing it.</p><p>So I wrote the thing I wanted: <a href="https://github.com/yanairon/taskpods">taskpods</a>, a small Python CLI that wraps git worktrees into disposable “pods”.</p><pre>pip install taskpods</pre><h3>What a pod is</h3><p>A pod is a git worktree plus a branch, managed as one unit. One command creates it and drops your agent inside:</p><pre>taskpods start fix-auth --agent &quot;claude -p &#39;fix the token refresh bug&#39;&quot;</pre><p>That creates .taskpods/fix-auth/ as a worktree on branch pods/fix-auth and runs the agent there. --agent takes any command, so it works with claude, codex, gemini, opencode, a shell script, whatever you use. Start a second pod and the two agents never see each other&#39;s files:</p><pre>taskpods start docs-update --agent &quot;claude -p &#39;document the config options&#39;&quot; <br>taskpods list</pre><h3>The lifecycle</h3><p>When an agent finishes, I review the diff like I would for a junior dev:</p><pre>git -C .taskpods/fix-auth diff main</pre><p>if it’s good:</p><pre>taskpods done fix-auth -m &quot;fix: token refresh&quot; --remove</pre><p>That commits, pushes the branch, opens a PR if you have gh installed, and removes the worktree. If it&#39;s bad:</p><pre>taskpods abort fix-auth</pre><p>and the pod never existed. Abort refuses to delete work you’ve already pushed, which has saved me once already.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/790/1*sy8Pk2oprs2QAg0HASCT6g.gif" /></figure><h3>Design choices I cared about</h3><ul><li><strong>Zero config.</strong> No daemon, no TUI, no config file to learn. It’s one Python file over plain git worktree commands. If you know git, you already know what it&#39;s doing.</li><li><strong>Agent-agnostic.</strong> Claude Code has a native worktree flag now, but it’s Claude-only. I wanted the same workflow regardless of which agent I’m using that week, and I wanted the lifecycle (list / done / abort) in one place instead of in my shell history.</li><li><strong>Boring on purpose.</strong> Pods are real worktrees with real branches. Nothing is hidden in a database somewhere; you can cd into a pod and use git normally.</li></ul><h3>What’s next</h3><p>It’s MIT-licensed and on PyPI: <a href="https://github.com/yanairon/taskpods">github.com/yanairon/taskpods</a>. v0.4.0 just shipped with the --agent launcher. I&#39;d genuinely like to hear how other people run parallel agents - if you have a workflow that works better, tell me about it in the comments.</p><p><em>Originally published at </em><a href="https://dev.to/yanairon/i-got-tired-of-my-ai-agents-fighting-over-one-repo-so-i-built-taskpods-nk0"><em>https://dev.to</em></a><em> on September 10, 2026.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=4fdaf14e4296" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[When You Say “I’m on It,” Here’s What Your Manager is Really Expecting]]></title>
            <link>https://medium.com/@yanairon/when-you-say-im-on-it-here-s-what-your-manager-is-really-expecting-7e0261412308?source=rss-f60ce30ae8a9------2</link>
            <guid isPermaLink="false">https://medium.com/p/7e0261412308</guid>
            <category><![CDATA[accountability]]></category>
            <category><![CDATA[management]]></category>
            <category><![CDATA[management-style]]></category>
            <category><![CDATA[management-and-leadership]]></category>
            <dc:creator><![CDATA[Yanai Ron]]></dc:creator>
            <pubDate>Fri, 24 Jan 2025 11:42:36 GMT</pubDate>
            <atom:updated>2025-01-24T11:42:36.441Z</atom:updated>
            <content:encoded><![CDATA[<p>Not so long ago, during a team meeting, I asked my team members a seemingly simple question: “When you say, ‘I’m on it,’ what does that mean?”</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Ftenor.com%2Fembed%2F6277377558062854699&amp;display_name=Tenor&amp;url=https%3A%2F%2Ftenor.com%2Fview%2Fi%27m-on-it-dennis-wojciechowski-cisco-angus-sampson-the-lincoln-lawyer-gif-6277377558062854699&amp;image=https%3A%2F%2Fmedia.tenor.com%2FVx25oU1YcisAAAAN%2Fi%2527m-on-it-dennis-wojciechowski.png&amp;type=text%2Fhtml&amp;schema=tenor" width="600" height="400" frameborder="0" scrolling="no"><a href="https://medium.com/media/9027c46fc1ca6a40f5bafda16553229b/href">https://medium.com/media/9027c46fc1ca6a40f5bafda16553229b/href</a></iframe><p>The responses varied:</p><blockquote>- “I understand the task.”<br>- “I know how to do the task.”<br>- “I need to do this task.”</blockquote><p>These answers made sense but missed the point. When I hear “I’m on it,” I’m looking for something deeper: <strong>Accountability.</strong></p><h4>What “I’m on It” Really Means</h4><p>When you say, “I’m on it,” here’s what I’m expecting:</p><ol><li><strong>Ownership<br></strong>You’ve taken responsibility. The responsibility is no longer mine — it’s yours, and I can trust that you’ll see it through. I can now mentally cross it off my list because I know it’s now on your list.</li><li><strong>Doing whatever it takes<br></strong>If you don’t know how to proceed, you’ll ask questions or find answers. If others need to act, you’ll coordinate and follow up until it’s done.</li><li><strong>Prioritization</strong><br>If the task’s priority isn’t clear, you’ll ask. You’ll balance it with your other responsibilities to ensure nothing falls through the cracks.</li><li><strong>Updates</strong><br> You’ll keep me informed, sharing progress and timelines. If there’s a roadblock, I’ll hear about it from you — not because I asked.</li></ol><h4>The Essence of “I’m on It”</h4><p>“I’m on it” isn’t just an acknowledgment. It’s a promise. It tells me:</p><p>- You’ve got this covered.<br>- I don’t need to worry about it anymore.<br>- You’ll ensure it gets done, no matter the challenges.</p><p>In short, it’s a transfer of responsibility that lets me focus elsewhere with confidence.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/800/1*SNUd79fWCMAIK-w-YwY2mg.png" /></figure><h4>Building Accountability in Your Team</h4><p>As a manager, here’s how to create a culture where “I’m on it” equals true accountability:</p><ul><li><strong>Set Clear Expectations:</strong> Explain what “I’m on it” should mean.<br><em>You can start with the exercise I did on your upcoming team meeting.</em></li><li><strong>Model Accountability:</strong> Show ownership in your actions to set the tone.</li><li><strong>Offer Support:</strong> Encourage team members to seek help when needed. Accountability doesn’t mean doing it alone.</li><li><strong>Recognize Ownership:</strong> Praise those who take responsibility and follow through.</li></ul><h4><strong>Final Thoughts</strong></h4><p>Next time you say, “I’m on it,” think about what it truly means. It’s not just a reply — it’s a commitment to take full ownership and deliver results.</p><p>As a manager, I’m not just asking for a task to be done; <strong>I’m trusting you with it</strong>. And when you take that trust seriously, it’s a win for both of us.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=7e0261412308" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[With ChatGPT’s Help, I Created a Local Environment Script in a Matter of Hours]]></title>
            <link>https://medium.com/@yanairon/with-chatgpts-help-i-created-a-local-environment-script-in-a-matter-of-hours-6180dea4f290?source=rss-f60ce30ae8a9------2</link>
            <guid isPermaLink="false">https://medium.com/p/6180dea4f290</guid>
            <category><![CDATA[script]]></category>
            <category><![CDATA[docker]]></category>
            <category><![CDATA[ai]]></category>
            <category><![CDATA[local-environment]]></category>
            <category><![CDATA[chatgpt]]></category>
            <dc:creator><![CDATA[Yanai Ron]]></dc:creator>
            <pubDate>Wed, 25 Jan 2023 12:15:17 GMT</pubDate>
            <atom:updated>2023-01-25T12:15:17.829Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*HzvURn3eXW5nSyS89dNp-A.png" /></figure><p>As a software developer, setting up a local development environment can be tedious. There are different tools and libraries to install, git repositories to clone, a database to set up, and configuration files to create. If you’re new to a project or working on multiple projects simultaneously, this can take hours and be frustrating. Also, it’s never the right time to do it!</p><p>In this post, I will show you how I used <a href="https://chat.openai.com/">ChatGPT</a> to create a script that automates the process of setting up a local development environment for a backend developer and add some tips on approaching this kind of task.</p><h3>TL;DR</h3><ul><li>Don’t use this tool like Google; use it as a friend/consultant you are working with on a project.</li><li>Explain patiently and thoroughly what you want, and iterate until it’s perfect for your needs, one step at a time.</li><li>Think about the user, and make the script friendly; in my case, I’ve asked ChatGPT to use Sassy echo prompts and colors.</li><li>Use ChatGPT to fix errors that occur along the way.</li></ul><h3>The basic script logic</h3><p>First thing first, when starting with ChatGPT, define exactly what you are about to do, in my case:</p><blockquote>“can you help me create a script that generates a local environment for a backend developer, step by step, until we have the perfect script?”</blockquote><p>At this point ChatGPT started suggesting what this script would do, which is not what I meant, So I gave it a little tune:</p><blockquote>“some ground rules: the OS is mac, install nodejs version using nvm, clone a github project (nodejs), create a local DB using docker with a specific base, creating postgres db and specific extensions and import from a dump, then create a .env file to access it. let’s start step by step, first, what will you recommend as the programming language for the script? bash/nodejs/other?”</blockquote><p>ChatGPT then suggested we’ll go with bash since I want to install Node.js as part of this script, good choice!</p><blockquote>“Alright, let’s start with a bash script with all of the above, start with a boilerplate”</blockquote><p>At this point, ChatGPT started coding:</p><pre>#!/bin/bash<br><br># Update package manager<br>sudo apt-get update<br><br># Install nvm<br>curl -o- https://raw.githubusercontent.com/nvm-sh/nvm/v0.37.2/install.sh | bash<br><br># Load nvm<br>export NVM_DIR=&quot;$([ -z &quot;${XDG_CONFIG_HOME-}&quot; ] &amp;&amp; printf %s &quot;${HOME}/.nvm&quot; || printf %s &quot;${XDG_CONFIG_HOME}/nvm&quot;)&quot;<br>[ -s &quot;$NVM_DIR/nvm.sh&quot; ] &amp;&amp; \. &quot;$NVM_DIR/nvm.sh&quot; # This loads nvm<br><br># Install Node.js<br>nvm install 12.22.0<br><br># Clone Github repository<br>git clone https://github.com/&lt;username&gt;/&lt;repository&gt;.git<br><br># Start Docker container with Postgres<br>docker run --name &lt;container-name&gt; -e POSTGRES_USER=&lt;username&gt; -e POSTGRES_PASSWORD=&lt;password&gt; -e POSTGRES_DB=&lt;dbname&gt; -p 5432:5432 -d postgres<br><br># create the extensions<br>docker exec -it &lt;container-name&gt; psql -U &lt;username&gt; -d &lt;dbname&gt; -c &quot;create extension if not exists pg_trgm;&quot;<br><br># import dump<br>docker exec -i &lt;container-name&gt; pg_restore -U &lt;username&gt; -d &lt;dbname&gt; &lt; dump.sql<br><br># create .env file<br>echo &quot;DATABASE_URL=postgres://&lt;username&gt;:&lt;password&gt;@localhost:5432/&lt;dbname&gt;&quot; &gt; .env</pre><p>That’s a good start, but not exactly what I wanted, so I refined:</p><blockquote>“Can you change it to using homebrew?”</blockquote><p>Done. But the node version is wrong:</p><blockquote>“change node version to 18”</blockquote><p>Done. But I wanted Postgres to run on docker. I needed to be a little specific to get this one done:</p><blockquote>“now change the way postgres is installed to work with docker, with this command : docker run — name local_db -p 65432:5432 -e POSTGRES_PASSWORD=postgres -e POSTGRES_USER=postgres -d gangstead/postgis:13–3.1-arm”</blockquote><p>At this time, it’s worth mentioning a few annoying ChatGPT behaviors I managed to overcome:</p><p>1 — Every time I got a piece of code, ChatGPT added a long explanation after it. I didn’t want this, so I wrote “don’t explain to me what the script does, only output the script.” and it worked</p><p>2 — For some reason, many times the code was cut in the middle, and I needed to ask it not to do it again</p><p><em>As you can see, I’m treating ChatGPT as a little kid, with patience, explaining precisely what I need over and over until I get what I want, because, even though in many fields, its knowledge matches a skilled professional, his social/cognitive abilities can sometimes feel like a child’s.</em></p><p><em>As software developers, we are used that our tools are getting input and outputting exactly what we want. we need to do a mind switch here</em>;<em> It’s a tool we are consulting with, not just activating to get an expected result for an input.</em></p><p><em>We need to use social skills, not computer science skills, and we need to get used to that.</em></p><h3>“Make it sassy”</h3><p>So, after a bit more back and forth, the script was ready to run, but I wanted it to be more user-friendly, so I asked ChatGPT to do it for me:</p><blockquote>“now make it sassier, make explanations in echo prompts as if a cheeky woman is saying it, and use colors”</blockquote><pre>#!/bin/bash<br><br>red=&#39;\033[0;31m&#39;<br>green=&#39;\033[0;32m&#39;<br>yellow=&#39;\033[0;33m&#39;<br>nc=&#39;\033[0m&#39; # No Color<br><br>echo -e &quot;${green}Welcome to the &lt;company name&gt; local environment setup script for the &lt;repository name&gt; repository! Let&#39;s get this party started, honey!${nc}&quot;<br><br># Update Homebrew and Install necessary packages<br>echo &quot;Updating Homebrew and installing necessary packages... Sweetie pie, we&#39;re making progress!&quot;<br>brew update &amp;&amp; brew install nvm docker<br>nvm install 18.9.1<br><br># Clone Github repository<br>echo &quot;Cloning SafeUP repository... Almost there, darling!&quot;<br>git clone https://github.com/&lt;repository name&gt;.git<br>cd &lt;repository name&gt;<br><br># Install and start postgres with Docker<br>echo &quot;Starting up postgres with Docker... Hang on tight, we&#39;re getting there!&quot;<br>docker run --name local_db -p 65432:5432 -e POSTGRES_PASSWORD=postgres -e POSTGRES_USER=postgres -d gangstead/postgis:13-3.1-arm<br><br># create the extensions<br>docker exec -it local_db psql -U postgres -c &quot;create extension if not exists pg_trgm; create extension if not exists postgis; create extension if not exists uuid-ossp; create extension if not exists postgres_fdw;&quot;<br><br># import dump<br>docker exec -i local_db pg_restore -U postgres -d postgres &lt; dump.sql<br><br># create .env file<br>echo &quot;Creating .env fil<br>echo &quot;DATABASE_URL=postgres://postgres:postgres@localhost:65432/postgres&quot; &gt; .env<br><br>echo &quot;All done, sweetie! Your local environment is ready for use! Let&#39;s get coding!&quot;</pre><p><em>I’ve hidden our internal names for privacy reasons. Here’s an example of the colorful output:</em></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*FIZwGIMSPQKmdXEG5JMUJQ.png" /></figure><h3>What else?</h3><p>I asked ChatGPT some more things along the way, for example:</p><ul><li>extract GitHub repository, DB name, port, etc., to outside arguments, with arguments validation</li><li>Write a script that runs the original script with the arguments hard coded</li><li>Deal with edge cases when the repository or DB already exists</li><li>Or, let’s let ChatGPT write that list for us:</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*T3-_Ciw5BvxxN9uhPkGWWQ.png" /></figure><p>Since ChatGPT is saving your chat history (for now), I can return to it and add more stuff as I need it, forever.</p><h3>Testing</h3><p>Now for the money time, actually running the script.</p><p>Of course, there’s no way the first run will succeed. It never does, but, can I use ChatGPT to help me make it run? of course!</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*3bm5OQrsvVB9wpFEngd7eg.png" /></figure><p>Of course, ChatGPT can change it for me and output the script again.</p><p>I did a few of these until everything was running smoothly.</p><h3>Finalizing</h3><p>Time to wrap up the script</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*bHSEs8YCPBbys-twqlHEvQ.png" /></figure><p>Amazing stuff! Now for the final part:</p><blockquote>“I want you to help write a medium.com post about how you helped me building this script”</blockquote><p>This would have been an interesting turn of events, right?</p><p>Eventually, I decided to take some ideas (like the title, for example) but write most of the post myself. I also asked it to write me a <a href="https://openai.com/dall-e-2/">Dall-E</a> prompt to create an image for this post, but eventually decided not to use it.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*WsO3rm_Ap8t6j40gDArBrg.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Nz7s6vLLXJ0XOmVR4yChGg.png" /><figcaption>The image I didn’t want to use, generated with Dall-E</figcaption></figure><h3>Final thoughts</h3><p>It’s becoming a <a href="https://medium.com/search?q=chatgpt">cliché</a>, but I believe we haven’t uncovered everything ChatGPT has to offer. It’s an amazing tool, and I plan to use it a lot more to make my life easier. Some examples:</p><ul><li>As an engineering manager, I’ve used it to help me think about personal goals for the developers — I took the suggestions, altered it myself a little bit, and used them.</li><li>I’ve asked it to help me develop a security and verification strategy for the product — it just reassured me what I already knew, which is also pretty good.</li><li>I’ve asked it to help me choose the correct team structure — it gave me some ideas for the future.</li><li>I’ve asked it to convert legacy code — works like magic!</li><li>I’ve asked it for the best directory structure for my mono repo — it challenged my assumptions and made me think of new ideas.</li></ul><p>And much more.</p><p>Share with me your unique uses of this amazing tool. Would love to hear your comments</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=6180dea4f290" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Choose the right company: How to optimize your next job search]]></title>
            <link>https://medium.com/@yanairon/choose-the-right-company-how-to-optimize-your-next-job-search-b6ae5d53d26a?source=rss-f60ce30ae8a9------2</link>
            <guid isPermaLink="false">https://medium.com/p/b6ae5d53d26a</guid>
            <category><![CDATA[decision-making]]></category>
            <category><![CDATA[job-hunting]]></category>
            <category><![CDATA[rd-managers]]></category>
            <category><![CDATA[tech-companies]]></category>
            <category><![CDATA[job-search]]></category>
            <dc:creator><![CDATA[Yanai Ron]]></dc:creator>
            <pubDate>Wed, 15 Dec 2021 15:59:01 GMT</pubDate>
            <atom:updated>2021-12-16T14:16:51.063Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*JKvOzb7DVwzVRwjEQPNU3w.jpeg" /></figure><p>Lately, I’ve been on the job hunt, again. After almost 4 years in my previous job, in a great company, I felt it is time for a change.</p><p>While trying to understand what’s the next step for me, I told myself:</p><blockquote>“This time i’m doing it right, this time I’m going to figure out the next place i’m going to work in, not (only) by gut feeling, the decision is going to be more structured, let’s optimize this”</blockquote><p>In other words: let’s take the <strong>data-driven approach</strong> this time.</p><p><strong><em>Disclaimer #1</em></strong></p><p><em>This post won’t be around how to search for a job, what’s the correct time to leave your job, how to </em><a href="https://resume.io/"><em>write your CV</em></a><em>, prepare for </em><a href="https://www.amazon.com/Cracking-Coding-Interview-Programming-Questions/dp/0984782850"><em>interviews</em></a><em> or </em><a href="https://www.audible.com/pd/Never-Split-the-Difference-Audiobook/B01CF5O89G"><em>negotiate</em></a><em> salary.</em></p><p><em>The internet is full with information about all that, I’ve nothing intelligent to add here.</em></p><p><em>I’m here to suggest a way to choose the correct company </em><strong><em>once you already have a few options.</em></strong></p><p><strong><em>Disclaimer #2</em></strong></p><p><em>My job search was in a place, time and profession (Tel Aviv, late 2021, R&amp;D manager in tech companies) in which the demand for employees was much bigger than the supply, and I am aware it’s not always like this. </em><strong><em>Sometimes you need to pick the job that is offered and you don’t have other options.</em></strong></p><p><em>The system I am suggesting doesn’t fit for these situations.</em></p><h4>Decisions</h4><p>So I have decided to leave my job, and started spreading the word among friend and searched for leads, got a couple of interviews and started to “feel the market”, and understand what’s in there for me.</p><p>This phase was about brainstorming (with myself, friends, family and mentors) and understand where I want to be, personally and professionally</p><h4>The excel file</h4><p>When I felt it’s too much information to hold in my head, I have created the Excel file, which later helped me make the final decision.</p><p>I’ve started with some <strong>general info</strong> I have gathered (all made up companies in this example, obviously)</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*T_c3kRaf2jZHlieAFjJl9Q.png" /><figcaption>First section, general info</figcaption></figure><p>What do we have here?</p><ul><li>Company name and website</li><li>What do they do (in a few words) and what is the market</li><li>What is the position i’m applying to</li><li>When was it founded, how many employees, how many employees in my proposed unit</li><li>Tech stack</li><li>Location (I like to work close to home so I can get there by bicycle, so that’s important to me)</li></ul><p>Basically, add here any general info that is important to you and you can gather (either ask or search the web)</p><h4>Section 2: Investments rounds</h4><p>After few interviews, I have decided to narrow down my search to startups in early stages, since leading R&amp;D in such a startups felt the right next step for me, and small startups is where I enjoy the most.</p><p>But how do I know if a startup will succeed? Obviously I can’t really know, but the investments they got might be the best prediction I can have at this point, so I have added this section (if I could find the info):</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*7U2v-2QPVQSr04tdyFyLbQ.png" /><figcaption>Second section, investments</figcaption></figure><p>What do we have here?</p><ul><li>Round (You can know a lot about the company’s stage by what’s investment round is it in)</li><li>$$$ Funded</li><li>Investors (Most important, can be a great signal if an important investor is in)</li></ul><h4>Section 3: The interview process</h4><p>In the next section, I have kept a log of where I am at in the process</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*tTIDkvF5h8lfl0_HsY2RlA.png" /><figcaption>Third section: Interview process</figcaption></figure><p>What do we have here?</p><ul><li>People I have met, It’s so hard to remember with whom I have talked, so that’s the reminder</li><li>My status (Applied, Interviewing, Rejected by me, Rejected by them, Offer, Accepted) — this is also the grouping of the Excel file, for easier browsing</li><li>Last communication date, which is updated after every call or interview, in order to feel when it’s too long and I might want to do a pulse check to see if it’s still on.</li><li>I didn’t add an interview notes section but if you add it, that’s the place to put it</li></ul><h4>Section 4: advantages and disadvantages</h4><p>For each of the companies in the list, there are advantages and disadvantages (this where the gut feeling usually kicks in), That’s the place to put anything you feel is a big yes or no</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/912/1*sb0BtVCuNzFrbUqYu4Nf4A.png" /><figcaption>Fourth section: advantages/disadvantages</figcaption></figure><h4>Section 4: The offer</h4><p>So you got an offer (congrats!), that’s the place to write its details so you can compare.</p><p>I’ve learned that many companies won’t talk about the offer unless they feel you’re in (When they give an offer to you, they hold it for the rest) so actually this section was empty most of the time.</p><p>In here you would write the salary, stock options and any other benefit</p><h4>Section 5: the grading system</h4><p>This is where it gets interesting.</p><p>To avoid the gut feeling bias, I’ve chosen 7 parameters with weights, and started filling 1–10 grades for each.</p><p>Later on, I have chosen the 3 most important to me (at the time) and did the weighted average again, to understand the situation better</p><p>As you may see, there’s usually no perfect score, but it helps with the decision</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*qPTlXGUa74urfw9A-91dkQ.png" /></figure><p>My initial parameters:</p><ul><li><strong>Product grade</strong> — how do I relate to the product, is the problem interesting for me to solve</li><li><strong>Tech grade</strong> — what’s the tech challenge, how do I relate to it</li><li><strong>People grade</strong> — the people I have met, how was the connection and vibe</li><li><strong>Company growth grade</strong> — Do I feel this company will grow?</li><li><strong>Position/Influence grade</strong> — How much influence will I have in the offered position</li><li><strong>Compensation grade</strong> — will they be able to meet my requirements</li><li><strong>Gut feeling grade</strong> — cause you gotta have that (^_^)</li></ul><p>I have put a weight for each one (total 100%) and used SUMPRODUCT function to calculate the total grade</p><p><em>Note: While there’s no “perfect score”, filling a value for each of these parameters forces you to think and consider them</em></p><p>Some valid params that I didn’t pick, but can be valuable to others:</p><ul><li>Commute time</li><li>Work/Life balance</li><li>Personal growth</li><li>etc…</li></ul><p>After working a while with that, I received an advice from a mentor who told me I cannot hold so many parameter in my head, and challenged me to choose my 3 most important ones, and I came up with <strong>Product, Influence and compensation.</strong></p><p>At the end, some of the companies rejected me (it always happen, for various reasons) but I had a good and solid sorted list to pick from.</p><p>The list showed there were companies that are not for me and others are, and helped me make a conscious, data-driven decision when moving on with the offers.</p><p>Wanna give this a try? you can download the template <a href="https://docs.google.com/spreadsheets/d/1mI59o25ZirAA9OGQGWS2p6xjQ9JFgmQ3AxYHdyIUFFI/edit?usp=sharing">here</a>.</p><p>Hopefully, this has given you some tips in how to make the correct decision when picking your next job from a list of good companies.</p><p>Do you have any other tips? I would love to hear about it in the comments section below :-)</p><p>Hope you enjoyed it, don’t forget to clap!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=b6ae5d53d26a" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Why should you build an organizational Slack bot?]]></title>
            <link>https://medium.com/tech-at-trax/why-should-you-build-an-organizational-slack-bot-c7cec814a0de?source=rss-f60ce30ae8a9------2</link>
            <guid isPermaLink="false">https://medium.com/p/c7cec814a0de</guid>
            <category><![CDATA[slack]]></category>
            <category><![CDATA[bots]]></category>
            <category><![CDATA[slackbot]]></category>
            <category><![CDATA[organizational-culture]]></category>
            <category><![CDATA[software-development]]></category>
            <dc:creator><![CDATA[Yanai Ron]]></dc:creator>
            <pubDate>Tue, 14 Apr 2020 12:21:27 GMT</pubDate>
            <atom:updated>2023-01-05T11:28:08.749Z</atom:updated>
            <content:encoded><![CDATA[<h3>Why you should build an organizational Slack bot?</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Fx1T_9H33xTTDag_8Niabg.png" /></figure><p>If you’re working in a tech organization, most chances are that you are using Slack to interact with coworkers. Did you know that you can build your own organizational Slack bot to enhance interaction between co-workers and to share knowledge?</p><p>In this post I will show you the simplicity and value of making time for you and the team to build one. I’ll also throw in some ideas to get you started.</p><h3>What are bots? Here’s the explanation from <a href="https://api.slack.com/bot-users">Slack</a>:</h3><blockquote><em>“A bot is a type of Slack App designed to interact with users via conversation…the same as a regular app: it can access the same range of APIs and do all of the magical things that a Slack App can do.</em></blockquote><blockquote><em>But when you build a bot for your Slack App, you’re giving that app a face, a name, and a personality, and encouraging users to talk to it. Your bot can send DMs, it can be mentioned by users, it can post messages or upload files, and it can be invited to channels — or kicked out. Bots are not cybernetic infiltration units, and it is unlikely that they dream of electric sheep, though we can’t rule it out. 🤖”</em></blockquote><figure><img alt="" src="https://cdn-images-1.medium.com/max/775/1*EjrAyDNpYA3QBPVd25P3cQ.png" /></figure><h3>Why do I need an organizational Slack bot?</h3><p>To be honest, you don’t really need it, but it can solve many problems your organization may have (and it’s easy and fun to write), such as:</p><h4>Knowledge Sharing</h4><p>Your Slack bot can be used to retrieve internal information, for example:</p><ul><li>Customer statistics</li><li>Employee roles, departments, birthdays</li><li>KPIs, open support tickets, system health</li><li>Product adoption, Sales data, top customers / customers at risk</li><li>Data for Salesforce: release notes, new versions, how-tos</li></ul><p>At Trax, we have many internal data sources (SQL DBs, No-SQL, internal APIs, etc.). The Slack bot can consolidate the interesting stuff and present it in an easily digestible way, the options are endless…</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/681/1*m7WnVGhKw7ONmYlU1J_whg.png" /><figcaption>Supply useful information about our customers</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/617/1*DEytG089n7NNwZcBxX07Pw.png" /><figcaption>Supply useful information about your mobile versions</figcaption></figure><h4>Provide easy access to common actions</h4><p>Your Slack bot can be a great tool to initiate actions, such as:</p><ul><li>Environment setup</li><li>Running internal scripts</li><li>Accessing APIs</li></ul><p>At Trax, we can copy a production environment to a testing environment in order to perform tests on real data, it’s a killer feature used daily by multiple departments:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/511/1*bICFKEQj98zGMHbRvq2Z9Q.png" /></figure><p>This is a valuable feature for multiple stakeholders in the organization, but in order to get wide usage we needed to make it accessible, and a Slackbot is the simple UI-free way to accomplish that.</p><p>We can also run internal jobs (we call it “Simon”):</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/576/1*2jHndz2YbBqcmUgMf9zyJg.png" /></figure><h3>Alright, I get it, I need all that, but why choose Slack?</h3><p>Great that you asked, there are many reasons to choose Slack for that:</p><ul><li>It’s already installed for everybody in your organization: HR, Finance, Sales, Technology, upper management, etc.</li><li>It’s a “UI without UI”, you don’t need to develop a fancy dashboard and employ designers to get the information to the organization</li><li>It’s so easy to implement, a few hours to set up everything for any passionate developer</li></ul><h3><strong>So it’s good for the company, but what’s in it for me?</strong></h3><p>Well, for starters, it’s an opportunity to work on something new, whether you’re a Frontend developer who wants to experience some Backend, or a Backend developer who wants to try out a new technology.</p><p>It’s small and well defined, and you get to do it on work hours because it’s useful at work! Perfect for a side-project, <strong>win win!</strong></p><h3>Okay, I’ll build it, but where should I start?</h3><p>Alright, firstly you’ll need a server with a public address/DNS, then…</p><ul><li>Pick the programming language of your choice, Node.js, Python or Golang are good starters for web servers</li><li>Write a simple REST API using <a href="https://slack.com/intl/en-il/help/articles/115005265703-Create-a-bot-for-your-workspace">this guide</a></li><li>Pick a cool <a href="https://www.userlike.com/en/blog/bot-names">name and avatar</a></li><li>Bonus: Track your bot usage using your favorite analytics platform (I use <a href="http://mixpanel.com/">Mixpanel</a>)</li></ul><p>You can start with <a href="https://github.com/yanairon/slack-bot-template">this</a> skeleton I’ve made using Node.js:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/278/1*et0opkcP4xsqn-BoQBfZGg.png" /></figure><p>Once the skeleton is set up, you can add more and more to it, the sky’s the limit! Here are some ideas:</p><ul><li>Provide visibility on customer’s statistics about system usage, features adoption, amount of data, etc.</li><li>Bonus: add some buttons that will lead to open issues, customers’ dashboards, etc.</li><li>Send a “Did you know” message from your bot once a week, with a trivia detail about the company, events that are happening, “kudos” to those special employees, etc.</li><li>Send notifications about employees’ birthdays, and let the other employees share a personalized message</li><li>Think about manual recurring operations your organization is doing, think about automating it with Slack</li></ul><p>Later on when it catches like wildfire in your organization, you can make it an internal open-source project for the rest of the company developers to contribute to.</p><h3>Wrapping up</h3><p>Now you should have a general idea of how an organizational slack bot can benefit you and your organization.</p><p>I’d love to hear about it, please share your ideas and success stories in the comments section, maybe I’ll implement them in Trax as well :)</p><p>Hope you enjoyed it, don’t forget to clap!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=c7cec814a0de" width="1" height="1" alt=""><hr><p><a href="https://medium.com/tech-at-trax/why-should-you-build-an-organizational-slack-bot-c7cec814a0de">Why should you build an organizational Slack bot?</a> was originally published in <a href="https://medium.com/tech-at-trax">Tech at Trax</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
    </channel>
</rss>