After REST: Trying Out GraphQL
While solving a real over-fetching problem with GraphQL, I weigh where REST is still sufficient and where GraphQL actually makes sense.
Blog
My hands-on development journal: PHP and Laravel, Go, JavaScript and TypeScript, developer tools and career. Architecture writing lives in Engineering. (Page 10/17)
While solving a real over-fetching problem with GraphQL, I weigh where REST is still sufficient and where GraphQL actually makes sense.
A practical look at PHP type conversion and coercion: gettype, settype, var_dump, and why strict_types belongs in every file.
I explain the syntax and structural differences that turned test writing from a chore into a habit when moving from PHPUnit to Pest.
A practical comparison of MySQL storage engines: the differences between InnoDB and MyISAM, their trade-offs, and which one to choose.
I compare the visibility problem that client-side rendering creates for search engines and evaluate server-side rendering alternatives.
Building reusable, type-safe abstractions with TypeScript generics: how type inference and extends constraints work, and when a union fits better.
How Laravel Octane removes per-request bootstrap overhead with a warm process, and what it costs: state leaking between requests and Swoole requirements.
A practical approach to error handling as a Go language idiom: the error value, wrapping, custom error types and a PHP developer's adjustment period.
How we represent fixed value sets until PHP 8.1 brings native enums: class constants, a package and backed classes, and the trade-offs of each.
How binding API error responses to one consistent contract simplifies client development and debugging: structure, codes, versioning and limits.
How to write more testable and maintainable code by moving business logic out of controllers and into single-purpose action classes.
Why switching from a Webpack-based dev environment to Vite shortens the feedback loop, how Vite works differently, and when I would recommend migrating.