Skip Navigation

  • I'm confused why people are voting down an article about AI in an AI community, discussing small language models, which are much better in terms of energy consumption and the environment.

  • I stumbled upon this article after reviewing a pull request, where someone was unit testing the abstract base class. I'm of the opinion that base classes should not be tested. We don't want to be testing the architecture of an application, we want to be testing the behaviour. The author sums this up nicely with this point:

    For tests, though, it shouldn’t matter whether the classes under test share the domain logic or duplicate it. Tests should view all production code as a black box, and approach verifying it with a blank slate. Otherwise, such tests will start couple to the code’s implementation details.

  • I'm not an architect, but I do dislike how much of development work has AWS wrangling, dealing with the architectural hoops that are mentioned in the article

  • Oh, it's not my own blog, I just stumbled upon it, and wanted to share the post.

  • Back in the day, I used CakePHP to build websites, and it had a tool that could "bake" all the boilerplate code.

    You could use a snippet engine or templates with your editor, but unless you get a lot of reuse out of them, it's probably easier and quicker to use an LLM for the boilerplate.

  • I also make use of ‘⚠’ to mark significant/blocking comments and bullet points. Other labels, like or similar to conventional comment prefixes, like “thought:” or “note:”, can indicate other priorities and significance of comments.

    Thank you for introducing me to conventional comments! I hadn't heard of them before, and I can see how they'd be really useful, particularly in a neurodiverse team.

  • The issue was they changed their server URL and added www, so I've updated the link accordingly.

  • How strange. It was definitely working when I shared it.

  • Ollama uses the Metal API on Apple Silicon Macs for GPU acceleration.

  • How does one measure code quality? I'm a big advocate of linting, and have used rules including cyclomatic complexity, but is that, or tools such as SonarQube, an effective measure of quality? You can code that passes those checks, but what if it doesn't address the acceptance criteria - is it still quality code then?

  • What I got from the article is an example of how generative AI can fix a bug, if you provide it with a reproducing case. Yet funnily enough, the AI introduced a bug in the first place by using an older version of a dependency.

  • The author of the article is Dan Abramov, the co-creator of Redux and a prominent React contributor. Putting aside what you may think of vibe coding, there is little doubt that he is an experienced developer, that knows what he is doing.

  • A good companion piece to this article, is the Dead Framework Theory article, which discusses AI coding tools bolstering React's dominance.

  • The author does make some good points about colours as visual cues, instead of just making things look colourful. I have to admit prior to reading this post, I always picked my themes on aesthetics, but it has made me think about colour as utility.

  • Preact is not new, it's been around for about a decade.