DEV Community: Shawon Saha

The "Windows Update Ate My Grub" Fix: A One-Line Lifesaver

Shawon Saha — Tue, 07 Apr 2026 22:09:53 +0000

It’s a tale as old as time (or at least as old as UEFI). You spend your morning updating Windows, hit restart, and instead of your familiar GRUB menu offering a choice between Linux and Windows, you’re booted straight into Windows.

Your Linux partition isn't gone, and your files are safe—Windows has simply "reclaimed" the boot priority, effectively hiding the door to your Ubuntu installation.

While many guides suggest booting from a Live USB and re-installing GRUB (which takes ages), there is a surgical, one-line fix you can run right from inside Windows.

The Magic Command

If you are using Ubuntu (or most Ubuntu-based distros like Mint or Pop!_OS), open the Command Prompt as Administrator and run:

bcdedit /set {bootmgr} path \efi\ubuntu\grubx64.efi

What does this actually do?

Windows uses a tool called bcdedit (Boot Configuration Data editor) to manage how the computer starts.

{bootmgr}: This targets the Windows Boot Manager.
path \efi\ubuntu\grubx64.efi: This tells the Windows Boot Manager that instead of looking for the Windows startup file, it should point directly to the GRUB bootloader file located on your EFI partition.

Step-by-Step Guide

Boot into Windows: Since GRUB is missing, you’re likely already here.
Open CMD as Admin: Press the Win key, type cmd, right-click it, and select Run as Administrator. This is crucial; the command will fail without elevated permissions.
Run the Command: Copy and paste the command above and hit Enter. You should see a message saying "The operation completed successfully."
Restart: Reboot your machine. Your GRUB menu should reappear, giving you back access to your Linux world.

"It didn't work!" (Troubleshooting)

If the command runs but nothing changes, or if you get an error, check these two things:

Secure Boot: Sometimes Secure Boot prevents the handoff to GRUB. Try disabling it in your BIOS/UEFI settings if the problem persists.
Path Variation: If you aren't using Ubuntu, the folder name might be different. For example, Fedora users would likely use \efi\fedora\grubx64.efi.

Why does this happen?

Windows updates occasionally overwrite the "Boot Order" stored in your motherboard’s NVRAM to ensure Windows remains the default OS. By running this command, you aren't "breaking" Windows; you're just politely telling the motherboard that GRUB is the rightful conductor of the orchestra.

Pro-tip: Keep this command in a Note or a physical sticky note. Windows updates are inevitable, and having this shortcut saves you from a 30-minute troubleshooting session down the road!

How to Check the Number of Lines Changed in Your Current Git Branch Compared to Main

Shawon Saha — Mon, 24 Nov 2025 10:48:29 +0000

When working with Git, developers often need to understand how much their current branch differs from the main branch. This can help in assessing the scope of changes, planning reviews, or making decisions before merging. One useful metric is the total number of lines added and removed between branches.

Why Check Lines of Diff?

Counting the lines of code changed gives a quick snapshot of the volume of work done. It helps to:

Gauge the size of your feature or fix.
Estimate code review effort.
Track progress against expectations.
Identify large or complex changes that might require extra testing.

Using Git to Check Line Differences

The Git command line provides simple ways to check these differences precisely.

The most straightforward command is:

git diff --shortstat main...HEAD

Here’s how it works:

git diff shows changes between commits or branches.
main...HEAD compares your current branch (HEAD) with the main branch.
--shortstat gives a brief summary report with the total files changed, and lines added and deleted.

For example, running this command might show:

3 files changed, 45 insertions(+), 20 deletions(-)

This means across 3 files, you've added 45 lines and removed 20 lines compared to main.

Getting More Detailed Line Counts

If you want to see the exact line changes per file, you can use:

git diff main...HEAD --numstat

This command outputs a list where each line contains the number of added and deleted lines per file. It’s handy for deeper inspection or for scripting purposes.

How to Disable Automatic Rearrangement of Desktops (Spaces) on Mac

Shawon Saha — Fri, 21 Nov 2025 09:58:59 +0000

macOS offers a powerful feature called Spaces, which allows users to organize their open applications across multiple virtual desktops or workspaces. This helps maintain an organized workflow by separating projects or tasks into distinct environments. However, a feature that automatically rearranges these desktops based on your recent app usage can sometimes disrupt this organization. If you prefer your desktops to remain in a fixed order, it is essential to disable this auto-rearrangement.

What is Desktop (Spaces) Auto Rearrangement?

By default, macOS reorders your desktops (also called Spaces) so that the most recently used desktop appears next to your current one. While this can be useful for some people to quickly switch between frequently used spaces, it often causes confusion and breaks your muscle memory of where apps or documents reside.

For instance, if you have Chrome on Desktop 2 and a document on Desktop 3, after switching between them, macOS might shuffle these desktops, making it hard to keep track of your workspace layout.

Why Disable Auto Rearrangement?

Disabling this feature locks your desktops in the order you set, avoiding unexpected shuffling and helping maintain a consistent workflow. It is especially helpful for users who rely heavily on multiple desktops or workspaces for different tasks, making navigation predictable and stable.

How to Disable Auto Rearrangement of Desktops on macOS

The process to disable automatic rearrangement is straightforward and involves adjusting the Mission Control settings from System Settings. Here’s how:

Click the Apple menu () and open System Settings.
In the sidebar, select Desktop & Dock.
Scroll down to the Mission Control section.
Find the option labeled "Automatically rearrange Spaces based on most recent use".
Toggle this option off.

Once disabled, macOS will no longer move your desktops around based on usage, preserving the custom order you prefer.

Additional Tips

This setting is relevant for macOS Ventura and later. On older macOS versions, look for the similar option under System Preferences > Mission Control.
Disabling this feature does not affect your ability to create or delete desktops; it only stops the system from rearranging existing ones.
If you use full-screen apps, they will still create new spaces as usual, just without automatic reshuffling.

Conclusion

The automatic rearrangement of deskspaces can disrupt productivity and cause frustration for users accustomed to a set order of virtual desktops. Thankfully, macOS allows you to disable this feature easily, giving you control back over your workspace organization. By following the steps outlined above, you can keep your desktops locked in place and enjoy a more stable and predictable workflow.

How to Reset a Remote Git Repository to Match Your Local State: A Careful Approach

Shawon Saha — Wed, 17 Sep 2025 09:04:02 +0000

Working with Git and GitHub is great until a mistake or unwanted commit is pushed to the remote repository. Sometimes, you need to undo those mistakes and force the remote repository to match your corrected local state. This must be done carefully to avoid disrupting collaborators and losing important work.

This guide will walk you through the safest and most effective way to reset a remote repository to a specific commit in your local repository while highlighting important precautions.

Step 1: Backup Your Current State

Before making any changes that rewrite history, always take a backup of your current local branch. This protects you from accidental data loss and allows you to recover changes if needed.

git branch backup-before-force-push

This creates a new branch backup-before-force-push that preserves your current state.

Step 2: Fetch Latest Changes from Remote

Make sure your local Git repository has the latest information from the remote repository:

git fetch origin

This updates all remote tracking branches without modifying your local branch or working directory.

Step 3: Reset Your Local Branch to the Desired Commit

Identify the commit hash you want to reset to (the last known good state). Then, reset your local branch hard to that commit:

git reset --hard <good-commit-hash>

Replace <good-commit-hash> with the actual commit ID. This moves your branch pointer and makes your working directory match the specified commit exactly.

Step 4: Force Push to Overwrite Remote History

Now that your local branch is at the correct commit, you need to force push to update the remote repository:

git push --force-with-lease origin main

This command overwrites the remote branch main with your local branch state.

--force-with-lease is safer than a simple force because it checks if the remote branch has changed since you last fetched, preventing you from accidentally overwriting someone else's work.
Replace main with your branch name if different.

Important Warnings and Best Practices

Communicate with your team: If working with collaborators, notify them before rewriting history. They will need to sync their local repositories afterwards to avoid conflicts.
Backup important changes: Double-check you have saved any work that shouldn't be lost, as git reset --hard and force push discard changes from both local and remote.
Force push carefully: Rewriting history can cause confusion if done without care, so use --force-with-lease whenever possible.
Prepare collaborators to reset their local branches: Anyone who pulled the previous commits will need to reset or reclone to align with the rewritten history.

Summary

Resetting a remote Git repository to match a clean local state involves:

Backing up your current local branch
Fetching the latest changes from remote
Hard resetting your local branch to a known good commit
Force pushing your rebased branch to remote with --force-with-lease

By following these steps carefully and communicating effectively, you can safely undo mistakes pushed to GitHub and maintain clean project history.

This approach ensures your local and remote repositories are perfectly aligned while minimizing risks associated with overwriting shared history.

If unsure, always make backups and coordinate with your team!

How To Suppress Build Errors in Next.js with TypeScript

Shawon Saha — Wed, 17 Sep 2025 08:47:49 +0000

In the fast-paced world of web development, minimizing roadblocks during prototyping or initial integration can be useful. Suppressing build errors is one way to keep your pipeline moving, especially when integrating large third-party libraries. Here’s how it’s commonly done in a Next.js project with TypeScript—and why you need to be careful.

Suppressing TypeScript Build Errors in `next.config.ts` or `next.config.mjs`

Next.js provides a straightforward way to ignore TypeScript build errors by updating the next.config.ts/next.config.mjs file:

// next.config.ts/mjs
export default {
  typescript: {
    ignoreBuildErrors: true,
  },
};

Setting ignoreBuildErrors to true tells Next.js to proceed with the build even if TypeScript finds type errors.

Disabling Strict Type Checking in `tsconfig.json`

Another approach is to loosen TypeScript’s strictness in your tsconfig.json:

{
  "compilerOptions": {
    "strict": false
  }
}

Turning off "strict" disables a suite of advanced type-checking features, which can make builds pass more easily but also reduces the safety and reliability of your codebase.

When and Why You Might Do This

Rapid prototyping: When integrating complex packages or fast-tracking proof-of-concept work.
3rd-party code: Some external libraries might introduce type errors you can’t immediately address.
Legacy code: Migrating older codebases where fixing all type errors upfront is impractical.

Best Practices and Warnings

Temporary measure: Only suppress errors short-term. Plan to re-enable strict checking before major releases.
Track suppressed errors: Maintain a list of known issues to avoid introducing new bugs.
Code review required: All uses of suppressed errors should be reviewed, and a plan for resolution should be in place.

Conclusion

Suppressing errors can unblock your workflow, but always treat it as a temporary solution. Ultimately, type errors exist to prevent runtime bugs—ignoring them for too long can lead to greater technical debt.

References:

Next.js Documentation

TypeScript Compiler Options

This approach helps you move quickly—just remember to address the root issues when possible!

Streamlining Your Git Workflow: A Developer's Guide to Efficient Branch Creation

Shawon Saha — Wed, 28 May 2025 05:26:28 +0000

As developers, we've all been there – repeatedly typing the same sequence of Git commands every time we want to start working on a new feature. The traditional workflow of checking out main, pulling the latest changes, and then creating a new branch feels unnecessarily verbose. Let's explore how to make this process more efficient and developer-friendly.

The Traditional Approach and Its Pain Points

Most developers are familiar with this common pattern:

git checkout main
git pull 
git checkout -b new-feature-branch

While this approach works, it has several drawbacks that can slow down your development workflow. You're forced to switch contexts by checking out the main branch first, potentially interrupting your current work. If your local main branch has uncommitted changes, you might encounter conflicts or need to stash your work. Additionally, this three-step process simply takes more time and mental overhead than necessary.

The Modern Solution: Direct Branch Creation from Remote

The most elegant solution is to create your new branch directly from the remote main branch without switching to it locally:

git checkout -b new-feature-branch origin/main

This single command accomplishes everything the traditional three-step process does, but more efficiently. It creates a new branch called new-feature-branch based on the latest state of origin/main and immediately switches to it. The beauty of this approach is that it works with the remote reference directly, ensuring you always start with the most up-to-date code.

Alternative Approaches for Different Scenarios

Using Git Switch for Modern Workflows

If you're using a newer version of Git, the git switch command offers a more intuitive syntax:

git switch -c new-feature-branch origin/main

The git switch command was introduced to make branch operations more explicit and user-friendly. The -c flag creates a new branch, similar to checkout -b, but with clearer intent.

The Fetch-First Approach

For teams working in fast-moving environments where the remote repository changes frequently, you might want to ensure you have the absolute latest changes:

git fetch origin
git checkout -b new-feature-branch origin/main

This two-step process first fetches all the latest changes from the remote repository, then creates your branch from the most current state. While it's one extra command compared to the direct approach, it guarantees you're working with the freshest possible codebase.

Understanding Why These Methods Work Better

These streamlined approaches offer several advantages over the traditional workflow:

Reduced Context Switching: You don't need to leave your current branch to create a new one, which is particularly valuable when you're in the middle of debugging or reviewing code.

Cleaner Local Repository: Your local main branch remains untouched, avoiding potential merge conflicts or the need to stash uncommitted work.

Faster Execution: Reducing three commands to one or two saves time, especially when repeated multiple times throughout the day.

Remote-First Thinking: By working directly with remote references, you develop better habits around distributed version control and reduce the likelihood of working with stale local branches.

When to Use Each Approach

The choice between these methods depends on your specific workflow and team practices:

Use git checkout -b new-feature-branch origin/main for most scenarios where you want maximum efficiency
Use git switch -c new-feature-branch origin/main if your team has adopted modern Git practices and prefers explicit command semantics
Use the fetch-first approach in high-velocity environments where remote changes happen frequently

How to Automatically Disable Bluetooth and WiFi on MacBook Sleep

Shawon Saha — Sat, 22 Feb 2025 17:54:09 +0000

Are you tired of your MacBook maintaining Bluetooth and WiFi connections when it's supposed to be sleeping? This can lead to unnecessary battery drain and potential security risks. In this guide, we'll walk you through a simple yet effective solution using SleepWatcher to automatically disable both Bluetooth and WiFi when your MacBook goes to sleep.

Why Disable Bluetooth and WiFi on Sleep?

When your MacBook goes to sleep, it often keeps Bluetooth and WiFi active. While this is convenient for quick wake-ups or maintaining network connections, it can:

Drain your battery unnecessarily.
Keep your Mac connected to devices or networks when it's not in use.
Pose potential security risks by leaving your wireless interfaces active.

By disabling both Bluetooth and WiFi during sleep, you can conserve battery life and improve security.

Step 1: Install SleepWatcher and Blueutil

To get started, you'll need two tools: SleepWatcher (to run scripts when your Mac sleeps or wakes) and Blueutil (to control Bluetooth via the command line).

Open Terminal.
Install both tools using Homebrew:

   brew install sleepwatcher blueutil

This will install SleepWatcher and Blueutil into the /opt/homebrew directory.

Step 2: Create Sleep and Wake Scripts

SleepWatcher works by running custom scripts when your Mac sleeps or wakes. You'll create two scripts: one for sleep (to disable Bluetooth and WiFi) and one for wake (to re-enable them).

Create the sleep script using Terminal in ~home directory:

echo "/opt/homebrew/bin/blueutil -p 0" > ~/.sleep
echo "networksetup -setairportpower Wi-Fi off" >> ~/.sleep

Create the wake script using Terminal in ~home directory:

echo "/opt/homebrew/bin/blueutil -p 1" > ~/.wakeup
echo "networksetup -setairportpower Wi-Fi on" >> ~/.wakeup

Make these scripts executable:

chmod +x ~/.sleep ~/.wakeup

Step 3: Configure SleepWatcher

Start the SleepWatcher service:

brew services start sleepwatcher

Step 4: Make SleepWatcher Start at Login

To ensure SleepWatcher runs automatically whenever you log in, follow these steps:

Option 1: Use Login Items & Extensions (GUI Method)

Open System Settings on your Mac.
Go to General > Login Items & Extensions.
Under Login Items, click the + button.
Navigate to /opt/homebrew/Cellar/sleepwatcher/[version]/sbin/ (replace [version] with the installed version of SleepWatcher, e.g., 2.2.1).
Select sleepwatcher and click Add.

This will add SleepWatcher as a login item so it starts automatically whenever you log in.

Testing Your Setup

To ensure everything is working correctly:

Close your MacBook lid
Wait a few seconds
Open the lid

Both Bluetooth and WiFi should turn off when the lid is closed and turn back on when opened.

Troubleshooting

If you encounter any issues:

Make sure SleepWatcher is running: brew services list
Check your script permissions: ls -l ~/.sleep ~/.wakeup
Review system logs for any error messages

Conclusion

By following this guide, you've successfully automated the process of disabling Bluetooth and WiFi whenever your MacBook goes to sleep—and re-enabling them upon waking up! With SleepWatcher configured to start at login, you can enjoy improved battery life, enhanced security, and peace of mind knowing that your wireless interfaces are inactive when not in use.

Remember, you can always modify the sleep and wake scripts to include additional actions or fine-tune the behavior to suit your specific needs.

Happy automating! 😊

How to Manually Approve LuLu Network Extension on Mac

Shawon Saha — Sun, 29 Dec 2024 08:59:29 +0000

If you're using LuLu, a popular open-source firewall for macOS, you might encounter a message stating that extensions must be manually approved via the Security and Privacy settings. This guide will walk you through the steps to approve the LuLu network extension, ensuring that your firewall is fully operational and protecting your system.

Why You Need to Approve Extensions

macOS has strict security measures in place to prevent unauthorized software from modifying system settings. As a result, certain applications, like LuLu, require manual approval for their network extensions. This process helps maintain the integrity of your system while allowing trusted applications to function properly.

Step-by-Step Guide to Approve LuLu's Network Extension

Follow these simple steps to manually approve the LuLu network extension on your Mac:

Step 1: Open System Settings

Click on the Apple menu in the top-left corner of your screen.
Select System Settings from the dropdown menu.

Step 2: Navigate to Login Items & Extensions

In the System Settings sidebar, click on General.
Scroll down and select Login Items & Extensions.

Step 3: Locate Network Extensions

Under the Extensions section, find Network Extensions.
Click on the (i) button next to it for more details.

Step 4: Enable LuLu

If LuLu is listed among the network extensions, toggle it on.
If you do not see LuLu, try running another application that uses network extensions (like DNSMonitor) from the Terminal to trigger the approval prompt.

Step 5: Authenticate Changes

You may be prompted to enter your administrator password to authenticate these changes.
Once authenticated, your settings should be updated.

Troubleshooting Tips

If you do not see LuLu or any related prompts in the Security & Privacy settings, ensure that you have installed the latest version of LuLu.
Check if your macOS version supports LuLu; compatibility issues may prevent it from appearing.
In some cases, reinstalling LuLu may help trigger the necessary approval prompts.

Conclusion

Manually approving network extensions like LuLu is an essential step in ensuring that your firewall functions correctly on macOS. By following these steps, you can enhance your system's security and maintain control over your network traffic. If you have any further questions or run into issues, feel free to reach out for assistance!

Happy browsing!

Fixing GRUB: A Guide to Dual Booting Windows and Linux on UEFI GPT Systems

Shawon Saha — Sun, 03 Nov 2024 09:52:56 +0000

Dual booting Windows and Linux can be a great way to enjoy the best of both operating systems. However, issues can arise, particularly with the GRUB bootloader, which is essential for selecting which OS to boot into. If you find that your computer boots directly into Windows without showing the GRUB menu, you may need to fix GRUB. This blog post summarizes a helpful video guide on how to resolve this issue using Ubuntu installation media.

Understanding the Problem

When you install both Windows and Linux on a single hard drive, the GRUB bootloader should allow you to choose between the two operating systems at startup. However, sometimes GRUB can go missing or fail to display due to various reasons, such as system updates or changes in boot order. In this case, the computer boots straight into Windows, leaving you unable to access your Linux installation.

Step-by-Step Guide to Fixing GRUB

1. Boot into Ubuntu Installation Media

To begin fixing GRUB, you will need to boot from an Ubuntu installation media (USB or DVD). You can download the latest Ubuntu ISO from the official website. Once you have created your installation media:

Insert it into your computer and restart.
Select "Try Ubuntu" when prompted.

2. Open Terminal and Mount Partitions

Once you're in the live session of Ubuntu:

Open a terminal window by searching for "Terminal" in the applications menu.
First, you need to identify your partitions by running:

  sudo fdisk -l

This command will display your drive structure. You’ll typically see partitions like /dev/sda1 for EFI and /dev/sda5 for your Linux filesystem.

Next, mount the necessary partitions. For example:

  sudo mount /dev/sda1 /mnt
  sudo mount /dev/sda5 /mnt/ubuntu

This mounts your EFI partition and your Linux filesystem so that you can make changes.

3. Install and Update GRUB

Now that your partitions are mounted, you can install GRUB:

Change root into your mounted directory:

  sudo chroot /mnt

Install GRUB on your disk (usually /dev/sda):

  grub-install /dev/sda

If you encounter a warning about EFI variables not being set, ensure that you've correctly mounted the EFI partition.

After successfully installing GRUB, update it with:

  update-grub

This command scans for installed operating systems and generates a new configuration file for GRUB.

4. Verify Boot Entries

To ensure that everything is set up correctly, check the EFI boot manager:

efibootmgr -v

You should see an entry for Ubuntu in the boot order. If it’s not there or not prioritized correctly, you may need to adjust it using efibootmgr.

5. Reboot and Test

After completing these steps:

Exit the terminal and reboot your computer.
Remove the installation media when prompted.

Upon rebooting, you should see the GRUB menu allowing you to select either Ubuntu or Windows.

Conclusion

Fixing GRUB in a dual-boot setup with Windows and Linux can seem daunting, but following these steps can help restore access to your Linux installation. By using Ubuntu installation media and executing a few commands in the terminal, you can resolve boot issues and enjoy seamless switching between operating systems.

For detailed visual guidance, check out the video linked above. Happy dual booting!

How to Fix "LuLu's Network Extension Is Not Running" on Mac

Shawon Saha — Sat, 02 Nov 2024 07:37:23 +0000

If you're encountering the message

LuLu's Network Extension Is Not Running. Extensions must be manually approved via Security & Privacy System Preferences

when trying to open LuLu on your Mac, don't worry! This guide will walk you through the steps to manually approve the extension via System Preferences.

What is LuLu?

LuLu is a free, open-source firewall for macOS that aims to block unauthorized outgoing connections. It uses a network extension to monitor and control these connections, which sometimes requires manual approval from the user.

Steps to Approve LuLu's Network Extension

Follow these steps to enable LuLu's network extension:

Open System Settings:
- Click on the Apple menu in the top-left corner of your screen and select System Settings.
Navigate to Login Items & Extensions:
- In the System Settings sidebar, click on General.
- Scroll down and select Login Items & Extensions.
Locate Network Extensions:
- Under the Extensions section, find Network Extensions.
- Click on the (i) button next to it to access more details.
Enable LuLu:
- If LuLu is listed, toggle it on. If it does not appear, you may need to run another application that uses network extensions (like DNSMonitor) from the Terminal to trigger the approval prompt.
Authenticate Changes:
- You might be prompted to enter your administrator password to authorize changes.
Restart LuLu:
- After enabling the extension, restart LuLu to ensure it is running properly.

Additional Troubleshooting

If you do not see LuLu in the Network Extensions list, consider running DNSMonitor as a workaround. Here’s how:

Download DNSMonitor from GitHub.
Open Terminal and execute the following commands:


bash
   cd /Applications/DNSMonitor.app/Contents/MacOS/
   ./DNSMonitor

Claude prompting guide - General tips for effective prompting

Shawon Saha — Wed, 30 Oct 2024 05:19:16 +0000

1. Be clear and specific

Clearly state your task or question at the beginning of your message.
Provide context and details to help Claude understand your needs.
Break complex tasks into smaller, manageable steps.

Bad prompt:

"Help me with a presentation."

Good prompt:

"I need help creating a 10-slide presentation for our quarterly sales meeting. The presentation should cover our Q2 sales performance, top-selling products, and sales targets for Q3. Please provide an outline with key points for each slide."

Why it's better: The good prompt provides specific details about the task, including the number of slides, the purpose of the presentation, and the key topics to be covered.

2. Use examples

Provide examples of the kind of output you're looking for.
If you want a specific format or style, show Claude an example.

Bad prompt:

"Write a professional email."

Good prompt:

"I need to write a professional email to a client about a project delay. Here's a similar email I've sent before:

'Dear [Client],
I hope this email finds you well. I wanted to update you on the progress of [Project Name]. Unfortunately, we've encountered an unexpected issue that will delay our completion date by approximately two weeks. We're working diligently to resolve this and will keep you updated on our progress.
Please let me know if you have any questions or concerns.
Best regards,
[Your Name]'

Help me draft a new email following a similar tone and structure, but for our current situation where we're delayed by a month due to supply chain issues."

Why it's better: The good prompt provides a concrete example of the desired style and tone, giving Claude a clear reference point for the new email.

3. Encourage thinking

For complex tasks, ask Claude to "think step-by-step" or "explain your reasoning."
This can lead to more accurate and detailed responses.

Bad prompt:

"How can I improve team productivity?"

Good prompt:

"I'm looking to improve my team's productivity. Think through this step-by-step, considering the following factors:

Current productivity blockers (e.g., too many meetings, unclear priorities)
Potential solutions (e.g., time management techniques, project management tools)
Implementation challenges
Methods to measure improvement

For each step, please provide a brief explanation of your reasoning. Then summarize your ideas at the end."

Why it's better: The good prompt asks Claude to think through the problem systematically, providing a guided structure for the response and asking for explanations of the reasoning process. It also prompts Claude to create a summary at the end for easier reading.

4. Iterative refinement

If Claude's first response isn't quite right, ask for clarifications or modifications.
You can always say "That's close, but can you adjust X to be more like Y?"

Bad prompt:

"Make it better."

Good prompt:

"That’s a good start, but please refine it further. Make the following adjustments:

Make the tone more casual and friendly
Add a specific example of how our product has helped a customer
Shorten the second paragraph to focus more on the benefits rather than the features"

Why it's better: The good prompt provides specific feedback and clear instructions for improvements, allowing Claude to make targeted adjustments instead of just relying on Claude’s innate sense of what “better” might be — which is likely different from the user’s definition!

5. Leverage Claude's knowledge

Claude has broad knowledge across many fields. Don't hesitate to ask for explanations or background information
Be sure to include relevant context and details so that Claude’s response is maximally targeted to be helpful

Bad prompt:

"What is marketing? How do I do it?"

Good prompt:

"I'm developing a marketing strategy for a new eco-friendly cleaning product line. Can you provide an overview of current trends in green marketing? Please include:

Key messaging strategies that resonate with environmentally conscious consumers
Effective channels for reaching this audience
Examples of successful green marketing campaigns from the past year
Potential pitfalls to avoid (e.g., greenwashing accusations)

This information will help me shape our marketing approach."

Why it's better: The good prompt asks for specific, contextually relevant information that leverages Claude's broad knowledge base. It provides context for how the information will be used, which helps Claude frame its answer in the most relevant way.

6. Use role-playing

Ask Claude to adopt a specific role or perspective when responding.

Bad prompt:

"Help me prepare for a negotiation."

Good prompt:

"You are a fabric supplier for my backpack manufacturing company. I'm preparing for a negotiation with this supplier to reduce prices by 10%. As the supplier, please provide:

Three potential objections to our request for a price reduction
For each objection, suggest a counterargument from my perspective
Two alternative proposals the supplier might offer instead of a straight price cut

Then, switch roles and provide advice on how I, as the buyer, can best approach this negotiation to achieve our goal."

Why it's better: This prompt uses role-playing to explore multiple perspectives of the negotiation, providing a more comprehensive preparation. Role-playing also encourages Claude to more readily adopt the nuances of specific perspectives, increasing the intelligence and performance of Claude’s response.

Task-specific tips and examples

Content Creation

Specify your audience
- Tell Claude who the content is for.

Bad prompt:

"Write something about cybersecurity."

Good prompt:

"I need to write a blog post about cybersecurity best practices for small business owners. The audience is not very tech-savvy, so the content should be:

Easy to understand, avoiding technical jargon where possible
Practical, with actionable tips they can implement quickly
Engaging and slightly humorous to keep their interest

Please provide an outline for a 1000-word blog post that covers the top 5 cybersecurity practices these business owners should adopt."

Why it's better: The good prompt specifies the audience, desired tone, and key characteristics of the content, giving Claude clear guidelines for creating appropriate and effective output.

Define the tone and style
- Describe the desired tone.
- If you have a style guide, mention key points from it.

Bad prompt:

"Write a product description."

Good prompt:

"Please help me write a product description for our new ergonomic office chair. Use a professional but engaging tone. Our brand voice is friendly, innovative, and health-conscious. The description should:

Highlight the chair's key ergonomic features
Explain how these features benefit the user's health and productivity
Include a brief mention of the sustainable materials used
End with a call-to-action encouraging readers to try the chair

Aim for about 200 words."

Why it's better: This prompt provides clear guidance on the tone, style, and specific elements to include in the product description.

Define output structure
- Provide a basic outline or list of points you want covered.

Bad prompt:

"Create a presentation on our company results."

Good prompt:

"I need to create a presentation on our Q2 results. Structure this with the following sections:

Overview
Sales Performance
Customer Acquisition
Challenges
Q3 Outlook

For each section, suggest 3-4 key points to cover, based on typical business presentations. Also, recommend one type of data visualization (e.g., graph, chart) that would be effective for each section."

Why it's better: This prompt provides a clear structure and asks for specific elements (key points and data visualizations) for each section.

Document summary and Q&A

Be specific about what you want
- Ask for a summary of specific aspects or sections of the document.
- Frame your questions clearly and directly.
- Be sure to specify what kind of summary (output structure, content type) you want
Use the document names
- Refer to attached documents by name.
Ask for citations
- Request that Claude cites specific parts of the document in its answers.

Here is an example that combines all three of the above techniques:

Bad prompt:

"Summarize this report for me."

Good prompt:

"I've attached a 50-page market research report called 'Tech Industry Trends 2023'. Can you provide a 2-paragraph summary focusing on AI and machine learning trends? Then, please answer these questions:

What are the top 3 AI applications in business for this year?
How is machine learning impacting job roles in the tech industry?
What potential risks or challenges does the report mention regarding AI adoption?

Please cite specific sections or page numbers when answering these questions."

Why it's better: This prompt specifies the exact focus of the summary, provides specific questions, and asks for citations, ensuring a more targeted and useful response. It also indicates the ideal summary output structure, such as limiting the response to 2 paragraphs.

Data analysis and visualization

Specify the desired format
- Clearly describe the format you want the data in.

Bad prompt:

"Analyze our sales data."

Good prompt:

"I've attached a spreadsheet called 'Sales Data 2023'. Can you analyze this data and present the key findings in the following format:

Executive Summary (2-3 sentences)
Key Metrics:
- Total sales for each quarter
- Top-performing product category
- Highest growth region
Trends:
- List 3 notable trends, each with a brief explanation
Recommendations:
- Provide 3 data-driven recommendations, each with a brief rationale

After the analysis, suggest three types of data visualizations that would effectively communicate these findings."

Why it's better: This prompt provides a clear structure for the analysis, specifies key metrics to focus on, and asks for recommendations and visualization suggestions for further formatting.

Brainstorming

Use Claude to generate ideas by asking for a list of possibilities or alternatives.
- Be specific about what topics you want Claude to cover in its brainstorming

Bad prompt:

"Give me some team-building ideas."

Good prompt:

"We need to come up with team-building activities for our remote team of 20 people. Can you help me brainstorm by:

Suggesting 10 virtual team-building activities that promote collaboration
For each activity, briefly explain how it fosters teamwork
Indicate which activities are best for: a) Ice-breakers b) Improving communication c) Problem-solving skills
Suggest one low-cost option and one premium option."

Why it's better: This prompt provides specific parameters for the brainstorming session, including the number of ideas, type of activities, and additional categorization, resulting in a more structured and useful output.

Request responses in specific formats like bullet points, numbered lists, or tables for easier reading.

Bad Prompt:

"Compare project management software options."

Good Prompt:

"We're considering three different project management software options: Asana, Trello, and Microsoft Project. Can you compare these in a table format using the following criteria:

Key Features
Ease of Use
Scalability
Pricing (include specific plans if possible)
Integration capabilities
Best suited for (e.g., small teams, enterprise, specific industries)"

Why it's better: This prompt requests a specific structure (table) for the comparison, provides clear criteria, making the information easy to understand and apply.

Troubleshooting, minimizing hallucinations, and maximizing performance

Allow Claude to acknowledge uncertainty
- Tell Claude that it should say it doesn’t know if it doesn’t know. Ex. “If you're unsure about something, it's okay to admit it. Just say you don’t know.”
Break down complex tasks
- If a task seems too large and Claude is missing steps or not performing certain steps well, break it into smaller steps and work through them with Claude one message at a time.
Include all contextual information for new requests
- Claude doesn't retain information from previous conversations, so include all necessary context in each new conversation.

Example good vs. bad prompt examples

These are more examples that combine multiple prompting techniques to showcase the stark difference between ineffective and highly effective prompts.

Example 1: Marketing strategy development

Bad prompt:

"Help me create a marketing strategy."

Good prompt:

"As a senior marketing consultant, I need your help developing a comprehensive marketing strategy for our new eco-friendly smartphone accessory line. Our target audience is environmentally conscious millennials and Gen Z consumers. Please provide a detailed strategy that includes:

Market Analysis:
- Current trends in eco-friendly tech accessories
- 2-3 key competitors and their strategies
- Potential market size and growth projections
Target Audience Persona:
- Detailed description of our ideal customer
- Their pain points and how our products solve them
Marketing Mix:
- Product: Key features to highlight
- Price: Suggested pricing strategy with rationale
- Place: Recommended distribution channels
- Promotion: a) 5 marketing channels to focus on, with pros and cons for each b) 3 creative campaign ideas for launch
Content Strategy:
- 5 content themes that would resonate with our audience
- Suggested content types (e.g., blog posts, videos, infographics)
KPIs and Measurement:
- 5 key metrics to track
- Suggested tools for measuring these metrics

Please present this information in a structured format with headings and bullet points. Where relevant, explain your reasoning or provide brief examples.

After outlining the strategy, please identify any potential challenges or risks we should be aware of, and suggest mitigation strategies for each."

Why it's better: This prompt combines multiple techniques including role assignment, specific task breakdown, structured output request, brainstorming (for campaign ideas and content themes), and asking for explanations. It provides clear guidelines while allowing room for Claude's analysis and creativity.

Example 2: Financial report analysis

Bad prompt:

"Analyze this financial report."

Good prompt:

"I've attached our company's Q2 financial report titled 'Q2_2023_Financial_Report.pdf'. Act as a seasoned CFO and analyze this report and prepare a briefing for our board of directors. Please structure your analysis as follows:

Executive Summary (3-4 sentences highlighting key points)
Financial Performance Overview:
a) Revenue: Compare to previous quarter and same quarter last year
b) Profit margins: Gross and Net, with explanations for any significant changes
c) Cash flow: Highlight any concerns or positive developments
Key Performance Indicators:
- List our top 5 KPIs and their current status (Use a table format)
- For each KPI, provide a brief explanation of its significance and any notable trends
Segment Analysis:
- Break down performance by our three main business segments
- Identify the best and worst performing segments, with potential reasons for their performance
Balance Sheet Review:
- Highlight any significant changes in assets, liabilities, or equity
- Calculate and interpret key ratios (e.g., current ratio, debt-to-equity)
Forward-Looking Statements:
- Based on this data, provide 3 key predictions for Q3
- Suggest 2-3 strategic moves we should consider to improve our financial position
Risk Assessment:
- Identify 3 potential financial risks based on this report
- Propose mitigation strategies for each risk
Peer Comparison:
- Compare our performance to 2-3 key competitors (use publicly available data)
- Highlight areas where we're outperforming and areas for improvement

Please use charts or tables where appropriate to visualize data. For any assumptions or interpretations you make, please clearly state them and provide your reasoning.

After completing the analysis, please generate 5 potential questions that board members might ask about this report, along with suggested responses.

Finally, summarize this entire analysis into a single paragraph that I can use as an opening statement in the board meeting."

Why it's better: This prompt combines role-playing (as CFO), structured output, specific data analysis requests, predictive analysis, risk assessment, comparative analysis, and even anticipates follow-up questions. It provides a clear framework while encouraging deep analysis and strategic thinking.

Overcoming Upload Limits: A Guide for WordPress Developers Using MAMP

Shawon Saha — Sat, 26 Oct 2024 09:17:42 +0000

As a WordPress developer, you've likely encountered the frustrating "413 Request Entity Too Large" error or a similar message about exceeding upload limits. This issue often crops up when trying to upload large themes or plugins, and it can bring your workflow to a screeching halt. But fear not! In this post, we'll walk through the steps to increase your upload limits and get you back to building amazing websites.

Understanding the Problem

The root of this issue lies in the default settings of your server environment. Both NGINX (the web server) and PHP (the scripting language) have their own file size limits, which can be quite restrictive out of the box. When you try to upload a file that exceeds these limits, you'll encounter errors like:

"413 Request Entity Too Large" (from NGINX)
"POST Content-Length of X bytes exceeds the limit of Y bytes" (from PHP)

The Solution: Adjusting Server Configurations

To resolve this issue, we need to modify both NGINX and PHP configurations. Here's a step-by-step guide:

Step 1: Increase NGINX File Size Limit

Open your NGINX configuration file. In MAMP, it's typically located at:
/Applications/MAMP/conf/nginx/nginx.conf
Add the following line within the http block:

   client_max_body_size 64M;

This allows file uploads up to 64 megabytes. Adjust the value as needed.

Step 2: Modify PHP Settings

Locate your php.ini file. In MAMP, you'll find it at:
/Applications/MAMP/bin/php/phpX.X.XX/conf/php.ini
(Replace X.X.XX with your PHP version)
Find and modify these lines:

   upload_max_filesize = 64M
   post_max_size = 64M
   max_execution_time = 300

If these lines don't exist, add them. The max_execution_time setting allows for longer upload times.

Step 3: Increase WordPress Memory Limit

For an extra boost, you can increase WordPress's PHP memory limit:

Open your wp-config.php file.
Add this line:

   define('WP_MEMORY_LIMIT', '256M');

Wrapping Up

After making these changes, restart MAMP to apply the new settings. You should now be able to upload larger files without encountering those pesky size limit errors.

Remember:

Increasing these limits can be helpful for development purposes
Consider security and performance implications when setting up a production server
Always consult with your hosting provider or system administrator before making similar changes on a live site

Key Takeaways:

Modify NGINX configuration to increase client_max_body_size
Adjust PHP settings in php.ini for larger uploads and longer execution times
Optionally increase WordPress memory limit in wp-config.php

DEV Community: Shawon Saha

The "Windows Update Ate My Grub" Fix: A One-Line Lifesaver

The Magic Command

What does this actually do?

Step-by-Step Guide

"It didn't work!" (Troubleshooting)

Why does this happen?

How to Check the Number of Lines Changed in Your Current Git Branch Compared to Main

Why Check Lines of Diff?

Using Git to Check Line Differences

Getting More Detailed Line Counts

How to Disable Automatic Rearrangement of Desktops (Spaces) on Mac

What is Desktop (Spaces) Auto Rearrangement?

Why Disable Auto Rearrangement?

How to Disable Auto Rearrangement of Desktops on macOS

Additional Tips

Conclusion

How to Reset a Remote Git Repository to Match Your Local State: A Careful Approach

Step 1: Backup Your Current State

Step 2: Fetch Latest Changes from Remote

Step 3: Reset Your Local Branch to the Desired Commit

Step 4: Force Push to Overwrite Remote History

Important Warnings and Best Practices

Summary

How To Suppress Build Errors in Next.js with TypeScript

Suppressing TypeScript Build Errors in next.config.ts or next.config.mjs

Disabling Strict Type Checking in tsconfig.json

When and Why You Might Do This

Best Practices and Warnings

Conclusion

Streamlining Your Git Workflow: A Developer's Guide to Efficient Branch Creation

The Traditional Approach and Its Pain Points

The Modern Solution: Direct Branch Creation from Remote

Alternative Approaches for Different Scenarios

Using Git Switch for Modern Workflows

The Fetch-First Approach

Understanding Why These Methods Work Better

When to Use Each Approach

How to Automatically Disable Bluetooth and WiFi on MacBook Sleep

Why Disable Bluetooth and WiFi on Sleep?

Step 1: Install SleepWatcher and Blueutil

Step 2: Create Sleep and Wake Scripts

Step 3: Configure SleepWatcher

Step 4: Make SleepWatcher Start at Login

Option 1: Use Login Items & Extensions (GUI Method)

Testing Your Setup

Troubleshooting

Conclusion

How to Manually Approve LuLu Network Extension on Mac

Why You Need to Approve Extensions

Step-by-Step Guide to Approve LuLu's Network Extension

Step 1: Open System Settings

Step 2: Navigate to Login Items & Extensions

Step 3: Locate Network Extensions

Step 4: Enable LuLu

Step 5: Authenticate Changes

Troubleshooting Tips

Conclusion

Fixing GRUB: A Guide to Dual Booting Windows and Linux on UEFI GPT Systems

Understanding the Problem

Step-by-Step Guide to Fixing GRUB

1. Boot into Ubuntu Installation Media

2. Open Terminal and Mount Partitions

3. Install and Update GRUB

4. Verify Boot Entries

5. Reboot and Test

Conclusion

How to Fix "LuLu's Network Extension Is Not Running" on Mac

What is LuLu?

Steps to Approve LuLu's Network Extension

Additional Troubleshooting

Claude prompting guide - General tips for effective prompting

1. Be clear and specific

2. Use examples

3. Encourage thinking

4. Iterative refinement

5. Leverage Claude's knowledge

6. Use role-playing

Task-specific tips and examples

Content Creation

Suppressing TypeScript Build Errors in `next.config.ts` or `next.config.mjs`

Disabling Strict Type Checking in `tsconfig.json`