Pinned Tweet
Spent way too long obsessing over micro-interactions on my new portfolio. Worth every hour. yafetport.vercel.app
Solid baseline on SQL injection... Although telling people to just "use an ORM" and ask their agent to audit itself misses the traps vibe coded search bars actually fall into
does your vibecoded app have a search bar? ask your agent:
"is user input ever put straight into a database query?"
if yes, someone can type a few characters and read or delete your whole database..
fix: use parameterized queries or your ORM, never glue user text into SQL!
1
6
LLMs routinely reach for ORM escape hatches like $queryRawUnsafe, interpolate dynamic ORDER BY column names, which bind parameters can't protect, so you need strict allowlists.
1
5
Plus, don't ask the agent that wrote the bug to audit it, grep for raw queries or run a static scanner like periderm.vercel.app/
No... In standard SQL's three valued logic, NULL represents an unknown state rather than a concrete value, so salary = NULL always evaluates to UNKNOWN (never TRUE) and silently returns zero rows, but salary IS NULL explicitly checks for the absence of a value...
SELECT * FROM users WHERE salary = NULL;
SELECT * FROM users WHERE salary IS NULL;
Are both these queries same?
1
1
Japheth Jerry retweeted
Just default to returning 429 Too Many Requests with a 'Retry After' header right at the edge or API gateway via a token bucket rate limiter. Because failing fast sheds load cheaply without holding sockets and worker threads open.
Japheth Jerry retweeted
Nope, React is a JavaScript library for building user interfaces, while JavaScript (or TypeScript) is the actual programming language underneath.
Nope, React is a JavaScript library for building user interfaces, while JavaScript (or TypeScript) is the actual programming language underneath.
Just default to returning 429 Too Many Requests with a 'Retry After' header right at the edge or API gateway via a token bucket rate limiter. Because failing fast sheds load cheaply without holding sockets and worker threads open.
And intentionally slowing down requests usually exhausts your own connection pool and turns a noisy user into a self-inflicted DoS.
1
1
3
Japheth Jerry retweeted
All in favour of me building a model trained on the entirety of Stack Overflow, say aye
Japheth Jerry retweeted
Middle school algebra in a SELECT statement 😂
The math gives $x = 7$...
SQL doesn't solve equations, the query only returns 7 if 7 actually exists in the numbers table otherwise it returns an empty set, or multiple rows if there are duplicates...
Japheth Jerry retweeted
Node.js, and i'm not sorry...
Startups overwhelmingly fail from slow iteration and empty runways long before hitting a runtime ceiling, and sharing TypeScript schemas, types, and engineers across your backend, web, and mobile apps eliminates the context-switching tax...
Japheth Jerry retweeted
To avoid this enforce server side object level authorization on EVERY query alongside authentication.
Scope every lookup directly to the verified session's user or tenant ID, such as WHERE id = :invoiceId AND user_id = :sessionUserId, and back it up with database-level (RLS)













