Timothy B. Means

Tag: MVC

  • JS journey retrospect

    Last year I “wondered if MVC was even the best design for a chess game,” but if I had taken the time to read about the Universal Chess Interface (UCI) I would have seen that MVC is a common design for online chess. If I had built to UCI specs and selected a full-stack framework instead of trying to write backend from the ground up in Node, I might not have given up and resorted to just writing frontend for a platform service.

    Sure, online chess is a solved problem, but I was reinventing the wheel for learning’s sake.

  • Server actions debate

    So i return to PHP practice and unfortunately fall into a habit of writing a page or form response src like i did in 2019, one script inside html, and the script does both PDO to get data and uses that data in the render of html.

    Later in my regular doomscrolling on Twitter I find this screenshot of a presentation slide that has started a big conversation, the slide depicts a React component in Next.js that does exactly what my quick fix php does, access data and render in the same script, only all in JS. And the upshot of the conversation is this, these backend frontend scripts aren’t following best practices for architecture, e.g. MVC.

    So, mission accepted, no more quick fix scripts, and time for me to work on a real MVC project and see it through, unlike in 2021 where I thought I could create an MVC SPA without using any frameworks, just JS libraries Node and jQuery.