DEV Community: Zaphod Dev

Escape quotes correctly when using psql via docker in bash

Zaphod Dev — Tue, 14 Apr 2026 16:07:26 +0000

docker compose exec site bash -c 'PGPASSWORD=***** psql -Ufoo -d bar \
  -h example.com -x -c "select qux, date(xyzzy) from tabley          \
  where field in(1, 2, 3) and that_time > '"'"'2024-11-18'"'"'       \
  order by that_time;"'

Quoteception

'"'"' is the Quoteception operator.

When used in the middle of a single quoted string, it:

' Ends the current single quoted string
" Starts a new double quoted string
' That contains one single quote
" Ends the double quoted string
' Re-starts the next single quoted string

Example usage:

echo 'Embedded single quote is here: '"'"' did you see it?'

Outputs:

Embedded single quote is here:  '  did you see it?

Disable keyboard shortcuts for Jira and Confluence

Zaphod Dev — Tue, 14 Apr 2026 15:46:36 +0000

Keyboard "shortcuts" are enabled by default for Atlassian products, and they can be extremely annoying.

Quick way disable keyboard shortcuts for Jira

Type ? (Question mark)
Toggle the switch

Another way to enable/disable keyboard shortcuts for Jira

Open a ticket, for example https://YOURCOMPANY.atlassian.net/browse/FOO-1234
Click the three dots ... in the top right of the page (or type Ctrl-K) to open the command palette
Type "keyboard" to search for the keyboard shortcuts page, click it
Toggle the "Keyboard shortcuts are enabled" switch in the top right

To disable keyboard shortcuts for Confluence

Go to https://YOURCOMPANY.atlassian.net/wiki/users/viewmysettings.action
Click Edit
Uncheck "Keyboard Shortcuts | Enable"

How to get past Sub::Defer in the Perl debugger

Zaphod Dev — Tue, 14 Apr 2026 15:42:35 +0000

YOU ARE IN A MAZE OF TWISTY LITTLE PASSAGES, ALL ALIKE

perl -d professional_adventure_2024.pl

Sub::Defer::CODE(0x8ab8938)(/epsi/perlbrew/perls/perl-5.16.3/lib/perl5/Sub/Defer.pm:55):
55:         $undeferred ||= undefer_sub($deferred_info->[3]);
auto(-1)  DB<2> v
52:       my $undeferred;
53:       my $deferred_info;
54        my $deferred = sub {
55==>       $undeferred ||= undefer_sub($deferred_info->[3]);
56:         goto &$undeferred;
57:       };
58:       $deferred_info = [ $target, $maker, \$undeferred, $deferred ];
59:       weaken($deferred_info->[3]);
60:       weaken($DEFERRED{$deferred} = $deferred_info);
61:       _install_coderef($target => $deferred) if defined $target;
  DB<2> n

Walkthrough:

How to review code changes

Zaphod Dev — Tue, 14 Apr 2026 11:20:42 +0000

A checklist that works:

Basics

Has the author finished making changes?
Have you read the entire summary/description?
Does the PR satisfy all the acceptance criteria?
Have AI and/or junior developers reviewed it first?
Are there any unnecessary changes?
Are all the changes covered by automated or manual tests?
Do the automated tests all pass? Check the logs afterwards: Do the messages look right?

Missing requirements

If anything is discovered at this point, it's too late. But raise it anyway.

Is the feature performant?
Do the changes affect overall performance?
Are there metrics?
Does the feature need to be communicated to users?
Is it secure?
Does it scale?
Is the UX good?
Is it maintainable?

Testing

First, run the latest release to observe baseline behaviour. Make detailed notes if necessary, including logs and screenshots where appropriate, to help communicate all this to the team later.
Observe system behaviour, paying close attention to:
- Any unexpected warnings or errors, or unexplained behaviour (no matter how harmless it seems).
- All relevant application logs
- Browser console
You may need to account for differences between your dev environment and production, for example:
- Mounted network storage
- Browser ad-blockers/proxies
- Amount of memory/storage/processing power available
Sanity test the changes. Try to break it. Does everything work as expected? Does it raise any questions in your mind?
Check the logs again. Do all the messages look right?
Are there any new non-critical warnings? (don't ignore them)
Are there any gaps in the automated or manual testing?

More things

Think through the flow with your human brain and apply Murphy's Law.
Ask AI specifically "review this code/test thoroughly, considering everything that could possibly go wrong".

Gotchas

Avoid gold plating / nit picking / bikeshedding
Don't assume it will work. Assume it won't and prove otherwise.

AI Prompts

Zaphod Dev — Tue, 24 Feb 2026 10:09:17 +0000

Rovo

I'm ________ and ________ happened.
Search the whole company, restricted to _____ Jira project, _____ confluence space, and ______ github repo.
Answer my question: ________
Reply very concisely and abruptly, with no background information or definitions <--- this doesn't fully work with Rovo!

Copilot

You're an expert __________ with comprehensive knowledge of ________.
Help me ______.
I already know ______.
I want you to ________.

I need you to reason step by step and explain your thought process internally before giving the final answer.
Think through trade-offs before deciding.
Perform internal reasoning before answering.
Provide the final output only after complete reasoning.

Gemini

As of 22nd January 2026, ____________?

Answer Yes or No, with sources.
Do not rely on memory, verify against current official docs.
If you are not sure, say 'unknown' instead of guessing.
State whether this comes from official docs, community reports, or inference.
Don't use markdown tables, they don't render in the android messages app
Answer in two paragraphs with short, simple sentences. Disable clickbait headings option.

[critical thinking]

I need you to reason step by step and explain your thought process internally before giving the final answer.
Think through trade-offs before deciding.
Perform internal reasoning before answering.
Provide the final output only after complete reasoning.
Do not rely on memory, verify against actual content.
If you are not sure, say 'unknown' instead of guessing.
State whether this comes from official docs, community reports, or inference.

dev.to image generator

Striking bold solid lines, minimal colours, not too many details (poster-like to be seen at a distance).
The text _____ and then ____ on a new line in a weird, amusing bulbous font.
Do not use the 80s synthwave aesthetic at all. No random floating objects.