<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:dc="http://purl.org/dc/elements/1.1/">
  <channel>
    <title>DEV Community: Marcus Kim</title>
    <description>The latest articles on DEV Community by Marcus Kim (@marcusykim).</description>
    <link>https://dev.to/marcusykim</link>
    <image>
      <url>https://media2.dev.to/dynamic/image/width=90,height=90,fit=cover,gravity=auto,format=auto/https:%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Fuser%2Fprofile_image%2F3986100%2Fc1575634-3404-470c-8a8c-07bbc047ff7c.jpg</url>
      <title>DEV Community: Marcus Kim</title>
      <link>https://dev.to/marcusykim</link>
    </image>
    <atom:link rel="self" type="application/rss+xml" href="https://dev.to/feed/marcusykim"/>
    <language>en</language>
    <item>
      <title>Before You Ship an AI-Built Web Feature, Test the Browser Fallback</title>
      <dc:creator>Marcus Kim</dc:creator>
      <pubDate>Sat, 14 Nov 2026 19:40:37 +0000</pubDate>
      <link>https://dev.to/marcusykim/before-you-ship-an-ai-built-web-feature-test-the-browser-fallback-3j9e</link>
      <guid>https://dev.to/marcusykim/before-you-ship-an-ai-built-web-feature-test-the-browser-fallback-3j9e</guid>
      <description>&lt;p&gt;Imagine you're building a workshop registration page. An AI coding tool adds a polished session picker. You open the page, pick the afternoon slot, and register. Good enough to send to the client?&lt;/p&gt;

&lt;p&gt;Not yet. You know the picker worked in the browser you opened. You don't know what a visitor sees when their browser can't apply the styling or positioning the picker relies on.&lt;/p&gt;

&lt;p&gt;This article was prepared with AI assistance. The workshop example is hypothetical.&lt;/p&gt;

&lt;p&gt;On November 10, Chrome for Developers announced &lt;a href="https://developer.chrome.com/blog/modern-web-guidance-v1" rel="noopener noreferrer"&gt;Modern Web Guidance 1.0&lt;/a&gt;, with Firefox and Edge joining the effort. The project gives coding agents web platform guidance that includes browser compatibility data. Its &lt;a href="https://developer.chrome.com/blog/cross-browser-by-default?hl=en" rel="noopener noreferrer"&gt;fallback guide&lt;/a&gt; makes a distinction worth keeping even if you never install it: sometimes an unsupported feature can disappear harmlessly, and sometimes you need a second way to complete the task.&lt;/p&gt;

&lt;p&gt;Here's the release checklist I'd use for that session picker.&lt;/p&gt;

&lt;h2&gt;
  
  
  1. Name the browsers before you name the solution
&lt;/h2&gt;

&lt;p&gt;Write down the browser and device combinations the feature needs to support. Use the client's known requirements or product traffic when you have it. If you're starting from scratch, pick a reasonable initial support target and label it as an assumption. Don't let the coding tool infer the target from whichever browser happens to be on your laptop.&lt;/p&gt;

&lt;p&gt;&lt;a href="https://web.dev/baseline" rel="noopener noreferrer"&gt;Baseline&lt;/a&gt; is a useful starting point. Newly available means a feature works across its core browsers; widely available means 30 months have passed since that point. Neither tells you which versions your particular visitors run. Ask the assistant to name the exact feature it wants to use and explain how it fits your targets. Check that answer before you approve the approach.&lt;/p&gt;

&lt;h2&gt;
  
  
  2. Define what must work without the enhancement
&lt;/h2&gt;

&lt;p&gt;For the workshop page, I'd start with a labeled native select and a submit button. If the decorative layout doesn't apply, a user should still be able to see the available sessions, select one, submit, and read which session they booked. The native control doesn't have to look like the enhanced control. It has to finish the same job.&lt;/p&gt;

&lt;p&gt;Make that difference explicit in the ticket: "If the enhanced picker isn't supported, show the regular session field. Submitting either version must use the same session identifier and show the same confirmation." Keep the enhancement separate from the submission logic so both paths don't drift into maintaining their own rules for a sold-out slot.&lt;/p&gt;

&lt;h2&gt;
  
  
  3. Run the same task through both paths
&lt;/h2&gt;

&lt;p&gt;Try a registration in a supported browser, then repeat it where the feature isn't supported. Use test data and check the confirmation, not just whether the button was clickable. On both paths, try submitting without a selection and make sure the error tells you what to fix. Check that you can choose and submit with the keyboard without losing track of focus.&lt;/p&gt;

&lt;p&gt;If you can't get the target browser right away, exercising the fallback in a test build can catch a logic error. Record that as fallback-path evidence, not proof that the target browser works. A smaller viewport is useful for layout testing, but it doesn't change which features the browser implements.&lt;/p&gt;

&lt;p&gt;My handoff would be two short rows: browser and version, picker path, session chosen, confirmation observed, and any failure. If only one row has results, that's the honest state of the release.&lt;/p&gt;

&lt;p&gt;The question isn't whether the enhanced picker looks good. It's whether someone can still register when that enhancement isn't there.&lt;/p&gt;

&lt;p&gt;The &lt;a href="https://marcusykim.gumroad.com/l/ai-app-builder-starter-prompts" rel="noopener noreferrer"&gt;$3 AI App Builder Starter Prompts&lt;/a&gt; help turn a feature request into checks you can actually run. The &lt;a href="https://marcusykim.gumroad.com/l/ai-app-builder-book-only" rel="noopener noreferrer"&gt;$9 AI App Builder From Zero e-book&lt;/a&gt; covers the path from planning to testing and release. The &lt;a href="https://marcusykim.gumroad.com/l/ai-app-builder-from-zero" rel="noopener noreferrer"&gt;$10 learning bundle&lt;/a&gt; includes both.&lt;/p&gt;

&lt;p&gt;&lt;a href="https://marcusykim.com/review-radar/" rel="noopener noreferrer"&gt;Bootcamp Bundle (Review Radar)&lt;/a&gt; is coming soon; the preview and waitlist are open, and checkout is closed.&lt;/p&gt;

&lt;p&gt;You can also find me here:&lt;/p&gt;

&lt;p&gt;Medium: &lt;a href="https://medium.com/@marcusykim" rel="noopener noreferrer"&gt;https://medium.com/@marcusykim&lt;/a&gt;&lt;br&gt;
DEV.to: &lt;a href="https://dev.to/marcusykim"&gt;https://dev.to/marcusykim&lt;/a&gt;&lt;br&gt;
Website: &lt;a href="https://marcusykim.com/" rel="noopener noreferrer"&gt;https://marcusykim.com/&lt;/a&gt;&lt;br&gt;
X: &lt;a href="https://x.com/marcusykim" rel="noopener noreferrer"&gt;https://x.com/marcusykim&lt;/a&gt;&lt;br&gt;
LinkedIn: &lt;a href="https://www.linkedin.com/in/marcusykim/" rel="noopener noreferrer"&gt;https://www.linkedin.com/in/marcusykim/&lt;/a&gt;&lt;br&gt;
Upwork: &lt;a href="https://www.upwork.com/freelancers/marcusykim" rel="noopener noreferrer"&gt;https://www.upwork.com/freelancers/marcusykim&lt;/a&gt;&lt;/p&gt;

</description>
      <category>webdev</category>
      <category>testing</category>
      <category>css</category>
      <category>a11y</category>
    </item>
    <item>
      <title>Your Local AWS Test Passed. What Still Needs a Real Environment?</title>
      <dc:creator>Marcus Kim</dc:creator>
      <pubDate>Sat, 14 Nov 2026 18:35:56 +0000</pubDate>
      <link>https://dev.to/marcusykim/your-local-aws-test-passed-what-still-needs-a-real-environment-1bc4</link>
      <guid>https://dev.to/marcusykim/your-local-aws-test-passed-what-still-needs-a-real-environment-1bc4</guid>
      <description>&lt;p&gt;You ask an AI coding tool to build a waitlist endpoint. It adds a test that writes a signup to a local DynamoDB table. The test passes. Does the deployed app have permission to write to the right table?&lt;/p&gt;

&lt;p&gt;This article was prepared with AI assistance. The waitlist example is hypothetical.&lt;/p&gt;

&lt;p&gt;That test can't tell you. It's still a useful test, as long as you don't ask it to answer the wrong question.&lt;/p&gt;

&lt;p&gt;On November 11, &lt;a href="https://aws.amazon.com/about-aws/whats-new/2026/11/aws-emulator-now-available/" rel="noopener noreferrer"&gt;AWS announced AWS Emulator&lt;/a&gt;, a way to run supported AWS operations locally or in CI using the AWS SDK or CLI. The emulator holds resource state in memory while it runs. An unsupported operation can return &lt;code&gt;501 Not Implemented&lt;/code&gt;. The &lt;a href="https://aws.amazon.com/blogs/aws/test-your-applications-against-aws-locally-with-aws-emulator/" rel="noopener noreferrer"&gt;AWS launch guide&lt;/a&gt; also says the emulator doesn't evaluate IAM policies the same way AWS does. That's a boundary worth putting into your test plan before an assistant starts writing tests.&lt;/p&gt;

&lt;h2&gt;
  
  
  Give the local test one job
&lt;/h2&gt;

&lt;p&gt;Use fictional signups and an isolated table. Test that a valid request writes one record, that an invalid request writes none, and that a duplicate request gets the response you intended. If retry behavior matters, send the same request twice and inspect the stored state. An HTTP success response alone won't tell you whether the handler stored two records.&lt;/p&gt;

&lt;p&gt;Point the test configuration at the emulator with test-only credentials. Make the test fail clearly if the endpoint isn't the expected local target. A test suite should never discover your real AWS account because someone forgot to set an environment variable. If the emulator returns &lt;code&gt;501&lt;/code&gt;, record the operation it couldn't exercise; don't stub away the result and report that the integration passed.&lt;/p&gt;

&lt;h2&gt;
  
  
  Give the staging test a different job
&lt;/h2&gt;

&lt;p&gt;Use an existing authorized staging environment when one is available. Run a small check with the exact role the deployed function will use. Verify it can write a test signup to the staging table and cannot write to a resource outside its intended scope. Check the expected destination and use clearly labeled synthetic data. Don't prove staging by sending real customer messages or using production records.&lt;/p&gt;

&lt;p&gt;If an emulator test passes and staging reports an access error, check the actual role, target resource, and applicable policy first. Don't grant broad permissions just to make the test green. The access error may be the test discovering a real difference between the local setup and what you intend to deploy.&lt;/p&gt;

&lt;h2&gt;
  
  
  Ask the assistant to report both outcomes separately
&lt;/h2&gt;

&lt;p&gt;I'd put this in the issue: "Report local request handling and staging permissions as separate results. Show the destination and the test case for each. If staging is unavailable, mark permissions unverified. Don't create resources or change permissions to get a green result."&lt;/p&gt;

&lt;p&gt;That gives you a more useful handoff than a single "tested" checkbox. The emulator can help answer whether your code behaves the way you expect. The staging check tells you whether it behaves that way in the environment, under the identity, where it will actually run.&lt;/p&gt;

&lt;p&gt;The &lt;a href="https://marcusykim.gumroad.com/l/ai-app-builder-starter-prompts" rel="noopener noreferrer"&gt;$3 AI App Builder Starter Prompts&lt;/a&gt; help spell out boundaries like these before handing work to a coding tool. The &lt;a href="https://marcusykim.gumroad.com/l/ai-app-builder-book-only" rel="noopener noreferrer"&gt;$9 AI App Builder From Zero e-book&lt;/a&gt; walks through planning, testing, and release. The &lt;a href="https://marcusykim.gumroad.com/l/ai-app-builder-from-zero" rel="noopener noreferrer"&gt;$10 learning bundle&lt;/a&gt; includes both.&lt;/p&gt;

&lt;p&gt;&lt;a href="https://marcusykim.com/review-radar/" rel="noopener noreferrer"&gt;Bootcamp Bundle (Review Radar)&lt;/a&gt; is coming soon; the preview and waitlist are open, and checkout is closed.&lt;/p&gt;

&lt;p&gt;You can also find me here:&lt;/p&gt;

&lt;p&gt;Medium: &lt;a href="https://medium.com/@marcusykim" rel="noopener noreferrer"&gt;https://medium.com/@marcusykim&lt;/a&gt;&lt;br&gt;
DEV.to: &lt;a href="https://dev.to/marcusykim"&gt;https://dev.to/marcusykim&lt;/a&gt;&lt;br&gt;
Website: &lt;a href="https://marcusykim.com/" rel="noopener noreferrer"&gt;https://marcusykim.com/&lt;/a&gt;&lt;br&gt;
X: &lt;a href="https://x.com/marcusykim" rel="noopener noreferrer"&gt;https://x.com/marcusykim&lt;/a&gt;&lt;br&gt;
LinkedIn: &lt;a href="https://www.linkedin.com/in/marcusykim/" rel="noopener noreferrer"&gt;https://www.linkedin.com/in/marcusykim/&lt;/a&gt;&lt;br&gt;
Upwork: &lt;a href="https://www.upwork.com/freelancers/marcusykim" rel="noopener noreferrer"&gt;https://www.upwork.com/freelancers/marcusykim&lt;/a&gt;&lt;/p&gt;

</description>
      <category>aws</category>
      <category>testing</category>
      <category>webdev</category>
      <category>devops</category>
    </item>
    <item>
      <title>A Postgres Upgrade Is Ready When Your App Can Use the Restored Data</title>
      <dc:creator>Marcus Kim</dc:creator>
      <pubDate>Sat, 14 Nov 2026 18:19:48 +0000</pubDate>
      <link>https://dev.to/marcusykim/a-postgres-upgrade-is-ready-when-your-app-can-use-the-restored-data-348a</link>
      <guid>https://dev.to/marcusykim/a-postgres-upgrade-is-ready-when-your-app-can-use-the-restored-data-348a</guid>
      <description>&lt;p&gt;Imagine a small appointment app. You upgrade a copy of its database, the restore finishes, and the tables look right. Then the app tries to confirm an appointment and gets a permission error.&lt;/p&gt;

&lt;p&gt;This article was prepared with AI assistance. The appointment app and rehearsal below are hypothetical.&lt;/p&gt;

&lt;p&gt;Both observations can be true. A restored table doesn't prove that the app's database role can use it. It also doesn't prove that each customer can see only their own appointments.&lt;/p&gt;

&lt;p&gt;On November 12, the PostgreSQL Global Development Group &lt;a href="https://www.postgresql.org/about/news/postgresql-187-1712-1616-1520-1425-and-19-rc-2-released-3442/" rel="noopener noreferrer"&gt;released PostgreSQL 14.25&lt;/a&gt; and confirmed that it was the final release of version 14. If your app still runs on 14, make a plan to move to a supported major version. The plan should include a rehearsal that tests your app, not just the database tools.&lt;/p&gt;

&lt;h2&gt;
  
  
  Write down what the rehearsal has to prove
&lt;/h2&gt;

&lt;p&gt;First confirm the version that actually serves the app. Your laptop, staging environment, and production database may all be different. Check which versions your host supports, what upgrade paths it offers, and whether your extensions are available on the target version. Don't let a coding assistant choose the target from a version number alone.&lt;/p&gt;

&lt;p&gt;For the appointment app, I'd name three checks: a customer can see their own booking, can't see another customer's booking, and can reschedule an eligible booking. Those checks cover a read, an access boundary, and a write that matters to the business.&lt;/p&gt;

&lt;h2&gt;
  
  
  Restore to a separate target
&lt;/h2&gt;

&lt;p&gt;Use a fresh target that cannot receive production traffic or send production email. Use synthetic data to develop the test; if a representative backup is necessary, handle it inside the approved environment with the same access controls as production. Don't upload it to an AI chat or move it to a personal machine.&lt;/p&gt;

&lt;p&gt;PostgreSQL's &lt;a href="https://www.postgresql.org/docs/current/backup-dump.html" rel="noopener noreferrer"&gt;SQL dump documentation&lt;/a&gt; explains that a single-database dump doesn't capture cluster-wide objects such as roles. Managed providers may handle those separately. Verify that the intended application role, grants, extensions, and configuration exist on the restored target. Test using the role the app actually uses, not an administrator account that can hide missing permissions.&lt;/p&gt;

&lt;p&gt;Record the restore exit status and read its errors. For an archive restore, &lt;a href="https://www.postgresql.org/docs/current/app-pgrestore.html" rel="noopener noreferrer"&gt;PostgreSQL documents an option to stop at the first SQL error&lt;/a&gt;. That makes a broken rehearsal easier to diagnose; it doesn't turn the absence of a restore error into proof that the application works.&lt;/p&gt;

&lt;h2&gt;
  
  
  Practice the switch as well as the restore
&lt;/h2&gt;

&lt;p&gt;Compare counts for a few meaningful records, then run the three checks through the app with test users. Confirm that changing an appointment leaves the related records consistent. Time the whole rehearsal from starting the backup or provider workflow through the last app check. That gives you a better estimate of the maintenance window than the restore time alone.&lt;/p&gt;

&lt;p&gt;Decide who can stop the cutover and how you'll handle writes. Switching a connection string back is simple only if the old and new databases haven't diverged. Before letting real users write to the new database, agree on when the old one stops accepting writes and what recovery means after the new one has accepted them.&lt;/p&gt;

&lt;p&gt;The release question isn't "Did the database come back?" It's "Can the right user do the right thing, and can we recover if the answer is no?" Write down the evidence before you move traffic.&lt;/p&gt;

&lt;p&gt;The &lt;a href="https://marcusykim.gumroad.com/l/ai-app-builder-starter-prompts" rel="noopener noreferrer"&gt;$3 AI App Builder Starter Prompts&lt;/a&gt; help turn a vague upgrade request into a plan with explicit checks. The &lt;a href="https://marcusykim.gumroad.com/l/ai-app-builder-book-only" rel="noopener noreferrer"&gt;$9 AI App Builder From Zero e-book&lt;/a&gt; covers the broader path from scope to release. The &lt;a href="https://marcusykim.gumroad.com/l/ai-app-builder-from-zero" rel="noopener noreferrer"&gt;$10 learning bundle&lt;/a&gt; includes both.&lt;/p&gt;

&lt;p&gt;&lt;a href="https://marcusykim.com/review-radar/" rel="noopener noreferrer"&gt;Bootcamp Bundle (Review Radar)&lt;/a&gt; is coming soon; the preview and waitlist are open, and checkout is closed.&lt;/p&gt;

&lt;p&gt;You can also find me here:&lt;/p&gt;

&lt;p&gt;Medium: &lt;a href="https://medium.com/@marcusykim" rel="noopener noreferrer"&gt;https://medium.com/@marcusykim&lt;/a&gt;&lt;br&gt;
DEV.to: &lt;a href="https://dev.to/marcusykim"&gt;https://dev.to/marcusykim&lt;/a&gt;&lt;br&gt;
Website: &lt;a href="https://marcusykim.com/" rel="noopener noreferrer"&gt;https://marcusykim.com/&lt;/a&gt;&lt;br&gt;
X: &lt;a href="https://x.com/marcusykim" rel="noopener noreferrer"&gt;https://x.com/marcusykim&lt;/a&gt;&lt;br&gt;
LinkedIn: &lt;a href="https://www.linkedin.com/in/marcusykim/" rel="noopener noreferrer"&gt;https://www.linkedin.com/in/marcusykim/&lt;/a&gt;&lt;br&gt;
Upwork: &lt;a href="https://www.upwork.com/freelancers/marcusykim" rel="noopener noreferrer"&gt;https://www.upwork.com/freelancers/marcusykim&lt;/a&gt;&lt;/p&gt;

</description>
      <category>postgres</category>
      <category>webdev</category>
      <category>testing</category>
      <category>devops</category>
    </item>
    <item>
      <title>Give Your Client Demo an Expiration Date</title>
      <dc:creator>Marcus Kim</dc:creator>
      <pubDate>Thu, 12 Nov 2026 22:26:25 +0000</pubDate>
      <link>https://dev.to/marcusykim/give-your-client-demo-an-expiration-date-99c</link>
      <guid>https://dev.to/marcusykim/give-your-client-demo-an-expiration-date-99c</guid>
      <description>&lt;p&gt;You send a client a demo link on Monday. On Friday they approve the flow. Three weeks later someone forwards the same link and asks why it doesn't have the new settings screen.&lt;/p&gt;

&lt;p&gt;That isn't necessarily a deployment bug. It may be a handoff bug: nobody said which URL was temporary, when it would stop working, or what would replace it.&lt;/p&gt;

&lt;p&gt;On November 6, Vercel &lt;a href="https://vercel.com/changelog/vercel-cli-can-now-set-new-projects-to-expire" rel="noopener noreferrer"&gt;announced a CLI option for setting an expiration on a new project&lt;/a&gt;. When the deploy creates a project, you can choose a duration and the CLI prints the deadline. Passing the option when deploying to an existing project doesn't change that project's expiration. You can remove a scheduled expiration with &lt;code&gt;vercel project keep&lt;/code&gt; before the deadline.&lt;/p&gt;

&lt;p&gt;The distinction matters: the expiration applies to the &lt;strong&gt;project&lt;/strong&gt;, not just the link you sent. &lt;a href="https://vercel.com/docs/projects/managing-projects#deleting-a-project" rel="noopener noreferrer"&gt;Vercel documents that deleting a project also removes its deployments, domains, environment variables, and settings&lt;/a&gt;. I would reserve this for a deliberately disposable project, not an existing staging or production environment.&lt;/p&gt;

&lt;p&gt;This article was prepared with AI assistance. The appointment app and review plan below are hypothetical.&lt;/p&gt;

&lt;h2&gt;
  
  
  Decide what you are asking the client to review
&lt;/h2&gt;

&lt;p&gt;Suppose the app lets a customer pick a time, see the cancellation policy, and review an appointment before confirming. For this demo, I would ask the client to try just that path with fake customers and test slots. I would leave real calendars, payments, and email delivery disconnected.&lt;/p&gt;

&lt;p&gt;Write down three things before deploying: which behavior is up for review, which project is disposable, and which accounts or resources must never be connected. That gives an AI coding tool a boundary it can actually check. My &lt;a href="https://marcusykim.gumroad.com/l/ai-app-builder-starter-prompts" rel="noopener noreferrer"&gt;$3 AI App Builder Starter Prompts&lt;/a&gt; help turn an app idea into an explicit scope and test plan. You can also start with those three lines in any project notes file.&lt;/p&gt;

&lt;h2&gt;
  
  
  Put the review deadline before the deletion deadline
&lt;/h2&gt;

&lt;p&gt;I would send the client a note like this:&lt;/p&gt;

&lt;blockquote&gt;
&lt;p&gt;Please try booking and canceling a test appointment by Thursday at 3 p.m. Pacific. This is a demo with sample data, not the live app. The link is scheduled to expire Monday at noon Pacific. I'll record the accepted changes and confirm whether we're retiring the demo or setting up a separate staging environment before then.&lt;/p&gt;
&lt;/blockquote&gt;

&lt;p&gt;Use the actual timestamp reported by the provider. The gap between feedback and expiration gives you time to save decisions and handle a request to keep the demo. Record who can make that call. Silence isn't approval to move a demo into production.&lt;/p&gt;

&lt;p&gt;An expiration also doesn't control who can see the demo while it's online. &lt;a href="https://vercel.com/docs/deployments/sharing-deployments" rel="noopener noreferrer"&gt;Vercel's preview-sharing guide&lt;/a&gt; distinguishes inviting specific reviewers from using a link that grants access. Choose the narrowest access that fits the review. Test it from the reviewer's perspective; a link that works for you while you're signed in as the owner proves very little about what the client can open.&lt;/p&gt;

&lt;h2&gt;
  
  
  Keep the work, not the disposable environment
&lt;/h2&gt;

&lt;p&gt;Before sending the link, I would record the revision that produced it, how to recreate the sample data, and where feedback will be collected. If the client sees a wrong cancellation message, the accepted wording belongs in the project notes or issue tracker, not only in a comment attached to a preview you plan to delete.&lt;/p&gt;

&lt;p&gt;For the same reason, inventory anything outside the project. A separate test database, storage bucket, or email sandbox needs its own cleanup decision. Don't assume expiring a deployment project also deletes a service owned somewhere else. Never put real customer records into the demo in the first place.&lt;/p&gt;

&lt;h2&gt;
  
  
  Make the next URL a deliberate decision
&lt;/h2&gt;

&lt;p&gt;When the review ends, choose one of three outcomes:&lt;/p&gt;

&lt;ol&gt;
&lt;li&gt;
&lt;strong&gt;Retire the demo.&lt;/strong&gt; Save accepted feedback and reproducible setup notes. Tell reviewers the link is going away and check that only the disposable project is scheduled to expire.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Keep it temporarily.&lt;/strong&gt; Get an explicit decision from the owner, confirm the correct project, remove its expiration before the deadline, and set a new review date. Keeping a demo does not make it production.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Build a separately owned environment.&lt;/strong&gt; Set up the client-approved staging or production project, verify access and integrations, then share the new URL. Check that the original demo is not still the link people are relying on.&lt;/li&gt;
&lt;/ol&gt;

&lt;p&gt;The useful handoff is a short record: what the client reviewed, what they accepted, where the work survives, and which link is now authoritative. The timer helps clean up the demo. The record is what keeps the decision from disappearing with it.&lt;/p&gt;

&lt;p&gt;For a structured path through scope, testing, and launch, see the &lt;a href="https://marcusykim.gumroad.com/l/ai-app-builder-book-only" rel="noopener noreferrer"&gt;$9 AI App Builder From Zero field manual&lt;/a&gt;. The &lt;a href="https://marcusykim.gumroad.com/l/ai-app-builder-starter-prompts" rel="noopener noreferrer"&gt;$3 Starter Prompts&lt;/a&gt; are available separately, or get the &lt;a href="https://marcusykim.gumroad.com/l/ai-app-builder-from-zero" rel="noopener noreferrer"&gt;book and all 40 prompts in the $10 learning bundle&lt;/a&gt;.&lt;/p&gt;

&lt;p&gt;Bootcamp Bundle (Review Radar) is coming soon. Preview it or request waitlist updates; checkout remains closed:&lt;/p&gt;

&lt;p&gt;&lt;a href="https://marcusykim.com/review-radar/" rel="noopener noreferrer"&gt;https://marcusykim.com/review-radar/&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;You can also find me here:&lt;/p&gt;

&lt;p&gt;Medium: &lt;a href="https://medium.com/@marcusykim" rel="noopener noreferrer"&gt;https://medium.com/@marcusykim&lt;/a&gt;&lt;br&gt;
DEV.to: &lt;a href="https://dev.to/marcusykim"&gt;https://dev.to/marcusykim&lt;/a&gt;&lt;br&gt;
Website: &lt;a href="https://marcusykim.com/" rel="noopener noreferrer"&gt;https://marcusykim.com/&lt;/a&gt;&lt;br&gt;
X: &lt;a href="https://x.com/marcusykim" rel="noopener noreferrer"&gt;https://x.com/marcusykim&lt;/a&gt;&lt;br&gt;
LinkedIn: &lt;a href="https://www.linkedin.com/in/marcusykim/" rel="noopener noreferrer"&gt;https://www.linkedin.com/in/marcusykim/&lt;/a&gt;&lt;br&gt;
Upwork: &lt;a href="https://www.upwork.com/freelancers/marcusykim" rel="noopener noreferrer"&gt;https://www.upwork.com/freelancers/marcusykim&lt;/a&gt;&lt;/p&gt;

</description>
      <category>beginners</category>
      <category>webdev</category>
      <category>programming</category>
      <category>freelance</category>
    </item>
    <item>
      <title>Cloudflare's New DNS Editor: A Beginner's Plan for Connecting an App Domain</title>
      <dc:creator>Marcus Kim</dc:creator>
      <pubDate>Sun, 01 Nov 2026 00:27:27 +0000</pubDate>
      <link>https://dev.to/marcusykim/cloudflares-new-dns-editor-a-beginners-plan-for-connecting-an-app-domain-4k8j</link>
      <guid>https://dev.to/marcusykim/cloudflares-new-dns-editor-a-beginners-plan-for-connecting-an-app-domain-4k8j</guid>
      <description>&lt;p&gt;Your AI-built app works at the hosting company's preview address. Now you want it at your own domain. The assistant tells you to change a DNS record, and the dashboard shows a successful save.&lt;/p&gt;

&lt;p&gt;Is the app live?&lt;/p&gt;

&lt;p&gt;Not necessarily. You have changed one part of the route a visitor takes. You still need to prove that the intended hostname reaches the intended application, over a working secure connection, with the behavior you actually built.&lt;/p&gt;

&lt;p&gt;This article was prepared with AI assistance. The examples are proposed checks for a hypothetical app, not a report of a production migration I performed.&lt;/p&gt;

&lt;p&gt;On October 30, 2026, Cloudflare &lt;a href="https://developers.cloudflare.com/changelog/post/2026-10-30-classic-dns-records-page-retired/" rel="noopener noreferrer"&gt;retired its classic DNS records page&lt;/a&gt;. Its newer editor is now the default across all plans. The update also confirms that you can change an existing record's type, such as from A to CNAME, directly in the dashboard.&lt;/p&gt;

&lt;p&gt;That is a useful interface improvement. It is also a good reason to stop following old screenshots without understanding what their fields mean.&lt;/p&gt;

&lt;p&gt;My rule for a beginner is simple: explain the intended hostname change in plain language before asking AI to make it.&lt;/p&gt;

&lt;h2&gt;
  
  
  Start with one hostname, not the whole domain
&lt;/h2&gt;

&lt;p&gt;Imagine a small appointment app. Your marketing site lives at &lt;code&gt;www.example.com&lt;/code&gt;, the app will live at &lt;code&gt;app.example.com&lt;/code&gt;, and email already works for the business. These are illustrative names, not configuration values to copy.&lt;/p&gt;

&lt;p&gt;The requested change is to connect the app hostname. It is not permission to replace the marketing site, change nameservers, delete unfamiliar records, or alter email delivery.&lt;/p&gt;

&lt;p&gt;I would write this first:&lt;/p&gt;

&lt;p&gt;"Only app.example.com should change. It should reach the deployment identified by our hosting provider. The marketing site and email records must remain unchanged."&lt;/p&gt;

&lt;p&gt;That one sentence makes an assistant's proposed diff much easier to judge. A suggestion to rewrite every record is now visibly outside the job.&lt;/p&gt;

&lt;p&gt;If you need help turning a vague build request into explicit boundaries, my &lt;a href="https://marcusykim.gumroad.com/l/ai-app-builder-starter-prompts" rel="noopener noreferrer"&gt;$3 AI App Builder Starter Prompts&lt;/a&gt; provide a guided starting point. You can also use the change note below on its own.&lt;/p&gt;

&lt;h2&gt;
  
  
  Read the record as a statement
&lt;/h2&gt;

&lt;p&gt;Cloudflare's &lt;a href="https://developers.cloudflare.com/dns/manage-dns-records/reference/dns-record-types/" rel="noopener noreferrer"&gt;record-type reference&lt;/a&gt; distinguishes an A record, which maps a name to an IPv4 address, from an AAAA record for an IPv6 address and a CNAME record that points to another hostname.&lt;/p&gt;

&lt;p&gt;Those are different meanings, not three interchangeable ways to paste a website URL. A DNS target is not an HTTPS URL with a path such as &lt;code&gt;/dashboard&lt;/code&gt;.&lt;/p&gt;

&lt;p&gt;Use the exact record type and destination supplied by your host for that project. Do not ask AI to infer the destination from a company name, an old tutorial, or another project's configuration.&lt;/p&gt;

&lt;p&gt;Before changing anything, record the current name, type, value, proxy status, and TTL. Note whether the hostname already has other records and ask the provider's documentation what combinations are supported. Save enough information to restore the specific previous configuration without exposing account secrets.&lt;/p&gt;

&lt;p&gt;Changing the record's type may be one click in the new editor. It still changes what the record says.&lt;/p&gt;

&lt;h2&gt;
  
  
  Decide whether traffic should pass through a proxy
&lt;/h2&gt;

&lt;p&gt;The orange cloud is not a generic indicator that a domain is configured correctly.&lt;/p&gt;

&lt;p&gt;Cloudflare's &lt;a href="https://developers.cloudflare.com/dns/proxy-status/" rel="noopener noreferrer"&gt;proxy-status documentation&lt;/a&gt; explains that a proxied record routes HTTP/HTTPS traffic through Cloudflare. A DNS-only record directs it to the origin without that HTTP proxy path. Only A, AAAA, and CNAME records can be proxied; MX and TXT records are DNS-only.&lt;/p&gt;

&lt;p&gt;The important beginner question is therefore not "Which icon looks enabled?" It is "Which traffic path does this service support and require?"&lt;/p&gt;

&lt;p&gt;A website hostname and a record used to prove ownership can need different treatment. Follow the hosting or verification provider's instructions for each purpose. Do not change proxy status merely to make an error disappear, particularly if doing so would remove protections you depend on.&lt;/p&gt;

&lt;p&gt;For the hypothetical appointment app, write down the expected path before the change: visitor, optional proxy, hosting project, application. If you cannot name the hosting project, you are not ready to change the destination.&lt;/p&gt;

&lt;h2&gt;
  
  
  Keep a short change note
&lt;/h2&gt;

&lt;p&gt;Here is the note I would give an AI coding assistant before authorizing a production edit:&lt;/p&gt;

&lt;ol&gt;
&lt;li&gt;
&lt;strong&gt;Scope:&lt;/strong&gt; the exact hostname being changed and the services that must remain untouched.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Before:&lt;/strong&gt; the current record and the evidence that it belongs to this hostname.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;After:&lt;/strong&gt; the proposed record, supported by this project's hosting instructions.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Traffic path:&lt;/strong&gt; whether the record is proxied and why that choice is supported.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Checks:&lt;/strong&gt; what will establish correct DNS, a working secure connection, and the intended app behavior separately.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Recovery:&lt;/strong&gt; the specific previous values, who can restore them, and the failure that would trigger restoration.&lt;/li&gt;
&lt;/ol&gt;

&lt;p&gt;Ask the assistant to identify unknowns rather than completing this note with plausible guesses. A blank destination is safer than the wrong destination presented confidently.&lt;/p&gt;

&lt;p&gt;This is intentionally small. You do not need a migration dashboard for a first app. You do need a record of what you meant to change.&lt;/p&gt;

&lt;h2&gt;
  
  
  A saved record is only the first receipt
&lt;/h2&gt;

&lt;p&gt;After the change, collect three different kinds of evidence.&lt;/p&gt;

&lt;p&gt;First, inspect the DNS answer for the exact hostname and compare it with the expected behavior. For a proxied hostname, seeing Cloudflare's addresses can be correct; looking only for your origin IP would be the wrong test.&lt;/p&gt;

&lt;p&gt;Second, open the intended HTTPS address and confirm that it reaches the right application without a certificate warning. Do not bypass a browser warning to declare the launch successful.&lt;/p&gt;

&lt;p&gt;Third, perform a harmless representative workflow with test data. For our appointment example, that might be opening the booking page and verifying its available-time display. Do not create real bookings, send customer messages, or trigger charges just to make a checklist look complete.&lt;/p&gt;

&lt;p&gt;A successful DNS lookup cannot prove that the app's environment variables, database, routing, or sign-in callbacks are correct. A working preview address cannot prove that the custom hostname is configured. Keep the results separate so the next fix targets the actual failing layer.&lt;/p&gt;

&lt;h2&gt;
  
  
  Waiting is not the same as verification
&lt;/h2&gt;

&lt;p&gt;Cloudflare's &lt;a href="https://developers.cloudflare.com/dns/manage-dns-records/reference/ttl/" rel="noopener noreferrer"&gt;TTL documentation&lt;/a&gt; explains that TTL affects how long DNS responses remain cached. Its proxied records use Auto, currently 300 seconds, and that setting is not editable. The documentation also warns that local caches can make a change take longer to appear.&lt;/p&gt;

&lt;p&gt;So "five minutes passed" is not a universal completion test. Nor does lowering a TTL now erase an answer that another resolver already cached under the previous value.&lt;/p&gt;

&lt;p&gt;Record when you changed the hostname and what each check returned. If different clients see different results, preserve that distinction instead of repeatedly editing records in response to every refresh.&lt;/p&gt;

&lt;p&gt;This is also a limit of rollback: restoring the previous record does not instantly erase every cached answer. Keep the old service available for an appropriate transition period and follow the provider's migration guidance when the stakes are higher than a practice app.&lt;/p&gt;

&lt;h2&gt;
  
  
  The next useful step
&lt;/h2&gt;

&lt;p&gt;Before you connect a custom domain, fill in one change note and ask AI to challenge its assumptions. Can it identify the exact hostname, supported destination, protected services, expected traffic path, and three independent checks?&lt;/p&gt;

&lt;p&gt;That is a better starting point than "fix my DNS." A clearer editor makes a change easier to enter. A clear change note makes it easier to understand and verify.&lt;/p&gt;

&lt;p&gt;The &lt;a href="https://marcusykim.gumroad.com/l/ai-app-builder-starter-prompts" rel="noopener noreferrer"&gt;$3 Starter Prompts&lt;/a&gt; help turn a rough app idea into bounded tasks. The &lt;a href="https://marcusykim.gumroad.com/l/ai-app-builder-book-only" rel="noopener noreferrer"&gt;$9 standalone e-book&lt;/a&gt; provides the organized path from idea through testing and publication; the &lt;a href="https://marcusykim.gumroad.com/l/ai-app-builder-from-zero" rel="noopener noreferrer"&gt;$10 learning bundle&lt;/a&gt; includes both resources.&lt;/p&gt;

&lt;p&gt;&lt;a href="https://marcusykim.com/review-radar/" rel="noopener noreferrer"&gt;Bootcamp Bundle (Review Radar)&lt;/a&gt; is coming soon, with a public preview and email waitlist; checkout remains closed.&lt;/p&gt;

&lt;p&gt;You can also find me here:&lt;/p&gt;

&lt;p&gt;Medium: &lt;a href="https://medium.com/@marcusykim" rel="noopener noreferrer"&gt;https://medium.com/@marcusykim&lt;/a&gt;&lt;br&gt;
DEV.to: &lt;a href="https://dev.to/marcusykim"&gt;https://dev.to/marcusykim&lt;/a&gt;&lt;br&gt;
Website: &lt;a href="https://marcusykim.com/" rel="noopener noreferrer"&gt;https://marcusykim.com/&lt;/a&gt;&lt;br&gt;
X: &lt;a href="https://x.com/marcusykim" rel="noopener noreferrer"&gt;https://x.com/marcusykim&lt;/a&gt;&lt;br&gt;
LinkedIn: &lt;a href="https://www.linkedin.com/in/marcusykim/" rel="noopener noreferrer"&gt;https://www.linkedin.com/in/marcusykim/&lt;/a&gt;&lt;br&gt;
Upwork: &lt;a href="https://www.upwork.com/freelancers/marcusykim" rel="noopener noreferrer"&gt;https://www.upwork.com/freelancers/marcusykim&lt;/a&gt;&lt;/p&gt;

</description>
      <category>webdev</category>
      <category>ai</category>
      <category>beginners</category>
      <category>programming</category>
    </item>
    <item>
      <title>GitHub's New Webhook IP Ranges: An Allowlist Is Not a Signature</title>
      <dc:creator>Marcus Kim</dc:creator>
      <pubDate>Sun, 01 Nov 2026 00:05:53 +0000</pubDate>
      <link>https://dev.to/marcusykim/githubs-new-webhook-ip-ranges-an-allowlist-is-not-a-signature-50i8</link>
      <guid>https://dev.to/marcusykim/githubs-new-webhook-ip-ranges-an-allowlist-is-not-a-signature-50i8</guid>
      <description>&lt;p&gt;Your app stops receiving GitHub events. An AI assistant spots a changed network range and suggests opening the webhook endpoint to more traffic. That may solve the connection problem. It does not answer whether your app should trust each message that arrives.&lt;/p&gt;

&lt;p&gt;This article was prepared with AI assistance. The examples below are proposed review exercises, not reports of a production system I tested.&lt;/p&gt;

&lt;p&gt;On October 29, GitHub &lt;a href="https://github.blog/changelog/2026-10-29-webhook-ip-ranges-added-to-the-meta-api/" rel="noopener noreferrer"&gt;announced additional webhook IP ranges&lt;/a&gt;. Teams maintaining static allowlists need to include the additions; systems already refreshing from the Meta API do not need a separate change for this update. The announcement applies to webhook deliveries on github.com, including Enterprise Cloud.&lt;/p&gt;

&lt;p&gt;The practical lesson for a first app is bigger than updating a list. Separate three questions: can this request reach the handler, is the body authentic, and is this event allowed to trigger the requested action?&lt;/p&gt;

&lt;h2&gt;
  
  
  Three checks, three different answers
&lt;/h2&gt;

&lt;p&gt;Imagine a small app that creates a preview task when a repository receives a pull request. This is a hypothetical design, not a description of an existing service.&lt;/p&gt;

&lt;p&gt;Its network filter decides which connections can reach the webhook route. Its signature check decides whether the received bytes match a message authenticated with the configured shared secret. Its application logic decides whether this repository, event, and action belong in the preview workflow.&lt;/p&gt;

&lt;p&gt;A pass at the first step should not silently count as a pass at the other two.&lt;/p&gt;

&lt;p&gt;For example, a correctly signed event from the wrong repository is still the wrong input for that project's preview workflow. And a delivery from an allowed network address with an invalid signature should not create a task merely because it got through the firewall.&lt;/p&gt;

&lt;p&gt;That separation is useful when reviewing AI-generated code: ask the assistant to point to the exact check that answers each question. My &lt;a href="https://marcusykim.gumroad.com/l/ai-app-builder-starter-prompts" rel="noopener noreferrer"&gt;$3 Starter Prompts&lt;/a&gt; offer a guided starting point for that kind of review, but you can use the exercise below without buying anything.&lt;/p&gt;

&lt;h2&gt;
  
  
  Fix the network layer without removing the next check
&lt;/h2&gt;

&lt;p&gt;GitHub's announcement lists three added CIDR ranges: &lt;code&gt;9.234.98.160/28&lt;/code&gt;, &lt;code&gt;9.234.98.176/28&lt;/code&gt;, and &lt;code&gt;9.234.106.48/28&lt;/code&gt;. Treat those as the dated announcement, not a permanent complete allowlist.&lt;/p&gt;

&lt;p&gt;The &lt;a href="https://docs.github.com/en/rest/meta/meta" rel="noopener noreferrer"&gt;Meta API documentation&lt;/a&gt; describes the endpoint used to retrieve GitHub's address information. For webhook filtering, use the current &lt;code&gt;hooks&lt;/code&gt; collection. A copied documentation example is not a promise that your firewall has today's complete list.&lt;/p&gt;

&lt;p&gt;For a practice project, I would ask for a short operational note with four facts: where the configured list lives, who updates it, when it was last refreshed, and how a rejected connection becomes visible. The note should not contain secrets or private payloads.&lt;/p&gt;

&lt;p&gt;If events disappear again, that gives you a specific first check. Did the request reach your application at all? If not, changing the signature validator will not repair the network path. Keep the layers separate while investigating.&lt;/p&gt;

&lt;h2&gt;
  
  
  Validate the bytes you actually received
&lt;/h2&gt;

&lt;p&gt;GitHub's &lt;a href="https://docs.github.com/en/webhooks/using-webhooks/validating-webhook-deliveries" rel="noopener noreferrer"&gt;signature-validation guide&lt;/a&gt; uses HMAC-SHA256 with a webhook secret and the &lt;code&gt;X-Hub-Signature-256&lt;/code&gt; header. Validation needs the original payload bytes, with a constant-time comparison rather than ordinary string equality. Its JavaScript example uses &lt;code&gt;@octokit/webhooks&lt;/code&gt;.&lt;/p&gt;

&lt;p&gt;This is where I would resist a convenient-looking shortcut. Parsing JSON and then serializing it again can change the representation. A semantically equivalent object is not necessarily the exact byte sequence that was signed. Review middleware ordering so the verifier gets the original body before transformations.&lt;/p&gt;

&lt;p&gt;Prefer a maintained validation library and the framework's documented raw-body handling over an improvised cryptography helper. Then test the integration around that library. A correct dependency cannot compensate for passing it the wrong body or selecting the wrong secret.&lt;/p&gt;

&lt;p&gt;Never put the secret in a screenshot, article comment, log message, or URL while debugging. You need evidence that verification succeeded or failed, not a copy of the credential that makes it work.&lt;/p&gt;

&lt;h2&gt;
  
  
  Write the rejection cases before the happy path
&lt;/h2&gt;

&lt;p&gt;Here is the review exercise I would give an AI assistant for the hypothetical preview app:&lt;/p&gt;

&lt;ol&gt;
&lt;li&gt;A valid test delivery from the intended repository creates exactly one preview task.&lt;/li&gt;
&lt;li&gt;A request with no signature creates no task.&lt;/li&gt;
&lt;li&gt;A request whose body changes after signing creates no task.&lt;/li&gt;
&lt;li&gt;A correctly signed event for a different repository creates no task for this project.&lt;/li&gt;
&lt;li&gt;An event with an unsupported action is ignored without starting preview work.&lt;/li&gt;
&lt;li&gt;Reprocessing the same accepted delivery does not create a second task.&lt;/li&gt;
&lt;/ol&gt;

&lt;p&gt;These are proposed acceptance criteria. A generated test file is not evidence that they passed. Run the tests and inspect both the result and the side effect, including the absence of a task in rejection cases.&lt;/p&gt;

&lt;p&gt;For the final case, two simultaneous workers are more revealing than two sequential requests. Ask what prevents both workers from deciding that the same delivery is new. The answer should identify the durable uniqueness check or transaction, not only a comment saying duplicates are handled.&lt;/p&gt;

&lt;h2&gt;
  
  
  A successful response needs a precise meaning
&lt;/h2&gt;

&lt;p&gt;GitHub's &lt;a href="https://docs.github.com/en/webhooks/using-webhooks/best-practices-for-using-webhooks" rel="noopener noreferrer"&gt;webhook best practices&lt;/a&gt; recommend checking event type and action, responding within ten seconds, and considering asynchronous processing. They also explain that a requested redelivery keeps the original &lt;code&gt;X-GitHub-Delivery&lt;/code&gt; value.&lt;/p&gt;

&lt;p&gt;For the example app, I would make an acknowledgment mean the accepted work was durably recorded, not that every downstream step finished. Otherwise a fast success response could hide lost work, or a slow build could make delivery appear to fail even though processing started.&lt;/p&gt;

&lt;p&gt;That is a design decision to test, not a reason to build a large queueing system for every toy project. Keep the implementation small enough to explain. Document what is stored before acknowledgment and what happens if the worker stops afterward.&lt;/p&gt;

&lt;h2&gt;
  
  
  The next useful question
&lt;/h2&gt;

&lt;p&gt;Open one webhook handler and ask: which line admits the request, which verifies its contents, and which authorizes the side effect? If the answer is one vague statement that the request is trusted, the review is not finished.&lt;/p&gt;

&lt;p&gt;For a guided first build, the &lt;a href="https://marcusykim.gumroad.com/l/ai-app-builder-starter-prompts" rel="noopener noreferrer"&gt;$3 Starter Prompts&lt;/a&gt; help turn questions into concrete tasks. The &lt;a href="https://marcusykim.gumroad.com/l/ai-app-builder-book-only" rel="noopener noreferrer"&gt;$9 standalone e-book&lt;/a&gt; provides the organized path from idea through testing and publication; the &lt;a href="https://marcusykim.gumroad.com/l/ai-app-builder-from-zero" rel="noopener noreferrer"&gt;$10 learning bundle&lt;/a&gt; includes both resources.&lt;/p&gt;

&lt;p&gt;&lt;a href="https://marcusykim.com/review-radar/" rel="noopener noreferrer"&gt;Bootcamp Bundle (Review Radar)&lt;/a&gt; is coming soon, with a public preview and email waitlist; checkout remains closed.&lt;/p&gt;

&lt;p&gt;You can also find me here:&lt;/p&gt;

&lt;p&gt;Medium: &lt;a href="https://medium.com/@marcusykim" rel="noopener noreferrer"&gt;https://medium.com/@marcusykim&lt;/a&gt;&lt;br&gt;
DEV.to: &lt;a href="https://dev.to/marcusykim"&gt;https://dev.to/marcusykim&lt;/a&gt;&lt;br&gt;
Website: &lt;a href="https://marcusykim.com/" rel="noopener noreferrer"&gt;https://marcusykim.com/&lt;/a&gt;&lt;br&gt;
X: &lt;a href="https://x.com/marcusykim" rel="noopener noreferrer"&gt;https://x.com/marcusykim&lt;/a&gt;&lt;br&gt;
LinkedIn: &lt;a href="https://www.linkedin.com/in/marcusykim/" rel="noopener noreferrer"&gt;https://www.linkedin.com/in/marcusykim/&lt;/a&gt;&lt;br&gt;
Upwork: &lt;a href="https://www.upwork.com/freelancers/marcusykim" rel="noopener noreferrer"&gt;https://www.upwork.com/freelancers/marcusykim&lt;/a&gt;&lt;/p&gt;

</description>
      <category>webdev</category>
      <category>ai</category>
    </item>
    <item>
      <title>GitHub App Permissions: An Installation Is Not Access to Everything</title>
      <dc:creator>Marcus Kim</dc:creator>
      <pubDate>Mon, 26 Oct 2026 19:03:18 +0000</pubDate>
      <link>https://dev.to/marcusykim/github-app-permissions-an-installation-is-not-access-to-everything-8ib</link>
      <guid>https://dev.to/marcusykim/github-app-permissions-an-installation-is-not-access-to-everything-8ib</guid>
      <description>&lt;p&gt;An integration says it is connected. The demo works. Then the client asks it to read a second project, and it fails.&lt;/p&gt;

&lt;p&gt;The tempting fix is to grant more access until the error disappears. Before doing that, ask a smaller question: connected where, allowed to do what, and against which resource?&lt;/p&gt;

&lt;p&gt;On October 23, GitHub &lt;a href="https://github.blog/changelog/2026-10-23-enterprise-installations-for-github-apps-generally-available/" rel="noopener noreferrer"&gt;made enterprise installations for GitHub Apps generally available&lt;/a&gt;, with expanded support for administrative and governance automation. It is a useful update, but not a promise that one installation unlocks every project below it.&lt;/p&gt;

&lt;p&gt;The practical lesson for freelancers is broader than GitHub: a connection is not an acceptance test. You need a simple map of the access the work actually requires.&lt;/p&gt;

&lt;h2&gt;
  
  
  Three questions hidden inside one connected badge
&lt;/h2&gt;

&lt;p&gt;An installation answers where an app has been added. Permissions describe operations it may perform. Resource scope identifies the actual projects or data involved. Those are related decisions, not interchangeable ones.&lt;/p&gt;

&lt;p&gt;&lt;a href="https://docs.github.com/en/enterprise-cloud@latest/apps/using-github-apps/installing-a-github-app-on-your-enterprise" rel="noopener noreferrer"&gt;GitHub's enterprise installation guide&lt;/a&gt; makes a particularly clear distinction: an enterprise installation manages enterprise-level operations. It does not grant organization or repository access; those resources require separate organization installations. Enterprise installations also do not currently receive webhooks for enterprise-level activities.&lt;/p&gt;

&lt;p&gt;That means an administrator can complete a legitimate installation while a repository-based feature still needs a different setup. A success screen at one level does not prove access at another.&lt;/p&gt;

&lt;p&gt;If you are learning to frame these tasks for an AI coding tool, my &lt;a href="https://marcusykim.gumroad.com/l/ai-app-builder-starter-prompts" rel="noopener noreferrer"&gt;$3 AI App Builder Starter Prompts&lt;/a&gt; provide a guided starting point. For this task, give the assistant an access map before asking it to fix the integration.&lt;/p&gt;

&lt;p&gt;You do not need an enterprise plan to practice the reasoning. Use a disposable project and the tools you already have. The enterprise feature is the news hook, not a reason to buy anything.&lt;/p&gt;

&lt;h2&gt;
  
  
  Turn a client request into an access map
&lt;/h2&gt;

&lt;p&gt;Imagine a fictional client who wants a weekly release summary from one private repository. The tool should read merged work and prepare a draft. It should not modify code, publish a release or inspect the client's unrelated repositories.&lt;/p&gt;

&lt;p&gt;Before implementation, I would write five plain-language lines:&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Requested outcome:&lt;/strong&gt; prepare a draft weekly summary from the selected project.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Installation location:&lt;/strong&gt; the client's organization account, using its normal approval process.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Target resource:&lt;/strong&gt; the explicitly selected test repository first, then the approved production repository after review.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Allowed operations:&lt;/strong&gt; only the reads needed for the summary. Check each chosen API endpoint's actual requirements rather than guessing permission names.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Forbidden operations:&lt;/strong&gt; modifying repository contents, changing settings, publishing the draft and reading unrelated private repositories.&lt;/p&gt;

&lt;p&gt;This is a proposed work record, not a GitHub configuration format. The client's administrator still needs to review the real installation screen and approve the actual access.&lt;/p&gt;

&lt;p&gt;The map also exposes an ordinary scope question: where will the draft live? If it is saved in another service, that service has its own access and data-retention decisions. Do not silently turn a read-only GitHub task into permission to publish somewhere else.&lt;/p&gt;

&lt;h2&gt;
  
  
  Ask AI to explain the access, not broaden it
&lt;/h2&gt;

&lt;p&gt;A vague instruction such as "fix the permissions" gives a coding assistant too much room to reinterpret the job. I would use a more bounded request:&lt;/p&gt;

&lt;blockquote&gt;
&lt;p&gt;Inspect the integration code and identify each API operation used to produce the summary. For each operation, link the official documentation and state the required permission and installation scope. Compare those requirements with our approved access map. Do not request broader access or change account settings. Report mismatches and propose the smallest change for review.&lt;/p&gt;
&lt;/blockquote&gt;

&lt;p&gt;GitHub's &lt;a href="https://docs.github.com/en/apps/creating-github-apps/registering-a-github-app/choosing-permissions-for-a-github-app" rel="noopener noreferrer"&gt;permission-selection guide&lt;/a&gt; recommends minimum required permissions and explains that endpoint documentation specifies the needed access. It also notes that changing an app's requested permissions does not automatically update every installation: account owners must approve the new permissions, or their installation retains the old set.&lt;/p&gt;

&lt;p&gt;That last detail matters during client delivery. A developer may update the app configuration while the client is still running with previously approved access. Record both the requested configuration and what the client has actually approved. Neither a code change nor a saved settings page proves the client's workflow now works.&lt;/p&gt;

&lt;h2&gt;
  
  
  Test the boundary, not just the happy path
&lt;/h2&gt;

&lt;p&gt;For the fictional summary tool, a good demo includes a successful read from the selected test repository. A useful acceptance check also asks whether the tool stays inside its limits.&lt;/p&gt;

&lt;p&gt;Use only synthetic data and accounts or repositories you are authorized to test. Do not probe another person's private resources.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Allowed case:&lt;/strong&gt; the tool reads the approved sample project and produces a draft containing the expected sample changes. Compare its output with a small known input so a plausible-looking summary cannot hide missing work.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Excluded case:&lt;/strong&gt; a second private test repository, deliberately outside the approved selection, remains inaccessible to the same integration. The tool should explain the missing access rather than return an empty success or ask for every repository automatically.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Write case:&lt;/strong&gt; confirm that the credentials used by this read-only workflow cannot perform a harmless write in a disposable test project. Never test a forbidden operation against production just to see whether it succeeds.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Interrupted-access case:&lt;/strong&gt; have the authorized owner suspend or remove the disposable test installation through normal controls, then run the test again. The app should show that action is required, preserve the draft already produced and stop treating the connection as healthy. Restore only the access deliberately approved for the test.&lt;/p&gt;

&lt;p&gt;These are suggested acceptance checks, not claims that any particular product runs them for you. Keep the observed result, time and test environment with the delivery record. An unrun test stays unverified.&lt;/p&gt;

&lt;h2&gt;
  
  
  Make the narrow version easy to hand over
&lt;/h2&gt;

&lt;p&gt;There is a tradeoff. Restricting access can add setup work when the client adds a project. Broad access can make that expansion feel easier, but it also increases what the integration could affect.&lt;/p&gt;

&lt;p&gt;Do not bury that choice in an implementation shortcut. Explain it in the client's language: adding another project requires a fresh selection and approval; it is not a broken feature or an automatic entitlement.&lt;/p&gt;

&lt;p&gt;At handover, give the client the access map, the observed test results and the normal place to review or revoke the installation. Record who can approve a future expansion. Do not include passwords, tokens or private customer data in the handover document.&lt;/p&gt;

&lt;p&gt;The useful result is not a badge that says connected. It is a small, understandable agreement between the job, the resources and the operations the app is allowed to perform. When those three match, a failed request becomes a specific question instead of an invitation to grant everything.&lt;/p&gt;

&lt;h2&gt;
  
  
  A guided next step
&lt;/h2&gt;

&lt;p&gt;The &lt;a href="https://marcusykim.gumroad.com/l/ai-app-builder-starter-prompts" rel="noopener noreferrer"&gt;$3 Starter Prompts&lt;/a&gt; help frame your next task. The &lt;a href="https://marcusykim.gumroad.com/l/ai-app-builder-book-only" rel="noopener noreferrer"&gt;$9 AI App Builder From Zero e-book&lt;/a&gt; gives you an organized path from idea to publication. The &lt;a href="https://marcusykim.gumroad.com/l/ai-app-builder-from-zero" rel="noopener noreferrer"&gt;$10 learning bundle&lt;/a&gt; includes both complete resources.&lt;/p&gt;

&lt;p&gt;Bootcamp Bundle (Review Radar) is coming soon; checkout is closed. &lt;a href="https://marcusykim.com/bootcamp-bundle/" rel="noopener noreferrer"&gt;See the preview and manually request waitlist updates by email&lt;/a&gt;.&lt;/p&gt;

&lt;p&gt;You can also find me here:&lt;/p&gt;

&lt;p&gt;Medium: &lt;a href="https://medium.com/@marcusykim" rel="noopener noreferrer"&gt;https://medium.com/@marcusykim&lt;/a&gt;&lt;br&gt;
DEV.to: &lt;a href="https://dev.to/marcusykim"&gt;https://dev.to/marcusykim&lt;/a&gt;&lt;br&gt;
Website: &lt;a href="https://marcusykim.com/" rel="noopener noreferrer"&gt;https://marcusykim.com/&lt;/a&gt;&lt;br&gt;
X: &lt;a href="https://x.com/marcusykim" rel="noopener noreferrer"&gt;https://x.com/marcusykim&lt;/a&gt;&lt;br&gt;
LinkedIn: &lt;a href="https://www.linkedin.com/in/marcusykim/" rel="noopener noreferrer"&gt;https://www.linkedin.com/in/marcusykim/&lt;/a&gt;&lt;br&gt;
Upwork: &lt;a href="https://www.upwork.com/freelancers/marcusykim" rel="noopener noreferrer"&gt;https://www.upwork.com/freelancers/marcusykim&lt;/a&gt;&lt;/p&gt;

</description>
      <category>ai</category>
      <category>beginners</category>
      <category>programming</category>
      <category>productivity</category>
    </item>
    <item>
      <title>GitHub Copilot in Teams: A Chat-to-Code Handoff Template for Beginners</title>
      <dc:creator>Marcus Kim</dc:creator>
      <pubDate>Sun, 25 Oct 2026 02:08:42 +0000</pubDate>
      <link>https://dev.to/marcusykim/github-copilot-in-teams-a-chat-to-code-handoff-template-for-beginners-5d1i</link>
      <guid>https://dev.to/marcusykim/github-copilot-in-teams-a-chat-to-code-handoff-template-for-beginners-5d1i</guid>
      <description>&lt;p&gt;A bug report lands in a team chat. Three people suggest fixes. Someone corrects the original report. Then you ask an AI coding assistant to handle it.&lt;/p&gt;

&lt;p&gt;Which version of the conversation did you just delegate?&lt;/p&gt;

&lt;p&gt;On October 23, GitHub &lt;a href="https://github.blog/changelog/2026-10-23-turn-notifications-into-code-with-github-copilot-in-teams/" rel="noopener noreferrer"&gt;announced a consolidated GitHub app for Microsoft Teams&lt;/a&gt;, bringing notifications and Copilot into the same app. A notification can lead to an investigation and a pull request through a GitHub mention. The announcement still puts review, testing and merging with the team.&lt;/p&gt;

&lt;p&gt;That shorter handoff is useful. It also makes it easier to hand over a conversation before anyone has decided what it means.&lt;/p&gt;

&lt;p&gt;My recommendation is to insert a small decision snapshot between the chat and the coding task. It should say which facts are established, which proposal was accepted, what remains open, and what would invalidate the assignment.&lt;/p&gt;

&lt;h2&gt;
  
  
  A thread is a discussion, not a decision record
&lt;/h2&gt;

&lt;p&gt;Imagine a fictional appointment app. The first message says that reminders arrive an hour late. A teammate suggests changing the server's time zone. Another person later discovers that the affected appointments were created before a daylight-saving transition.&lt;/p&gt;

&lt;p&gt;Those messages have different roles. The symptom is evidence. The server change is a proposal. The later observation changes the investigation. None of them automatically authorizes a production configuration change.&lt;/p&gt;

&lt;p&gt;If you want a guided starting point for framing app work, my &lt;a href="https://marcusykim.gumroad.com/l/ai-app-builder-starter-prompts" rel="noopener noreferrer"&gt;$3 AI App Builder Starter Prompts&lt;/a&gt; help turn an idea into a concrete next task. For this handoff, start by labeling the messages rather than copying the whole thread and hoping the assistant infers your decision.&lt;/p&gt;

&lt;p&gt;This is especially important when several people can steer an asynchronous task. The latest message might be a question, a joke, or a suggestion from someone who does not own the release decision. Recency and authority are different things.&lt;/p&gt;

&lt;h2&gt;
  
  
  The four-part handoff I would use
&lt;/h2&gt;

&lt;p&gt;You do not need a long specification. Put these four sections in an issue or another durable task record, then link that record from the conversation.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;1. Evidence.&lt;/strong&gt; Record the observed problem, reproduction steps and relevant examples. Label guesses as guesses. For our appointment app, capture an affected appointment's time-zone setting and expected reminder time using synthetic test data, not a customer's private details.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;2. Accepted decision.&lt;/strong&gt; State the action a named task owner has actually chosen. For example: investigate how existing appointments store their time-zone information, reproduce the discrepancy, and propose the smallest fix. Explicitly mark the suggested server-wide time-zone change as unapproved.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;3. Open questions.&lt;/strong&gt; List anything the assistant must not silently decide. Should previously created appointments retain their original local time? Who can approve changing that behavior? An unanswered product question should remain visible, not become an implementation default.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;4. Revision and stop rule.&lt;/strong&gt; Give the snapshot a revision label and explain which later event invalidates it. If the owner changes the intended reminder behavior, pause implementation and update the task before continuing. A new comment does not silently rewrite an already running assignment.&lt;/p&gt;

&lt;p&gt;The important distinction is between adding more context and changing the decision. Additional reproduction details may support the same task. A different intended behavior creates a new revision.&lt;/p&gt;

&lt;h2&gt;
  
  
  A copyable example
&lt;/h2&gt;

&lt;p&gt;Here is the compact version I would adapt for that fictional app:&lt;/p&gt;

&lt;blockquote&gt;
&lt;p&gt;Task revision: R1. Owner: the person responsible for reminder behavior.&lt;/p&gt;

&lt;p&gt;Evidence: appointments created before the daylight-saving transition reproduce an hour-late reminder. Use the attached synthetic case; other appointments have not yet been checked.&lt;/p&gt;

&lt;p&gt;Accepted decision: investigate stored time-zone information, reproduce the mismatch and prepare a focused patch with tests. Do not change the server's time zone or rewrite existing appointment data.&lt;/p&gt;

&lt;p&gt;Open question: should an existing appointment preserve its original local time after a time-zone rule changes? Ask the owner before changing that behavior.&lt;/p&gt;

&lt;p&gt;Revision rule: work against R1. If the owner changes the expected behavior, stop and request an updated task revision. Return the reproduction, changed files, test results and unresolved questions for review.&lt;/p&gt;
&lt;/blockquote&gt;

&lt;p&gt;This is my suggested working template, not a built-in GitHub command or a claim that the product enforces these rules automatically.&lt;/p&gt;

&lt;h2&gt;
  
  
  Check what the integration can actually do
&lt;/h2&gt;

&lt;p&gt;&lt;a href="https://docs.github.com/en/integrations/how-tos/teams/use-github-in-teams" rel="noopener noreferrer"&gt;GitHub's Teams usage guide&lt;/a&gt; describes teammates contributing context and steering agent work in a conversation. It also explains that issue and pull-request updates are threaded. That is helpful collaboration infrastructure, but a stream of updates is not a substitute for your accepted task revision.&lt;/p&gt;

&lt;p&gt;The same guide labels Copilot in Teams a public preview. The &lt;a href="https://docs.github.com/en/integrations/how-tos/teams/integrate-github-with-teams" rel="noopener noreferrer"&gt;setup guide&lt;/a&gt; lists Teams installation permissions, client-preview requirements and enabled Copilot cloud sandboxes among its prerequisites. Check the current requirements before assuming your account can use it. This article is not a recommendation to buy a plan or expand access just to try the template.&lt;/p&gt;

&lt;p&gt;You can use the handoff approach with an ordinary issue and your existing coding tool.&lt;/p&gt;

&lt;h2&gt;
  
  
  Test one correction before relying on the workflow
&lt;/h2&gt;

&lt;p&gt;In a disposable project, start a small task using R1. Then have the owner change one requirement and issue R2. Check what the assistant actually does: does it identify the conflict, explain work already completed, and wait for a reconciled instruction, or simply continue with stale assumptions?&lt;/p&gt;

&lt;p&gt;Do not assume the tool will notice a later chat message automatically. Establish how the revised task reaches the active session. If necessary, stop that session through its normal controls and begin the corrected work explicitly, preserving the earlier artifacts for comparison.&lt;/p&gt;

&lt;p&gt;There is a cost here: maintaining a snapshot takes a little effort, and stopping work can interrupt momentum. Use a short version for small tasks. Spend more attention when multiple people, repositories or consequential decisions are involved.&lt;/p&gt;

&lt;p&gt;The goal is not more paperwork. It is a handoff that another person can inspect without reconstructing twenty messages. Make the accepted decision easy to find, keep unresolved choices visible, and make a correction an explicit revision rather than another sentence lost in the thread.&lt;/p&gt;

&lt;h2&gt;
  
  
  A guided next step
&lt;/h2&gt;

&lt;p&gt;The &lt;a href="https://marcusykim.gumroad.com/l/ai-app-builder-starter-prompts" rel="noopener noreferrer"&gt;$3 Starter Prompts&lt;/a&gt; help frame your next app-building task. The &lt;a href="https://marcusykim.gumroad.com/l/ai-app-builder-book-only" rel="noopener noreferrer"&gt;$9 AI App Builder From Zero e-book&lt;/a&gt; gives you an organized path from idea to publication. The &lt;a href="https://marcusykim.gumroad.com/l/ai-app-builder-from-zero" rel="noopener noreferrer"&gt;$10 learning bundle&lt;/a&gt; includes both complete resources.&lt;/p&gt;

&lt;p&gt;Bootcamp Bundle (Review Radar) is coming soon; checkout is closed. &lt;a href="https://marcusykim.com/review-radar/" rel="noopener noreferrer"&gt;See the preview and manually request waitlist updates by email&lt;/a&gt;.&lt;/p&gt;

&lt;p&gt;You can also find me here:&lt;/p&gt;

&lt;p&gt;Medium: &lt;a href="https://medium.com/@marcusykim" rel="noopener noreferrer"&gt;https://medium.com/@marcusykim&lt;/a&gt;&lt;br&gt;
DEV.to: &lt;a href="https://dev.to/marcusykim"&gt;https://dev.to/marcusykim&lt;/a&gt;&lt;br&gt;
Website: &lt;a href="https://marcusykim.com/" rel="noopener noreferrer"&gt;https://marcusykim.com/&lt;/a&gt;&lt;br&gt;
X: &lt;a href="https://x.com/marcusykim" rel="noopener noreferrer"&gt;https://x.com/marcusykim&lt;/a&gt;&lt;br&gt;
LinkedIn: &lt;a href="https://www.linkedin.com/in/marcusykim/" rel="noopener noreferrer"&gt;https://www.linkedin.com/in/marcusykim/&lt;/a&gt;&lt;br&gt;
Upwork: &lt;a href="https://www.upwork.com/freelancers/marcusykim" rel="noopener noreferrer"&gt;https://www.upwork.com/freelancers/marcusykim&lt;/a&gt;&lt;/p&gt;

</description>
      <category>ai</category>
      <category>beginners</category>
      <category>webdev</category>
      <category>programming</category>
    </item>
    <item>
      <title>GitHub's New Whitespace Preferences: How to Review AI Code in Two Passes</title>
      <dc:creator>Marcus Kim</dc:creator>
      <pubDate>Fri, 23 Oct 2026 00:28:58 +0000</pubDate>
      <link>https://dev.to/marcusykim/githubs-new-whitespace-preferences-how-to-review-ai-code-in-two-passes-59kp</link>
      <guid>https://dev.to/marcusykim/githubs-new-whitespace-preferences-how-to-review-ai-code-in-two-passes-59kp</guid>
      <description>&lt;p&gt;A cleaner diff can help you understand a change. Before you merge, check what your review settings left out.&lt;/p&gt;

&lt;p&gt;You ask AI to fix one bug. It returns a change that also reformats half the file.&lt;/p&gt;

&lt;p&gt;Now you have two problems: understanding the fix and finding everything else that moved.&lt;/p&gt;

&lt;p&gt;On October 22, GitHub &lt;a href="https://github.blog/changelog/2026-10-22-pull-requests-saved-whitespace-preferences-and-improved-split-view/" rel="noopener noreferrer"&gt;announced saved whitespace preferences for pull-request reviews&lt;/a&gt;. You can keep whitespace visible, hide it across reviews, or hide it for one diff. The update also gives new and deleted files the full width in split view.&lt;/p&gt;

&lt;p&gt;That is a useful change for anyone reviewing AI-generated code. A noisy diff can bury a tiny behavioral edit. But a quieter view is still a view you selected.&lt;/p&gt;

&lt;p&gt;My practical lesson: use one pass to understand the change and a second pass to check its completeness. Your review settings belong in that process.&lt;/p&gt;

&lt;h2&gt;
  
  
  First, write down the intended change
&lt;/h2&gt;

&lt;p&gt;Before opening the diff, describe the behavior in one sentence.&lt;/p&gt;

&lt;p&gt;For a fictional appointment app, that might be: “Reject an end time that comes before the start time, and keep the user's entered values visible.”&lt;/p&gt;

&lt;p&gt;You now have something to compare against the patch. A rewritten navigation menu or a new analytics dependency needs an explanation, even if the assistant calls it cleanup.&lt;/p&gt;

&lt;p&gt;If you want help turning a feature request into a bounded task, my &lt;a href="https://marcusykim.gumroad.com/l/ai-app-builder-starter-prompts" rel="noopener noreferrer"&gt;$3 AI App Builder Starter Prompts&lt;/a&gt; give you a guided starting point. The immediate job here is small enough to practice on your next change: state the intended behavior before judging the implementation.&lt;/p&gt;

&lt;p&gt;I would also ask the assistant to separate formatting from behavior where practical. That makes review easier, but it does not prove that either change is safe.&lt;/p&gt;

&lt;h2&gt;
  
  
  Pass one: understand the behavior
&lt;/h2&gt;

&lt;p&gt;Open the changed files and look for the part that implements your sentence.&lt;/p&gt;

&lt;p&gt;If whitespace churn makes that difficult, hide whitespace temporarily. Read the conditions, the values being compared, and the error path. Ask yourself what happens when the user corrects the time and tries again.&lt;/p&gt;

&lt;p&gt;GitHub's new preference can save you from choosing the same setting repeatedly. Its active filter also gives you a way to restore whitespace for the current review without replacing your saved preference. The announcement says displayed file counts and diff statistics follow the filtered view.&lt;/p&gt;

&lt;p&gt;That last detail is why I would avoid using the visible change count as a completeness check while a filter is active.&lt;/p&gt;

&lt;p&gt;Write a short behavior note instead: “The validation runs before saving; invalid input keeps the form open; correcting the input allows a save.” If you cannot explain the path, ask for clarification before approving it.&lt;/p&gt;

&lt;h2&gt;
  
  
  Pass two: restore the missing context
&lt;/h2&gt;

&lt;p&gt;Show whitespace again. Clear any file filters you used, and inspect the complete set of changed files, including additions and deletions.&lt;/p&gt;

&lt;p&gt;This is where you look for changes that were easy to overlook during the focused pass: a configuration edit, a deleted test, an altered text template, or an unrelated file that was reformatted.&lt;/p&gt;

&lt;p&gt;Whitespace is not universally cosmetic. &lt;a href="https://docs.python.org/3/reference/lexical_analysis.html#indentation" rel="noopener noreferrer"&gt;Python's language reference&lt;/a&gt; explains that leading whitespace determines statement grouping. Moving an operation outside a conditional can change when it runs while leaving the operation's words intact.&lt;/p&gt;

&lt;p&gt;For the appointment example, imagine a save operation that should run only after validation succeeds. An indentation change could move it outside that condition. Inspect the complete function, then test an invalid appointment and confirm that nothing was saved.&lt;/p&gt;

&lt;p&gt;I am not claiming that GitHub's filter necessarily conceals that exact example. The broader engineering point is that a whitespace option does not understand every consequence of your program. You still need to reason about the resulting file.&lt;/p&gt;

&lt;h2&gt;
  
  
  Keep review coverage separate from proof
&lt;/h2&gt;

&lt;p&gt;&lt;a href="https://docs.github.com/en/pull-requests/how-tos/review-pull-requests/reviewing-proposed-changes-in-a-pull-request" rel="noopener noreferrer"&gt;GitHub's review guide&lt;/a&gt; recommends examining files individually and supports marking them as viewed. I would use that progress tracking after the relevant inspection, rather than treating a collapsed file as evidence that its behavior works.&lt;/p&gt;

&lt;p&gt;For our fictional fix, a useful review record would name three things:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Intent: invalid time ranges cannot be saved.&lt;/li&gt;
&lt;li&gt;Coverage: the complete diff was inspected with whitespace visible after the focused pass.&lt;/li&gt;
&lt;li&gt;Behavior: invalid input failed safely, corrected input saved, and the saved record contained the expected times.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;Those statements answer different questions. Reading the patch helps explain it. Running the app checks a path through it. Neither guarantees that every possible failure has been found.&lt;/p&gt;

&lt;h2&gt;
  
  
  When two passes cost too much
&lt;/h2&gt;

&lt;p&gt;A second pass adds attention and time. That tradeoff matters when the patch is large.&lt;/p&gt;

&lt;p&gt;My response would be to shrink the change before asking a beginner to review it. Request a separate formatting change, a narrower bug fix, or an explanation for unrelated edits. Splitting work has its own coordination cost, so use judgment for tiny changes that are already easy to inspect.&lt;/p&gt;

&lt;p&gt;The rule I want to keep is simple: a convenient review view should not silently become the boundary of what you checked.&lt;/p&gt;

&lt;p&gt;On your next AI-generated patch, write the intended behavior, use a focused view to understand the edit, restore the full diff, and run one concrete failure path. Record anything you could not verify before deciding whether to merge.&lt;/p&gt;

&lt;h2&gt;
  
  
  A guided next step
&lt;/h2&gt;

&lt;p&gt;The &lt;a href="https://marcusykim.gumroad.com/l/ai-app-builder-starter-prompts" rel="noopener noreferrer"&gt;$3 Starter Prompts&lt;/a&gt; help you frame the next task. The &lt;a href="https://marcusykim.gumroad.com/l/ai-app-builder-book-only" rel="noopener noreferrer"&gt;$9 AI App Builder From Zero e-book&lt;/a&gt; provides an organized path from an app idea to publication. The &lt;a href="https://marcusykim.gumroad.com/l/ai-app-builder-from-zero" rel="noopener noreferrer"&gt;$10 learning bundle&lt;/a&gt; includes both complete resources.&lt;/p&gt;

&lt;p&gt;Bootcamp Bundle (Review Radar) is coming soon; checkout is closed. &lt;a href="https://marcusykim.com/review-radar/" rel="noopener noreferrer"&gt;See the preview and manually request waitlist updates by email&lt;/a&gt;.&lt;/p&gt;

&lt;p&gt;You can also find me here:&lt;/p&gt;

&lt;p&gt;Medium: &lt;a href="https://medium.com/@marcusykim" rel="noopener noreferrer"&gt;https://medium.com/@marcusykim&lt;/a&gt;&lt;br&gt;
DEV.to: &lt;a href="https://dev.to/marcusykim"&gt;https://dev.to/marcusykim&lt;/a&gt;&lt;br&gt;
Website: &lt;a href="https://marcusykim.com/" rel="noopener noreferrer"&gt;https://marcusykim.com/&lt;/a&gt;&lt;br&gt;
X: &lt;a href="https://x.com/marcusykim" rel="noopener noreferrer"&gt;https://x.com/marcusykim&lt;/a&gt;&lt;br&gt;
LinkedIn: &lt;a href="https://www.linkedin.com/in/marcusykim/" rel="noopener noreferrer"&gt;https://www.linkedin.com/in/marcusykim/&lt;/a&gt;&lt;br&gt;
Upwork: &lt;a href="https://www.upwork.com/freelancers/marcusykim" rel="noopener noreferrer"&gt;https://www.upwork.com/freelancers/marcusykim&lt;/a&gt;&lt;/p&gt;

</description>
      <category>ai</category>
      <category>programming</category>
      <category>beginners</category>
      <category>webdev</category>
    </item>
    <item>
      <title>GitHub's New Clone Authentication Rule: How to Stop Debugging the Wrong Problem</title>
      <dc:creator>Marcus Kim</dc:creator>
      <pubDate>Tue, 20 Oct 2026 02:16:30 +0000</pubDate>
      <link>https://dev.to/marcusykim/githubs-new-clone-authentication-rule-how-to-stop-debugging-the-wrong-problem-252o</link>
      <guid>https://dev.to/marcusykim/githubs-new-clone-authentication-rule-how-to-stop-debugging-the-wrong-problem-252o</guid>
      <description>&lt;p&gt;You open a tutorial, ask AI to set up the project, and watch the terminal fail before the app even starts.&lt;/p&gt;

&lt;p&gt;The expensive part can come next: two hours of changing files that had nothing to do with the failure.&lt;/p&gt;

&lt;p&gt;On October 19, GitHub &lt;a href="https://github.blog/changelog/2026-10-19-some-git-over-https-may-temporarily-require-authentication/" rel="noopener noreferrer"&gt;announced temporary authentication requirements for some public repository clones and fetches over HTTPS&lt;/a&gt;. The protection applies during unusual traffic and can occasionally affect legitimate unauthenticated operations. It is not a blanket change making public repositories private.&lt;/p&gt;

&lt;p&gt;That distinction matters when you build with AI. A setup command can fail because of the service it contacts, even when the project you want to run is perfectly fine.&lt;/p&gt;

&lt;p&gt;My practical takeaway: before you authorize a fix, decide whether you have acquired the code, prepared its environment, or actually reached the application.&lt;/p&gt;

&lt;h2&gt;
  
  
  Give the failure an address
&lt;/h2&gt;

&lt;p&gt;Imagine a fictional booking-app tutorial. Your assistant plans to download the starter repository, install its packages, start a local server, and test the booking form.&lt;/p&gt;

&lt;p&gt;Those are four different jobs. If downloading the repository fails, there is no evidence yet about whether its package versions work or its booking form is broken.&lt;/p&gt;

&lt;p&gt;I would ask the assistant to report three things before editing anything:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;The last step that completed.&lt;/li&gt;
&lt;li&gt;The first step that failed, with a sanitized error message.&lt;/li&gt;
&lt;li&gt;The next step that never ran.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;For this example, the answer might be: destination folder created; HTTPS clone requires authentication; package installation never started.&lt;/p&gt;

&lt;p&gt;Now you have a useful problem statement. You do not need a new framework, a different database, or a rewritten booking form. You need a decision about repository access.&lt;/p&gt;

&lt;p&gt;If you need help turning a vague app idea into small, inspectable tasks, my &lt;a href="https://marcusykim.gumroad.com/l/ai-app-builder-starter-prompts" rel="noopener noreferrer"&gt;$3 AI App Builder Starter Prompts&lt;/a&gt; provide a guided starting point. Add a simple boundary to the task: explain a failed prerequisite before proposing application changes.&lt;/p&gt;

&lt;h2&gt;
  
  
  Read the provider's scope before changing yours
&lt;/h2&gt;

&lt;p&gt;GitHub's announcement identifies an access protection, rather than a change to your application's behavior. Its scope is specific: some unauthenticated HTTPS clone and fetch operations. Authenticated HTTPS operations, SSH operations, pushes, and unrelated web or API traffic are described as unaffected.&lt;/p&gt;

&lt;p&gt;GitHub recommends supported authentication for automated access, or waiting until the temporary protection lifts when authentication is unavailable. The post does not supply a universal waiting period.&lt;/p&gt;

&lt;p&gt;That is enough to avoid several bad guesses. A repository loading in your browser does not establish that your terminal command has the right authentication. A failed clone does not prove a dependency is incompatible. Repeatedly rerunning the entire build does not investigate either question.&lt;/p&gt;

&lt;p&gt;The durable habit is to identify the affected operation precisely. “GitHub is down” and “this project is broken” are much broader claims than the evidence supports.&lt;/p&gt;

&lt;h2&gt;
  
  
  Keep access work separate from feature work
&lt;/h2&gt;

&lt;p&gt;&lt;a href="https://docs.github.com/en/authentication/keeping-your-account-and-data-secure/about-authentication-to-github" rel="noopener noreferrer"&gt;GitHub's authentication documentation&lt;/a&gt; explains that the access method determines the authentication path. Browser sign-in and command-line Git are different contexts; HTTPS and SSH also use different mechanisms.&lt;/p&gt;

&lt;p&gt;I would use the supported sign-in or credential-helper flow appropriate to the environment. I would not paste a credential into an AI conversation, commit one into the repository, or place one inside a remote URL that could appear in logs.&lt;/p&gt;

&lt;p&gt;Before asking someone to change a remote, confirm what it is supposed to point to. &lt;a href="https://docs.github.com/en/get-started/git-basics/managing-remote-repositories" rel="noopener noreferrer"&gt;GitHub's remote-management guide&lt;/a&gt; documents how remote names and URLs work. A transport change is a deliberate configuration decision, not a magic debugging incantation.&lt;/p&gt;

&lt;p&gt;For a client project, the owner of access might be the client or their administrator. Your feature-development task should not silently become permission to expand account access.&lt;/p&gt;

&lt;h2&gt;
  
  
  Put a time budget on the detour
&lt;/h2&gt;

&lt;p&gt;Here is the productivity rule I would use for a beginner build: spend ten minutes classifying a prerequisite failure before choosing whether to resolve it, hand it off, or work around it with an already approved task.&lt;/p&gt;

&lt;p&gt;Ten minutes is my suggested working limit, not a GitHub retry interval.&lt;/p&gt;

&lt;p&gt;During that window, preserve the exact failed operation, compare its message with current documentation, and identify who can resolve it. Avoid changing several unrelated settings to see what sticks.&lt;/p&gt;

&lt;p&gt;At the end, write a short handoff:&lt;/p&gt;

&lt;blockquote&gt;
&lt;p&gt;Starter code has not downloaded. The HTTPS clone reports an authentication requirement. No application files were changed. Access needs the project owner's supported sign-in path; the next build step is package installation after acquisition succeeds.&lt;/p&gt;
&lt;/blockquote&gt;

&lt;p&gt;That note lets you pause without losing the plot. You can continue drafting the booking flow, clarifying acceptance criteria, or reviewing an existing local copy if those tasks are useful and authorized. You do not have to produce a code diff to prove you worked.&lt;/p&gt;

&lt;h2&gt;
  
  
  Verify the boundary you just crossed
&lt;/h2&gt;

&lt;p&gt;Suppose the access step succeeds later. Resume at acquisition, confirm you have the intended repository, then continue setup.&lt;/p&gt;

&lt;p&gt;Do not report “the app is fixed.” You have proved that its source can now be obtained. Package installation, startup, and the booking journey still need their own evidence.&lt;/p&gt;

&lt;p&gt;There is a tradeoff here. This approach can feel slower than letting an assistant try five speculative fixes. It also requires you to stop and read a dull error message.&lt;/p&gt;

&lt;p&gt;But speculative changes create a second problem: now you must distinguish the original failure from the consequences of your attempted repair. A short triage pause can save a long cleanup session.&lt;/p&gt;

&lt;p&gt;Your next action is small. Take one recent failed build and label the last completed step, first failed step, and first unattempted step. Then check whether your proposed fix operates at that same boundary.&lt;/p&gt;

&lt;p&gt;Protect your working time by giving the problem an address before giving AI permission to renovate the house.&lt;/p&gt;

&lt;h2&gt;
  
  
  A guided next step
&lt;/h2&gt;

&lt;p&gt;The &lt;a href="https://marcusykim.gumroad.com/l/ai-app-builder-starter-prompts" rel="noopener noreferrer"&gt;$3 Starter Prompts&lt;/a&gt; help you turn an idea into guided building tasks. The &lt;a href="https://marcusykim.gumroad.com/l/ai-app-builder-book-only" rel="noopener noreferrer"&gt;$9 AI App Builder From Zero e-book&lt;/a&gt; organizes the path from idea through testing and publication. The &lt;a href="https://marcusykim.gumroad.com/l/ai-app-builder-from-zero" rel="noopener noreferrer"&gt;$10 learning bundle&lt;/a&gt; includes both complete resources.&lt;/p&gt;

&lt;p&gt;Bootcamp Bundle (Review Radar) is &lt;a href="https://marcusykim.com/review-radar/" rel="noopener noreferrer"&gt;coming soon; preview it and request waitlist updates manually by email&lt;/a&gt;. Checkout is closed.&lt;/p&gt;

&lt;p&gt;You can also find me here:&lt;/p&gt;

&lt;p&gt;Medium: &lt;a href="https://medium.com/@marcusykim" rel="noopener noreferrer"&gt;https://medium.com/@marcusykim&lt;/a&gt;&lt;br&gt;
DEV.to: &lt;a href="https://dev.to/marcusykim"&gt;https://dev.to/marcusykim&lt;/a&gt;&lt;br&gt;
Website: &lt;a href="https://marcusykim.com/" rel="noopener noreferrer"&gt;https://marcusykim.com/&lt;/a&gt;&lt;br&gt;
X: &lt;a href="https://x.com/marcusykim" rel="noopener noreferrer"&gt;https://x.com/marcusykim&lt;/a&gt;&lt;br&gt;
LinkedIn: &lt;a href="https://www.linkedin.com/in/marcusykim/" rel="noopener noreferrer"&gt;https://www.linkedin.com/in/marcusykim/&lt;/a&gt;&lt;br&gt;
Upwork: &lt;a href="https://www.upwork.com/freelancers/marcusykim" rel="noopener noreferrer"&gt;https://www.upwork.com/freelancers/marcusykim&lt;/a&gt;&lt;/p&gt;

</description>
      <category>ai</category>
      <category>beginners</category>
      <category>webdev</category>
      <category>programming</category>
    </item>
    <item>
      <title>Cloudflare's Bot Trust Update: Five Tests for an AI-Built Crawler in 2026</title>
      <dc:creator>Marcus Kim</dc:creator>
      <pubDate>Sat, 17 Oct 2026 19:41:48 +0000</pubDate>
      <link>https://dev.to/marcusykim/cloudflares-bot-trust-update-five-tests-for-an-ai-built-crawler-in-2026-4mpl</link>
      <guid>https://dev.to/marcusykim/cloudflares-bot-trust-update-five-tests-for-an-ai-built-crawler-in-2026-4mpl</guid>
      <description>&lt;p&gt;An automation can introduce itself correctly, stay logged in, and still be the worst visitor on a website.&lt;/p&gt;

&lt;p&gt;On October 16, Cloudflare &lt;a href="https://blog.cloudflare.com/verified-bots-accountability/" rel="noopener noreferrer"&gt;described a new system for continuously evaluating Verified bots&lt;/a&gt;. Its initial signals include whether traffic follows published robots preferences and adapts after a site returns HTTP 429. The company says it is using the system internally first; public scores and customer-selectable trust thresholds are planned, not something every customer can configure today.&lt;/p&gt;

&lt;p&gt;The useful beginner lesson is smaller than the infrastructure announcement: knowing who your software is does not prove it listens.&lt;/p&gt;

&lt;p&gt;If you ask AI to build a crawler, research assistant, or scheduled importer, do not stop testing after it downloads the first page. Test the moment the destination changes its answer.&lt;/p&gt;

&lt;p&gt;I would give that behavior its own checklist before expanding the queue.&lt;/p&gt;

&lt;h2&gt;
  
  
  Start with a tiny, fictional job
&lt;/h2&gt;

&lt;p&gt;Imagine a demo app that imports ten documentation pages from a site you are allowed to access.&lt;/p&gt;

&lt;p&gt;The app has two workers. Each worker takes a queued page, downloads it, and records a result. You can pause and restart the process.&lt;/p&gt;

&lt;p&gt;That is enough machinery to expose an important problem. Worker one can receive a slowdown signal while worker two keeps sending requests. A restart can forget a pause. A stale queue can contain pages that are no longer eligible.&lt;/p&gt;

&lt;p&gt;You do not need to test those mistakes against somebody else's production website. Use a local test server or a controlled fixture with synthetic pages and a request log.&lt;/p&gt;

&lt;p&gt;If turning the idea into a bounded first project is the hard part, my &lt;a href="https://marcusykim.gumroad.com/l/ai-app-builder-starter-prompts" rel="noopener noreferrer"&gt;$3 AI App Builder Starter Prompts&lt;/a&gt; are a guided starting point. For this exercise, keep the project to one queue and five observable tests.&lt;/p&gt;

&lt;h2&gt;
  
  
  Test 1: A disallowed path never reaches the downloader
&lt;/h2&gt;

&lt;p&gt;Create one allowed demo path and one path excluded by the fixture's robots rules. Put both in the queue.&lt;/p&gt;

&lt;p&gt;The result you want is not an error after downloading the excluded page. It is no content request to that path, plus a visible reason for skipping it.&lt;/p&gt;

&lt;p&gt;&lt;a href="https://www.rfc-editor.org/rfc/rfc9309" rel="noopener noreferrer"&gt;RFC 9309&lt;/a&gt; defines the Robots Exclusion Protocol and explicitly separates it from access authorization. A robots file is not a login system or a universal permission slip. Your app still needs an appropriate basis for accessing the destination and must respect its other controls.&lt;/p&gt;

&lt;p&gt;Ask AI to use an established parser for the protocol rather than inventing a few string checks. Then inspect the fixture's actual request log.&lt;/p&gt;

&lt;p&gt;My acceptance line would be: "The excluded content URL received zero requests, and the queue explains why."&lt;/p&gt;

&lt;h2&gt;
  
  
  Test 2: One slowdown reaches both workers
&lt;/h2&gt;

&lt;p&gt;Make the fixture return HTTP 429 with a short wait instruction on the first content request.&lt;/p&gt;

&lt;p&gt;&lt;a href="https://www.rfc-editor.org/rfc/rfc6585" rel="noopener noreferrer"&gt;RFC 6585&lt;/a&gt; defines 429 as rate limiting and permits a Retry-After header. The protocol does not give your app a universal quota; providers can count requests in different ways.&lt;/p&gt;

&lt;p&gt;For this small demo, I would choose a conservative destination-wide pause. Both workers consult the same next-eligible time before starting another request. That is a design choice for the example, not a claim that every API uses a whole-site limit.&lt;/p&gt;

&lt;p&gt;Now check the log during the pause. A message saying "worker one is waiting" is insufficient if worker two is still busy hitting the same destination.&lt;/p&gt;

&lt;p&gt;Also account for requests that were already in flight. Record when each request started so you can distinguish those from newly dispatched work after the pause became known.&lt;/p&gt;

&lt;h2&gt;
  
  
  Test 3: Restarting does not erase the pause
&lt;/h2&gt;

&lt;p&gt;Stop the demo during its waiting period. Start it again before that period ends.&lt;/p&gt;

&lt;p&gt;The queue should retain the destination's next-eligible time. If the app immediately starts over, the pause existed only in one process's memory.&lt;/p&gt;

&lt;p&gt;This is where I would ask AI to show the stored state, not just the function containing a sleep call.&lt;/p&gt;

&lt;p&gt;A useful test record includes the destination, the feedback received, the resulting pause, and the next request start time. Keep credentials and response bodies out of that record unless they are actually necessary and safe to retain.&lt;/p&gt;

&lt;h2&gt;
  
  
  Test 4: Changed preferences affect queued work
&lt;/h2&gt;

&lt;p&gt;Leave several demo pages waiting, then change the fixture's policy before the next batch begins.&lt;/p&gt;

&lt;p&gt;Define when your app refreshes that policy and how queued work is checked against the refreshed result. Use the protocol's caching rules and the destination's documented requirements; do not assume one lookup at installation lasts forever.&lt;/p&gt;

&lt;p&gt;The important product decision is what happens to old work. I would preserve an excluded item as skipped with its reason, rather than silently deleting it or trying an alternate identity.&lt;/p&gt;

&lt;p&gt;Do not route around a refusal with a different account, address, or browser. A technically successful download is not a successful test if it evades the boundary you were meant to honor.&lt;/p&gt;

&lt;h2&gt;
  
  
  Test 5: The user sees incomplete work honestly
&lt;/h2&gt;

&lt;p&gt;Pause the demo after four of ten pages finish.&lt;/p&gt;

&lt;p&gt;The interface should not say "Research complete" because the process exited normally. Show four completed pages, the remaining items, the destination pause, and whether any result is stale or unavailable.&lt;/p&gt;

&lt;p&gt;This is also where you decide whether partial output is useful. A documentation search may show the pages it has, with clear coverage. A comparison that requires all ten sources may need to remain incomplete.&lt;/p&gt;

&lt;p&gt;Neither decision should be hidden inside the downloader.&lt;/p&gt;

&lt;h2&gt;
  
  
  A prompt that asks for behavior, not reassurance
&lt;/h2&gt;

&lt;p&gt;I would give AI a prompt like this:&lt;/p&gt;

&lt;blockquote&gt;
&lt;p&gt;Build a local-only test harness for our documentation importer. Use synthetic pages and no external requests. Add fixtures for an excluded path, HTTP 429 feedback, two workers sharing a destination pause, restart during the pause, and a policy change while work is queued. State each expected request sequence before implementing it. Record request start times and queue transitions. Prove which requests did not occur. Show incomplete coverage truthfully. Do not change identities or bypass controls to make a test pass.&lt;/p&gt;
&lt;/blockquote&gt;

&lt;p&gt;Notice what the prompt does not ask for: "Make the crawler robust."&lt;/p&gt;

&lt;p&gt;That adjective leaves too much room for interpretation. A request sequence, a persistent pause, and a visible unfinished queue give you something to inspect.&lt;/p&gt;

&lt;h2&gt;
  
  
  Keep the first implementation modest
&lt;/h2&gt;

&lt;p&gt;A destination-wide pause can be overly cautious for an API with separate documented limits. A multi-machine deployment needs stronger coordination than a tiny local demo. A fixture cannot prove that an outside service will behave exactly like your simulation.&lt;/p&gt;

&lt;p&gt;Those are reasons to state the limits of the test, not reasons to skip it.&lt;/p&gt;

&lt;p&gt;Start with one destination and one explicit policy. When you add workers or destinations, repeat the tests at that boundary.&lt;/p&gt;

&lt;p&gt;The &lt;a href="https://marcusykim.gumroad.com/l/ai-app-builder-starter-prompts" rel="noopener noreferrer"&gt;$3 Starter Prompts&lt;/a&gt; help you begin a bounded project. For the organized path through planning, implementation, QA, and publication, AI App Builder From Zero is available as a &lt;a href="https://marcusykim.gumroad.com/l/ai-app-builder-book-only" rel="noopener noreferrer"&gt;$9 standalone e-book&lt;/a&gt;. The separate 40-prompt workbook is not included. The &lt;a href="https://marcusykim.gumroad.com/l/ai-app-builder-from-zero" rel="noopener noreferrer"&gt;$10 learning bundle&lt;/a&gt; includes the complete book and all 40 Starter Prompts.&lt;/p&gt;

&lt;p&gt;Eligible purchases carry one future Bootcamp Bundle benefit: $20 with the $3 prompts, $30 with the standalone book, or $70 with the learning bundle. Verified Apple Books and Kindle combined editions qualify for $70; each store displays its own price. One verified benefit per buyer, used once on either package when checkout opens; benefits do not stack, have no cash value, and exclude refunded or disputed purchases. Previously issued benefits retain their original terms.&lt;/p&gt;

&lt;p&gt;&lt;a href="https://marcusykim.com/review-radar/" rel="noopener noreferrer"&gt;Bootcamp Bundle (Review Radar) is coming soon&lt;/a&gt;, planned at $399 for one app project or $999 for three. Its planned research, specifications, screen designs, and guided curriculum are not a finished app. You can request waitlist updates through the existing page; checkout remains closed.&lt;/p&gt;

&lt;p&gt;The final check is simple: when the destination changes its answer, can you show that every worker changed its behavior?&lt;/p&gt;

&lt;p&gt;You can also find me here:&lt;/p&gt;

&lt;p&gt;Medium: &lt;a href="https://medium.com/@marcusykim" rel="noopener noreferrer"&gt;https://medium.com/@marcusykim&lt;/a&gt;&lt;br&gt;
DEV.to: &lt;a href="https://dev.to/marcusykim"&gt;https://dev.to/marcusykim&lt;/a&gt;&lt;br&gt;
Website: &lt;a href="https://marcusykim.com/" rel="noopener noreferrer"&gt;https://marcusykim.com/&lt;/a&gt;&lt;br&gt;
X: &lt;a href="https://x.com/marcusykim" rel="noopener noreferrer"&gt;https://x.com/marcusykim&lt;/a&gt;&lt;br&gt;
LinkedIn: &lt;a href="https://www.linkedin.com/in/marcusykim/" rel="noopener noreferrer"&gt;https://www.linkedin.com/in/marcusykim/&lt;/a&gt;&lt;br&gt;
Upwork: &lt;a href="https://www.upwork.com/freelancers/marcusykim" rel="noopener noreferrer"&gt;https://www.upwork.com/freelancers/marcusykim&lt;/a&gt;&lt;/p&gt;

</description>
      <category>ai</category>
      <category>beginners</category>
      <category>webdev</category>
      <category>programming</category>
    </item>
    <item>
      <title>Salesforce's New Agentforce Portfolio: Should You Build or Configure Your First AI App?</title>
      <dc:creator>Marcus Kim</dc:creator>
      <pubDate>Sat, 17 Oct 2026 19:24:57 +0000</pubDate>
      <link>https://dev.to/marcusykim/salesforces-new-agentforce-portfolio-should-you-build-or-configure-your-first-ai-app-5dkp</link>
      <guid>https://dev.to/marcusykim/salesforces-new-agentforce-portfolio-should-you-build-or-configure-your-first-ai-app-5dkp</guid>
      <description>&lt;p&gt;On September 14, Salesforce &lt;a href="https://www.salesforce.com/ap/news/press-releases/2026/09/14/ph-salesforce-expands-agentforce-with-a-new-portfolio-of-ai-agents-built-for-high-value-work/" rel="noopener noreferrer"&gt;announced a new Agentforce portfolio&lt;/a&gt; organized around jobs such as customer service, employee support, shopping, and back-office work. Its pitch is that companies can start with agents that already have relevant skills, actions, and data models, then tailor them.&lt;/p&gt;

&lt;p&gt;There is an availability distinction worth keeping straight. Salesforce lists several agents as generally available, while its Hunter outbound-sales agent is in pilot with general availability planned for November. Hunter is also the first agent using the new runtime for work that extends across days and weeks. That does not make every announced capability available today.&lt;/p&gt;

&lt;p&gt;What caught my attention was the starting point: a job that existing software already knows something about.&lt;/p&gt;

&lt;p&gt;If you are a beginner with an app idea, this raises an uncomfortable question. Before you ask an AI coding tool to build your business software, have you made an existing tool attempt the actual job?&lt;/p&gt;

&lt;p&gt;I studied entrepreneurship before software engineering, and I build apps with AI. I like building things. That makes this question especially useful for me. A working prototype can make a decision feel settled before I have compared the alternatives.&lt;/p&gt;

&lt;p&gt;My rule is to earn the custom build with evidence: find one important task that your available tools cannot handle acceptably, then decide whether owning new software is the best way to close that gap.&lt;/p&gt;

&lt;p&gt;If describing that task is where you get stuck, my &lt;a href="https://marcusykim.gumroad.com/l/ai-app-builder-starter-prompts" rel="noopener noreferrer"&gt;$3 AI App Builder Starter Prompts&lt;/a&gt; give you a guided starting point for turning an idea into a first build. Use the exercise below before committing to that build.&lt;/p&gt;

&lt;h2&gt;
  
  
  Give the existing option a fair attempt
&lt;/h2&gt;

&lt;p&gt;Imagine a fictional freelance studio that wants an AI project-update app. The owner wants to turn project notes into a weekly status update.&lt;/p&gt;

&lt;p&gt;An attractive first prompt would be: “Build a dashboard with clients, projects, AI summaries, and email delivery.”&lt;/p&gt;

&lt;p&gt;I would start with a smaller investigation. Choose one representative project and write down the required result:&lt;/p&gt;

&lt;p&gt;“Produce an update that distinguishes completed work from planned work, includes the latest client decision, and leaves disputed items for my review.”&lt;/p&gt;

&lt;p&gt;Now attempt that job with the tools the studio already has. A document, an existing project tracker, and a manual review step may be enough to learn something useful. You do not need a new subscription to begin.&lt;/p&gt;

&lt;p&gt;Use three sample inputs: an ordinary week, a week with a changed decision, and a week with contradictory notes. Use fictional or appropriately sanitized material when evaluating a tool that should not receive client information.&lt;/p&gt;

&lt;p&gt;Judge the result against the written requirement. A feature list that says “AI summaries” cannot tell you whether the update silently treats a proposed deadline as an agreed one.&lt;/p&gt;

&lt;h2&gt;
  
  
  Write down the gap precisely
&lt;/h2&gt;

&lt;p&gt;Suppose the existing workflow produces a decent draft, but it cannot distinguish a client-approved decision from an internal suggestion.&lt;/p&gt;

&lt;p&gt;That is a useful finding. “I need a better AI dashboard” was a preference. “The update needs an approval state attached to each decision” describes a missing capability.&lt;/p&gt;

&lt;p&gt;I would classify each failure before creating a development task:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;A missing setting: the capability exists, and we have not configured it.&lt;/li&gt;
&lt;li&gt;Missing or unclear input: the tool cannot identify approval because our notes never record it.&lt;/li&gt;
&lt;li&gt;A missing connection: the information exists in another tool but does not reach this workflow.&lt;/li&gt;
&lt;li&gt;Missing product behavior: the available system cannot represent or enforce the rule we need.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;Those diagnoses lead to different amounts of work. A notes convention may solve the second problem. A supported export may solve the third. The fourth may justify a custom component.&lt;/p&gt;

&lt;p&gt;Ask the existing workflow to fail honestly before giving a new app credit for solving it.&lt;/p&gt;

&lt;h2&gt;
  
  
  Compare three paths on the same task
&lt;/h2&gt;

&lt;p&gt;For the fictional studio, I would consider three options.&lt;/p&gt;

&lt;p&gt;First, configure the current tools and keep a person reviewing the draft. This can be a good fit if updates are infrequent and the review is quick.&lt;/p&gt;

&lt;p&gt;Second, add a narrow extension that records decision status and prepares the update. Keep the established project tracker if it already handles the rest of the job well.&lt;/p&gt;

&lt;p&gt;Third, build a dedicated app because the approval behavior, recurring volume, or required user experience makes the smaller options inadequate.&lt;/p&gt;

&lt;p&gt;Give every option the same sample inputs and required result. Record where it fails, what a person still has to do, and what you would have to maintain. For an unbuilt option, label the result as a hypothesis until a small prototype demonstrates it.&lt;/p&gt;

&lt;p&gt;This comparison prevents an unfair contest between an existing tool's real limitations and an imaginary app that has none.&lt;/p&gt;

&lt;p&gt;It also keeps you from building an entire project-management system to obtain one approval field.&lt;/p&gt;

&lt;h2&gt;
  
  
  Count the work after the first demo
&lt;/h2&gt;

&lt;p&gt;In his &lt;a href="https://aws.amazon.com/blogs/enterprise-strategy/revisiting-buy-vs-build-3-traps-to-avoid/" rel="noopener noreferrer"&gt;2020 AWS essay on build-versus-buy decisions&lt;/a&gt;, Gregor Hohpe explains why development cost alone is an incomplete comparison. Time spent creating one system cannot also be spent elsewhere, and writing your own software creates commitments of its own.&lt;/p&gt;

&lt;p&gt;My beginner version is to name the recurring chores before celebrating the saved subscription.&lt;/p&gt;

&lt;p&gt;Who corrects the source data? Who notices that the update is wrong? Who handles a changed integration? Who helps a new user? Can you return to the manual workflow if the tool becomes unavailable?&lt;/p&gt;

&lt;p&gt;Packaged AI also requires this work. Salesforce's &lt;a href="https://help.salesforce.com/s/articleView?id=ai.agent_testing_center.htm&amp;amp;language=en_US&amp;amp;type=5" rel="noopener noreferrer"&gt;Testing Center documentation&lt;/a&gt; describes evaluating responses and actions across scenarios. It warns that tests consume requests and credits and can modify CRM data, so testing belongs in a sandbox.&lt;/p&gt;

&lt;p&gt;That is relevant even if you never use Salesforce: obtaining an agent does not complete the job of operating it. For a zero-budget evaluation, write your cases and examine the current workflow first; do not assume a vendor's test button is free.&lt;/p&gt;

&lt;p&gt;I would keep a short list of the chores each option leaves with me. If nobody can own them, the option is not ready to become part of the business.&lt;/p&gt;

&lt;h2&gt;
  
  
  Set a condition for changing your mind
&lt;/h2&gt;

&lt;p&gt;There is a limitation to starting with existing tools. You can spend too long adapting your work to a system that cannot express the thing customers value.&lt;/p&gt;

&lt;p&gt;The answer is to put a limit on the investigation. For this example, I might allow one afternoon to test the three sample inputs and the relevant configuration. If the approval rule still cannot be represented, I would prototype only that missing behavior.&lt;/p&gt;

&lt;p&gt;Those are example limits, not universal benchmarks. Your consequence, workload, and available time should determine yours.&lt;/p&gt;

&lt;p&gt;Record why you chose the current path and what would make you reconsider. Perhaps manual review becomes too slow. Perhaps a recurring exception becomes the main customer need. Perhaps the existing product adds the missing capability and your extension is no longer worth maintaining.&lt;/p&gt;

&lt;p&gt;You are allowed to retire your own clever solution. The repository does not get a vote.&lt;/p&gt;

&lt;h2&gt;
  
  
  The question I would give AI next
&lt;/h2&gt;

&lt;p&gt;Try this with your actual workflow:&lt;/p&gt;

&lt;blockquote&gt;
&lt;p&gt;Compare using my existing tools, adding one narrow extension, and building a custom app for this task: [task]. Use the same required outcome and three representative inputs for each option. Separate configuration problems, missing information, missing connections, and missing product behavior. Mark untested capabilities as unknown. List the recurring work I would own, propose a limited evaluation, and state what evidence would justify a custom build. Start with what I already have; do not purchase or activate paid services.&lt;/p&gt;
&lt;/blockquote&gt;

&lt;p&gt;Choose one task today and attempt it with your current setup. Then write down the first important gap you can demonstrate.&lt;/p&gt;

&lt;p&gt;The &lt;a href="https://marcusykim.gumroad.com/l/ai-app-builder-starter-prompts" rel="noopener noreferrer"&gt;$3 AI App Builder Starter Prompts&lt;/a&gt; can help you turn that gap into a guided first-build conversation.&lt;/p&gt;

&lt;p&gt;&lt;a href="https://marcusykim.com/review-radar/" rel="noopener noreferrer"&gt;Review Radar is coming soon&lt;/a&gt;. Its planned public-review research, tailored screens, and AI-ready project folder are intended to help you define a specific app before implementation. Explore the public preview and join the email waitlist. Checkout is not open, and the package does not promise a finished app or revenue.&lt;/p&gt;

&lt;p&gt;Build when you can explain the important gap, show why it matters, and accept the work of owning the solution.&lt;/p&gt;

&lt;p&gt;For the complete beginner playbook, AI App Builder From Zero covers planning, design, building, testing, and publishing. The standalone e-book is $9 with $30 off Bootcamp Bundle (Review Radar); the separate 40 Starter Prompts workbook is not included. The Gumroad e-book + all 40 Starter Prompts bundle is $10 with $70 off instead. Verified Apple Books and Kindle combined editions qualify for $70 off; retailer prices are shown by each store. One verified reader benefit per buyer, used once on either Bootcamp Bundle package when checkout opens; discounts do not stack, have no cash value, and exclude refunded or disputed purchases. Previously issued benefits retain their original terms. Bootcamp Bundle (Review Radar) is planned at $399 for one app project or $999 for three, with the same quality standards. Checkout remains closed.&lt;/p&gt;

&lt;p&gt;Standalone e-book: &lt;a href="https://marcusykim.gumroad.com/l/ai-app-builder-book-only" rel="noopener noreferrer"&gt;https://marcusykim.gumroad.com/l/ai-app-builder-book-only&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;Gumroad bundle: &lt;a href="https://marcusykim.gumroad.com/l/ai-app-builder-from-zero" rel="noopener noreferrer"&gt;https://marcusykim.gumroad.com/l/ai-app-builder-from-zero&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;You can also find me here:&lt;/p&gt;

&lt;p&gt;Medium: &lt;a href="https://medium.com/@marcusykim" rel="noopener noreferrer"&gt;https://medium.com/@marcusykim&lt;/a&gt;&lt;br&gt;
DEV.to: &lt;a href="https://dev.to/marcusykim"&gt;https://dev.to/marcusykim&lt;/a&gt;&lt;br&gt;
Website: &lt;a href="https://marcusykim.com/" rel="noopener noreferrer"&gt;https://marcusykim.com/&lt;/a&gt;&lt;br&gt;
X: &lt;a href="https://x.com/marcusykim" rel="noopener noreferrer"&gt;https://x.com/marcusykim&lt;/a&gt;&lt;br&gt;
LinkedIn: &lt;a href="https://www.linkedin.com/in/marcusykim/" rel="noopener noreferrer"&gt;https://www.linkedin.com/in/marcusykim/&lt;/a&gt;&lt;br&gt;
Upwork: &lt;a href="https://www.upwork.com/freelancers/marcusykim" rel="noopener noreferrer"&gt;https://www.upwork.com/freelancers/marcusykim&lt;/a&gt;&lt;/p&gt;

</description>
      <category>ai</category>
      <category>beginners</category>
      <category>programming</category>
      <category>productivity</category>
    </item>
  </channel>
</rss>
