<?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: Daniil Kornilov</title>
    <description>The latest articles on DEV Community by Daniil Kornilov (@__be2942592).</description>
    <link>https://dev.to/__be2942592</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%2F3744244%2F9c728e8b-0d87-4fb5-9e10-776dbedfbea4.png</url>
      <title>DEV Community: Daniil Kornilov</title>
      <link>https://dev.to/__be2942592</link>
    </image>
    <atom:link rel="self" type="application/rss+xml" href="https://dev.to/feed/__be2942592"/>
    <language>en</language>
    <item>
      <title>A Backup File Is Not a Restore Test</title>
      <dc:creator>Daniil Kornilov</dc:creator>
      <pubDate>Thu, 29 Oct 2026 16:23:24 +0000</pubDate>
      <link>https://dev.to/__be2942592/a-backup-file-is-not-a-restore-test-npb</link>
      <guid>https://dev.to/__be2942592/a-backup-file-is-not-a-restore-test-npb</guid>
      <description>&lt;p&gt;Your application exports a backup file. You can see it in Downloads, but have you tried using it to recover the data?&lt;/p&gt;

&lt;p&gt;A file can be present and still be incomplete, outdated or incompatible with the version you need. A small restore test gives you a more useful answer than checking for the file alone.&lt;/p&gt;

&lt;h2&gt;
  
  
  Try one record
&lt;/h2&gt;

&lt;p&gt;Imagine a local project planner that exports JSON. Add a clearly named test task, export the data and confirm the file was created. In a separate test copy or isolated environment, import the file and check that the task and its details are present.&lt;/p&gt;

&lt;p&gt;Some imports replace the current project. Read the warning and use a safe test environment; do not overwrite your working data. If the export contains private information, handle the copy with the same care as the original.&lt;/p&gt;

&lt;p&gt;Then record what you checked: the application version, the file used and the result. If the import fails or a field is missing, investigate before relying on that export for recovery.&lt;/p&gt;

&lt;h2&gt;
  
  
  Check again after changes
&lt;/h2&gt;

&lt;p&gt;One successful test covers the file and version you tested. Repeat it after changes to the export format, import process or important data fields. For a service, use a suitable isolated test environment and check a real user flow after recovery.&lt;/p&gt;

&lt;p&gt;What is the first thing you check after restoring a backup?&lt;/p&gt;

</description>
      <category>programming</category>
      <category>beginners</category>
      <category>discuss</category>
      <category>abotwrotethis</category>
    </item>
    <item>
      <title>How to Explain Your Contribution to a Team Project</title>
      <dc:creator>Daniil Kornilov</dc:creator>
      <pubDate>Thu, 29 Oct 2026 16:22:15 +0000</pubDate>
      <link>https://dev.to/__be2942592/how-to-explain-your-contribution-to-a-team-project-1ool</link>
      <guid>https://dev.to/__be2942592/how-to-explain-your-contribution-to-a-team-project-1ool</guid>
      <description>&lt;p&gt;You worked on a team project and want to add it to your portfolio. The project had several contributors, so a list of everything the product does will not tell a reader what you built.&lt;/p&gt;

&lt;p&gt;Start with the shared goal, then describe your own part and give the reader something they can inspect.&lt;/p&gt;

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

&lt;p&gt;Imagine a team built an online shop. One developer worked on the delivery-address form. If that was your actual contribution, you could write:&lt;/p&gt;

&lt;blockquote&gt;
&lt;p&gt;Our team built an online shop. I added a check for an empty delivery address and a message explaining what the customer needs to enter. The screenshot shows the message after submitting an empty form.&lt;/p&gt;
&lt;/blockquote&gt;

&lt;p&gt;This is a fictional example. Adapt the structure to work you actually did. If someone else designed the interaction or reviewed the change, you can say so. Teamwork is useful context.&lt;/p&gt;

&lt;h2&gt;
  
  
  Choose evidence you can share
&lt;/h2&gt;

&lt;p&gt;A public pull request can show a specific change and the discussion around it. A screenshot or demo can show the result. Check that the link is accessible to your reader and that you have permission to share it.&lt;/p&gt;

&lt;p&gt;For confidential projects, describe an approved, anonymized version of the problem or create a separate example. Avoid publishing customer information or private code. A sample is useful, but label it as a sample rather than presenting it as production evidence.&lt;/p&gt;

&lt;p&gt;What helps you explain your contribution when several people worked on the same feature?&lt;/p&gt;

</description>
      <category>career</category>
      <category>beginners</category>
      <category>discuss</category>
      <category>abotwrotethis</category>
    </item>
    <item>
      <title>Your CSV Says 001. Why Does the Spreadsheet Show 1?</title>
      <dc:creator>Daniil Kornilov</dc:creator>
      <pubDate>Wed, 28 Oct 2026 21:19:38 +0000</pubDate>
      <link>https://dev.to/__be2942592/your-csv-says-001-why-does-the-spreadsheet-show-1-14cl</link>
      <guid>https://dev.to/__be2942592/your-csv-says-001-why-does-the-spreadsheet-show-1-14cl</guid>
      <description>&lt;p&gt;A product code is &lt;code&gt;001&lt;/code&gt; in a CSV file. You open it in a spreadsheet, and the cell shows &lt;code&gt;1&lt;/code&gt;.&lt;/p&gt;

&lt;p&gt;The spreadsheet may have interpreted the code as a number. That matters if &lt;code&gt;001&lt;/code&gt; and &lt;code&gt;1&lt;/code&gt; are different identifiers in your system.&lt;/p&gt;

&lt;h2&gt;
  
  
  Check the original first
&lt;/h2&gt;

&lt;p&gt;Open a trusted copy of the original CSV in a plain-text editor and look for the value in the relevant column. If the original contains &lt;code&gt;001&lt;/code&gt;, keep that file unchanged while you work on a separate copy.&lt;/p&gt;

&lt;p&gt;Use your spreadsheet's import flow and set the identifier column to &lt;strong&gt;text&lt;/strong&gt; before loading it. The wording differs between apps. Check that an earlier automatic conversion has not already removed the zeros, then compare a few known codes against the original. &lt;a href="https://support.microsoft.com/en-us/excel/keeping-leading-zeros-and-large-numbers" rel="noopener noreferrer"&gt;Microsoft explains how to import such columns as text in Excel&lt;/a&gt;.&lt;/p&gt;

&lt;p&gt;If you export the result to CSV and open it again, repeat the check: a spreadsheet may interpret the column as numbers again during the next import. Quotation marks in CSV do not guarantee that every spreadsheet will preserve the value as text.&lt;/p&gt;

&lt;h2&gt;
  
  
  If the original already says &lt;code&gt;1&lt;/code&gt;
&lt;/h2&gt;

&lt;p&gt;You cannot tell from that value alone whether it used to be &lt;code&gt;001&lt;/code&gt;, &lt;code&gt;01&lt;/code&gt; or simply &lt;code&gt;1&lt;/code&gt;. Look for a trustworthy source, backup or documented identifier rule before changing it. Adding zeros based on a guess can create a different wrong code.&lt;/p&gt;

&lt;p&gt;An identifier can look like a number without being something you calculate with. Decide its format from the source system, then check it at every import and export.&lt;/p&gt;

&lt;p&gt;Have you found an identifier changing when a file moved between tools?&lt;/p&gt;

</description>
      <category>data</category>
      <category>beginners</category>
      <category>programming</category>
      <category>abotwrotethis</category>
    </item>
    <item>
      <title>An Interviewer Asked About a Tool You Haven't Used. What Do You Say?</title>
      <dc:creator>Daniil Kornilov</dc:creator>
      <pubDate>Wed, 28 Oct 2026 21:18:36 +0000</pubDate>
      <link>https://dev.to/__be2942592/an-interviewer-asked-about-a-tool-you-havent-used-what-do-you-say-3mjj</link>
      <guid>https://dev.to/__be2942592/an-interviewer-asked-about-a-tool-you-havent-used-what-do-you-say-3mjj</guid>
      <description>&lt;p&gt;A job description asks for a tool you have not used. The interviewer asks how much experience you have with it.&lt;/p&gt;

&lt;p&gt;You do not need to turn a gap into a story you cannot defend. Explain the gap, then connect it to something you have actually done.&lt;/p&gt;

&lt;h2&gt;
  
  
  Try a specific answer
&lt;/h2&gt;

&lt;p&gt;Imagine the role asks for Docker, but your work so far has involved running and troubleshooting an application directly on a server.&lt;/p&gt;

&lt;p&gt;If that is true for you, an honest answer could be:&lt;/p&gt;

&lt;blockquote&gt;
&lt;p&gt;“I haven't used Docker in a production project yet. I have deployed an application directly to a server and investigated startup problems. I'd like to understand how your team packages and deploys its services, then work through that process in a safe test environment.”&lt;/p&gt;
&lt;/blockquote&gt;

&lt;p&gt;That answer separates what you have done from what you still need to learn. It also gives the interviewer a real project to ask about.&lt;/p&gt;

&lt;p&gt;Do not claim production experience just because you followed a tutorial. If the only thing you have done is a tutorial, say so and explain what you built or checked. If you have no related experience yet, it is fine to say that too.&lt;/p&gt;

&lt;p&gt;Before an interview, pick one real example for each important requirement: what you worked on, what you personally did and what you would investigate next. Where there is no example, write down the gap rather than filling it with a vague claim.&lt;/p&gt;

&lt;p&gt;How do you explain a skill you are still learning when an interviewer asks about it?&lt;/p&gt;

</description>
      <category>career</category>
      <category>beginners</category>
      <category>discuss</category>
      <category>abotwrotethis</category>
    </item>
    <item>
      <title>The Download Worked. Can Your Customer Use the File?</title>
      <dc:creator>Daniil Kornilov</dc:creator>
      <pubDate>Wed, 28 Oct 2026 01:44:52 +0000</pubDate>
      <link>https://dev.to/__be2942592/the-download-worked-can-your-customer-use-the-file-3aag</link>
      <guid>https://dev.to/__be2942592/the-download-worked-can-your-customer-use-the-file-3aag</guid>
      <description>&lt;p&gt;Someone buys a digital file from you. The payment succeeds and a download link appears.&lt;/p&gt;

&lt;p&gt;Can the buyer open the file and get a first result without asking for help?&lt;/p&gt;

&lt;p&gt;A successful upload tells you the file reached the platform. It does not show what the buyer receives or whether the instructions match the package.&lt;/p&gt;

&lt;h2&gt;
  
  
  Try the buyer's route
&lt;/h2&gt;

&lt;p&gt;Imagine you sell a downloadable template. Before release, get the file through the same delivery route a buyer uses, using a test purchase if the platform supports one. If you cannot use that route without paying, check the available delivery preview and label what you could not test.&lt;/p&gt;

&lt;p&gt;On a device or account without your working files, try the steps exactly as a customer would:&lt;/p&gt;

&lt;ol&gt;
&lt;li&gt;Download the delivered file and check that it opens.&lt;/li&gt;
&lt;li&gt;If it is an archive, extract it and find the starting file mentioned in the instructions.&lt;/li&gt;
&lt;li&gt;Follow the instructions to create a small example or open the included sample.&lt;/li&gt;
&lt;li&gt;Check that the result appears and that the instructions explain how to save it, if saving is part of the product.&lt;/li&gt;
&lt;/ol&gt;

&lt;p&gt;If you get stuck, record the step and fix the file or the instructions. Test again using a fresh copy of the package.&lt;/p&gt;

&lt;p&gt;Keep the first instruction concrete: “Extract the ZIP, then open Start Here” is easier to follow than “Use the included materials.” Only name a file that is actually in the package, and tell buyers about any required software before purchase.&lt;/p&gt;

&lt;p&gt;What is the first action a customer should take after downloading your product?&lt;/p&gt;

</description>
      <category>webdev</category>
      <category>testing</category>
      <category>beginners</category>
      <category>abotwrotethis</category>
    </item>
    <item>
      <title>No Users Yet? Show What Your Portfolio Project Actually Does</title>
      <dc:creator>Daniil Kornilov</dc:creator>
      <pubDate>Wed, 28 Oct 2026 01:43:07 +0000</pubDate>
      <link>https://dev.to/__be2942592/no-users-yet-show-what-your-portfolio-project-actually-does-597m</link>
      <guid>https://dev.to/__be2942592/no-users-yet-show-what-your-portfolio-project-actually-does-597m</guid>
      <description>&lt;p&gt;You built a small expense tracker for your portfolio. It has no customers, and you have not measured whether it saves anyone time.&lt;/p&gt;

&lt;p&gt;That does not mean you have nothing useful to show. It means you should describe what the project does and show evidence you actually have.&lt;/p&gt;

&lt;h2&gt;
  
  
  Turn a feature into an example
&lt;/h2&gt;

&lt;p&gt;Imagine the tracker lets someone enter an amount, choose a category and see a monthly total. Here is a fictional way to explain it:&lt;/p&gt;

&lt;blockquote&gt;
&lt;p&gt;This personal project groups expenses by category. To check the total, add two expenses in the same month, then remove one and confirm the total changes. The demo and its test steps are linked below.&lt;/p&gt;
&lt;/blockquote&gt;

&lt;p&gt;A reader can follow that example and inspect the behavior. It is more useful than saying the app “improved financial productivity by 40%” when no such result was measured.&lt;/p&gt;

&lt;p&gt;If your project is different, use its real behavior and actual links. A test, a screenshot or a working demo can support a specific claim, but it cannot prove that people used the app or saved money.&lt;/p&gt;

&lt;h2&gt;
  
  
  Be clear about the limits
&lt;/h2&gt;

&lt;p&gt;Say who built which part if it was a team project. Mention whether the example uses sample data and what the app does not yet handle. For instance, if entries stay only in one browser, explain that before someone expects their data to appear on another device.&lt;/p&gt;

&lt;p&gt;A small, honest result gives someone a starting point for understanding your work. You can add measured outcomes later if you actually collect them.&lt;/p&gt;

&lt;p&gt;What is one thing someone can try or inspect in your latest project?&lt;/p&gt;

</description>
      <category>career</category>
      <category>beginners</category>
      <category>webdev</category>
      <category>abotwrotethis</category>
    </item>
    <item>
      <title>Two Rows Have the Same ID. Which One Should You Trust?</title>
      <dc:creator>Daniil Kornilov</dc:creator>
      <pubDate>Tue, 27 Oct 2026 10:31:37 +0000</pubDate>
      <link>https://dev.to/__be2942592/two-rows-have-the-same-id-which-one-should-you-trust-2f42</link>
      <guid>https://dev.to/__be2942592/two-rows-have-the-same-id-which-one-should-you-trust-2f42</guid>
      <description>&lt;p&gt;You are comparing two lists of stock. In the new file, item A-17 appears twice: one row says there are 2 left, the other says 5.&lt;/p&gt;

&lt;p&gt;Which row is correct? The two rows alone do not tell you.&lt;/p&gt;

&lt;p&gt;Perhaps the item was duplicated by mistake. Or perhaps the rows refer to different warehouses, but the file does not include the warehouse name. Taking the first row automatically can produce a tidy-looking comparison with the wrong answer.&lt;/p&gt;

&lt;h2&gt;
  
  
  Separate the uncertain rows
&lt;/h2&gt;

&lt;p&gt;Put repeated IDs aside for review. Check the original source and look for a field that distinguishes the records, such as warehouse or product variant.&lt;/p&gt;

&lt;p&gt;Then decide what makes a record unique for your task. If one product can appear once per warehouse, the product ID alone is not enough. You may need a key that includes both product and warehouse.&lt;/p&gt;

&lt;p&gt;For example, &lt;code&gt;A-17 / north&lt;/code&gt; and &lt;code&gt;A-17 / south&lt;/code&gt; can represent two different records. But only use those labels if the source actually provides that distinction. Do not invent missing information to make the duplicate disappear.&lt;/p&gt;

&lt;p&gt;You can continue comparing the unambiguous rows while keeping the uncertain ones visible in a separate review list. Fix or clarify the source before treating those rows as a reliable result.&lt;/p&gt;

&lt;p&gt;When you find duplicate IDs, what do you check first?&lt;/p&gt;

</description>
      <category>data</category>
      <category>beginners</category>
      <category>testing</category>
      <category>abotwrotethis</category>
    </item>
    <item>
      <title>Your Product Page Has the New Price. What Does Checkout Show?</title>
      <dc:creator>Daniil Kornilov</dc:creator>
      <pubDate>Tue, 27 Oct 2026 10:31:15 +0000</pubDate>
      <link>https://dev.to/__be2942592/your-product-page-has-the-new-price-what-does-checkout-show-53n4</link>
      <guid>https://dev.to/__be2942592/your-product-page-has-the-new-price-what-does-checkout-show-53n4</guid>
      <description>&lt;p&gt;The product page shows the new price. You refresh it and everything looks right.&lt;/p&gt;

&lt;p&gt;But a customer sees more than the product page. They may add the item to a cart and move on to checkout, where an old price could still appear.&lt;/p&gt;

&lt;h2&gt;
  
  
  Follow one item through the order
&lt;/h2&gt;

&lt;p&gt;Open the public site on a phone, as a visitor. Find the item, add it to the cart and continue to checkout.&lt;/p&gt;

&lt;p&gt;Compare the item's price at each step. Then look at the final total: delivery, taxes or other fees can make it different from the item price. The important thing is that the customer can understand what was added.&lt;/p&gt;

&lt;p&gt;You do not have to pay to perform this check. If you need to submit an order, mark it as a test and make sure nobody starts fulfilling it.&lt;/p&gt;

&lt;p&gt;If the item price changes unexpectedly, record where it first differs and what you did before it happened. That gives the person fixing it a useful starting point.&lt;/p&gt;

&lt;p&gt;A correct product page is a good start. A consistent path to checkout gives you more confidence that customers see the price you intended.&lt;/p&gt;

&lt;p&gt;What do you check after changing a price: just the page, or the cart and checkout too?&lt;/p&gt;

</description>
      <category>webdev</category>
      <category>testing</category>
      <category>beginners</category>
      <category>abotwrotethis</category>
    </item>
    <item>
      <title>“Click Here” for What? Your Links Should Answer That.</title>
      <dc:creator>Daniil Kornilov</dc:creator>
      <pubDate>Mon, 26 Oct 2026 19:06:13 +0000</pubDate>
      <link>https://dev.to/__be2942592/click-here-for-what-your-links-should-answer-that-jkp</link>
      <guid>https://dev.to/__be2942592/click-here-for-what-your-links-should-answer-that-jkp</guid>
      <description>&lt;p&gt;A page has three useful resources.&lt;/p&gt;

&lt;p&gt;Every link says “Click here.”&lt;/p&gt;

&lt;p&gt;One opens a price list. One downloads a checklist. One starts a booking form. The destination matters more than the instruction to click.&lt;/p&gt;

&lt;h2&gt;
  
  
  Name what is on the other side
&lt;/h2&gt;

&lt;p&gt;Compare these labels:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;“Click here” → “View the price list.”&lt;/li&gt;
&lt;li&gt;“Learn more” → “See what is included in the website package.”&lt;/li&gt;
&lt;li&gt;“Download” → “Download the launch checklist (PDF).”&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;Only promise a PDF if the link really opens or downloads one. A clearer label still needs the correct destination.&lt;/p&gt;

&lt;p&gt;This is a small change you can review without redesigning the page: read the label, follow the link, and compare the promise with what appears.&lt;/p&gt;

&lt;h2&gt;
  
  
  Context can help. Guessing should not be the job
&lt;/h2&gt;

&lt;p&gt;“Read more” is not automatically wrong. A descriptive sentence or article heading can give it meaningful context.&lt;/p&gt;

&lt;p&gt;W3C's &lt;a href="https://www.w3.org/WAI/WCAG22/Understanding/link-purpose-in-context.html" rel="noopener noreferrer"&gt;explanation of link purpose&lt;/a&gt; allows the purpose to come from the link text together with its associated context. It also recommends meaningful link text where possible. This helps people who navigate using assistive technology, including a list of links.&lt;/p&gt;

&lt;p&gt;So you do not need to turn every link into a sentence. Start with the vague ones that lead to different things.&lt;/p&gt;

&lt;p&gt;Open one page you maintain. Can you tell where its links go before following them?&lt;/p&gt;

&lt;p&gt;Which label would you change first?&lt;/p&gt;

</description>
      <category>webdev</category>
      <category>ux</category>
      <category>beginners</category>
      <category>abotwrotethis</category>
    </item>
    <item>
      <title>Your Contact Button Works. Does the Message Arrive?</title>
      <dc:creator>Daniil Kornilov</dc:creator>
      <pubDate>Mon, 26 Oct 2026 19:06:04 +0000</pubDate>
      <link>https://dev.to/__be2942592/your-contact-button-works-does-the-message-arrive-eld</link>
      <guid>https://dev.to/__be2942592/your-contact-button-works-does-the-message-arrive-eld</guid>
      <description>&lt;p&gt;A visitor fills in your contact form, presses Send and sees a pleasant green message.&lt;/p&gt;

&lt;p&gt;You check the animation. It looks good.&lt;/p&gt;

&lt;p&gt;But did the inquiry reach the person who is supposed to answer it?&lt;/p&gt;

&lt;p&gt;That is a different thing to check.&lt;/p&gt;

&lt;h2&gt;
  
  
  Follow one message to its destination
&lt;/h2&gt;

&lt;p&gt;Imagine a small business website that sends inquiries to an email inbox. A useful release check is simple:&lt;/p&gt;

&lt;ol&gt;
&lt;li&gt;Open the public page on a phone, signed out of your admin account.&lt;/li&gt;
&lt;li&gt;Submit a clearly marked test inquiry using an address you control.&lt;/li&gt;
&lt;li&gt;Find that exact message in the intended inbox.&lt;/li&gt;
&lt;li&gt;Check that the sender's reply address and message are intact.&lt;/li&gt;
&lt;li&gt;Reply and confirm that the answer reaches your test address.&lt;/li&gt;
&lt;/ol&gt;

&lt;p&gt;You have checked one real route through the site. A screenshot of the green message cannot show you the same thing.&lt;/p&gt;

&lt;p&gt;If the inquiry does not arrive, start tracing that route: was it recorded by the form service, sent to the intended address, or placed in spam? Check the evidence before guessing at a cause.&lt;/p&gt;

&lt;h2&gt;
  
  
  Make the confirmation match what you know
&lt;/h2&gt;

&lt;p&gt;“Your request reached our team” is a stronger claim than “Your request was submitted.” Use wording that your system can actually support.&lt;/p&gt;

&lt;p&gt;W3C's &lt;a href="https://www.w3.org/WAI/tutorials/forms/notifications/" rel="noopener noreferrer"&gt;form notification guidance&lt;/a&gt; explains why users need clear feedback about the result of a submission. That feedback should also be truthful.&lt;/p&gt;

&lt;p&gt;A successful test message does not prove that every future delivery will work. Keep a way to notice failures after launch, and repeat this check when the form or its destination changes.&lt;/p&gt;

&lt;p&gt;What do you use as proof that your contact form works: the success screen, or a message someone can answer?&lt;/p&gt;

</description>
      <category>webdev</category>
      <category>testing</category>
      <category>beginners</category>
      <category>abotwrotethis</category>
    </item>
    <item>
      <title>Your Form Says “Invalid.” Your User Says “Now What?”</title>
      <dc:creator>Daniil Kornilov</dc:creator>
      <pubDate>Sun, 25 Oct 2026 19:32:23 +0000</pubDate>
      <link>https://dev.to/__be2942592/your-form-says-invalid-your-user-says-now-what-3l90</link>
      <guid>https://dev.to/__be2942592/your-form-says-invalid-your-user-says-now-what-3l90</guid>
      <description>&lt;p&gt;You spend twenty minutes polishing a button.&lt;/p&gt;

&lt;p&gt;Then the form tells someone: “Invalid input.”&lt;/p&gt;

&lt;p&gt;Invalid what? The date? The phone number? The file?&lt;/p&gt;

&lt;p&gt;A neat interface still needs to explain what to do next.&lt;/p&gt;

&lt;h2&gt;
  
  
  Change the message, not just its color
&lt;/h2&gt;

&lt;p&gt;Imagine a profile form that accepts JPG and PNG images up to 5 MB. Someone selects a larger file.&lt;/p&gt;

&lt;p&gt;“Upload failed” only reports the failure.&lt;/p&gt;

&lt;p&gt;“Your image is over 5 MB. Choose a smaller JPG or PNG” gives the person a next step.&lt;/p&gt;

&lt;p&gt;The wording must match the real rule. If the upload failed because the connection dropped, asking for a smaller image would be misleading.&lt;/p&gt;

&lt;p&gt;The same idea works elsewhere:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;“Invalid date” → “Enter the date as DD/MM/YYYY.”&lt;/li&gt;
&lt;li&gt;“Required” → “Enter an email address so we can send your receipt.”&lt;/li&gt;
&lt;li&gt;“Something went wrong” → explain the known problem, or say that you could not identify it. Do not invent a cause.&lt;/li&gt;
&lt;/ul&gt;

&lt;h2&gt;
  
  
  Put the help where the problem is
&lt;/h2&gt;

&lt;p&gt;Show the message near the field. Keep the person's other entries. A red outline alone does not explain the fix.&lt;/p&gt;

&lt;p&gt;W3C's &lt;a href="https://www.w3.org/WAI/tutorials/forms/notifications/" rel="noopener noreferrer"&gt;form notification guidance&lt;/a&gt; recommends clear error descriptions and simple correction instructions. For developers, it also describes linking fields and messages with &lt;code&gt;aria-describedby&lt;/code&gt; so that assistive technology can connect them.&lt;/p&gt;

&lt;p&gt;A quick review: deliberately submit the wrong value. Read only the message. Does it tell you which field needs attention and how to continue?&lt;/p&gt;

&lt;p&gt;If you have to ask the developer what the message means, the wording needs another pass.&lt;/p&gt;

&lt;p&gt;Which error message in your product would you rewrite first?&lt;/p&gt;

</description>
      <category>webdev</category>
      <category>ux</category>
      <category>beginners</category>
      <category>abotwrotethis</category>
    </item>
    <item>
      <title>Stop Asking AI to “Make It Better.” Name One Thing.</title>
      <dc:creator>Daniil Kornilov</dc:creator>
      <pubDate>Sun, 25 Oct 2026 19:30:21 +0000</pubDate>
      <link>https://dev.to/__be2942592/stop-asking-ai-to-make-it-better-name-one-thing-2cg3</link>
      <guid>https://dev.to/__be2942592/stop-asking-ai-to-make-it-better-name-one-thing-2cg3</guid>
      <description>&lt;p&gt;“Make this page better.”&lt;/p&gt;

&lt;p&gt;That sounds like a request. It leaves a lot of decisions open.&lt;/p&gt;

&lt;p&gt;Better for whom? Easier to read? Faster to load? More colorful? An assistant can change all three while missing the thing that bothered you.&lt;/p&gt;

&lt;p&gt;Take a simple example: the contact button is hard to find on a phone.&lt;/p&gt;

&lt;h2&gt;
  
  
  Give it a job you can point to
&lt;/h2&gt;

&lt;p&gt;Instead of:&lt;/p&gt;

&lt;blockquote&gt;
&lt;p&gt;Make the landing page look more professional.&lt;/p&gt;
&lt;/blockquote&gt;

&lt;p&gt;Try:&lt;/p&gt;

&lt;blockquote&gt;
&lt;p&gt;On a 360px-wide screen, make the contact button easy to find in the first section. Keep the current text, colors and desktop layout. Change only the button's size and spacing. Show me the changes before applying anything else.&lt;/p&gt;
&lt;/blockquote&gt;

&lt;p&gt;The second request names the problem, the allowed change and what should stay put. You can open the page on a phone-sized screen and judge the result.&lt;/p&gt;

&lt;p&gt;It is a clearer assignment, not proof that a particular model will follow it. You still have to inspect the output.&lt;/p&gt;

&lt;h2&gt;
  
  
  A small fix should have a small finish line
&lt;/h2&gt;

&lt;p&gt;For this example, the finish line is practical:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;The button is visible in the first section without sideways scrolling.&lt;/li&gt;
&lt;li&gt;Its label still says what happens when you press it.&lt;/li&gt;
&lt;li&gt;The desktop layout and the rest of the page remain as they were.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;If changing only size and spacing cannot meet that goal, ask the assistant to explain the conflict before expanding the job.&lt;/p&gt;

&lt;p&gt;“Improve everything” makes it hard to tell whether you are finished. One visible problem gives you something to accept, reject or revise.&lt;/p&gt;

&lt;p&gt;This also works for writing. Instead of “make it smarter,” try “replace the jargon, keep one example and cut the introduction.” You can check each part without guessing what “smarter” means.&lt;/p&gt;

&lt;p&gt;What is the smallest change you actually want from your next AI request?&lt;/p&gt;

</description>
      <category>ai</category>
      <category>webdev</category>
      <category>discuss</category>
      <category>abotwrotethis</category>
    </item>
  </channel>
</rss>
