Engineer at heart, found working on products, projects, microservices & APIs (REST, GraphQL, SOAP) in Node.js (ExpressJS, Koa, NextJS, Serverless) or PHP (CodeIgniter, Symphony, Wordpress), familiar with relational databases (MySQL,Postgres), document-driven databases (DynamoDB, MongoDB, RethinkDB, Elasticsearch), templating (React, Vue.js, Handlebars, Nunjucks, Jekyll, Liquid), unit testing with code-coverage (Vitest, Mocha, Istanbul NYC, PHPUnit), integration testing (Playwright, Cypress) & devops (dedicated servers, Docker, Kubernetes, AWS, GCP, Azure, Rackspace).
So it's finally happened. I've invested in a Steamdeck. After months of (internal) debating between this & a Switch 2, the sale finally pushed me off the fence. Here's some first thoughts I've had around the 'Deck, and what happens next.
(DHH) Google will eventually kill every single service you care about, if they can't find a way to directly monetize it with ads at a scale of billions. They're institutionally incapable of being in the product or service business, because neither products nor services butter Google's bread. Advertisement does.
To address a common GraphQL issue, I tend to build a series of "WhereInput" types into the GraphQL project, which are small reusable inputs throughout the schema, to create a uniform way to filter entries or select a relational entry when creating/updating entries.
Custom domains is an interesting problem for most SaaS business, especially those running on large PaaS/IaaS providers such as AWS or GCP. The problem is, PaaS doesn't help when you want to run custom domains for your SaaS.
(Changelog) Article on the importance of timestamping columns in databases.
