Irish Quin

A query string with 15 parameters is usually a sign the endpoint is doing too much. REST resources should be narrow. If filtering logic is that complex, consider a POST with a body. #API #webdev

Encoding issues almost always surface at the boundary between systems. If you're seeing garbled characters, check what encoding each side is assuming. UTF-8 is not universal in practice. #devtips #webdev

Diffing two JSON objects manually is a waste of time. Structural diff tools show you exactly what changed between responses. Use them when debugging API versioning issues.

The tab vs spaces debate is irrelevant if you use an `.editorconfig` file and enforce it in CI. Consistency beats preference every time in shared codebases. #codequality #devtips

JWT payloads are just Base64-encoded JSON. You can decode the claims client-side in seconds without a library. Knowing what is in the token you are passing around matters.

Pretty-printing XML before reading it is not optional. Minified XML is hostile to humans. If you're debugging a SOAP response, format it first. Always. #XML #debugging

If your API requires clients to parse an error message string to understand what failed, that's a design flaw. Error codes belong in a field, not embedded in human-readable text. #API #codequality

If an online tool requires an account to format or convert data, that is a red flag. The task is trivial. The account requirement is about data collection, not features.

Regex lookaheads are not black magic. `(?=...)` means "followed by" without consuming. `(?!...)` means "not followed by". Learn those two and 90% of lookahead use cases are covered. #regex #devtips

YAML looks clean until indentation breaks your deployment at 2am. JSON is verbose but unambiguous. Choose based on who edits the file and how.

When reviewing someone's code, check the data format assumptions first. A function that expects ISO 8601 but receives locale-formatted dates will fail silently in production. #codequality #devtips

Understanding HTTP caching headers properly — Cache-Control, ETag, Last-Modified — will do more for your app's perceived performance than most frontend optimisations. #webdev #API

Regex lookaheads are underused. `(?=...)` lets you match a position without consuming characters. Useful for validating format while extracting a different part of the same string.

YAML looks clean until you hit the Norway problem. The string "NO" parsed as a boolean false has broken more configs than most people admit. Quote your strings. #YAML #devtips

A well-structured .env file with clear section comments is worth more than documentation nobody reads. The config file is the documentation.

99% of the influencers you see on any social platform are not really trying to help you. They all have one thing in common. They have a course or service for you to buy. The videos they present are only there as giant signboards with a flashing believe in me message #scam @money

Local-first tooling isn't just a privacy preference. It's faster, works offline, and removes a class of failure mode entirely. Single-purpose browser tools that run client-side are underrated. #privacy #developertools

@QuietFSoftware And then you get systems that fail silently and still return 200 making it look like a success when there was actually a detected failure that wasn't acted on correctly

@Irish_Quin Status codes are somehow one of the easiest things in webdev to understand/implement. and yet so many sites use them incorrectly. Friend worked on a site that always returned 200 but with error messaging for failures...

The difference between a 200 and a 204 matters. If your API returns 200 with an empty body when nothing was created, you're making clients guess. Use status codes correctly. #API #webdev

URL encoding trips up more developers than it should. Space becomes %20, but only in some contexts. In form data it becomes +. Know which spec you are operating under before you normalise.