• 1 Post
  • 85 Comments
Joined 2 years ago
cake
Cake day: July 10th, 2023

help-circle
  • Writing tests is the one thing I wouldn’t get an LLM to write for me right now. Let me give you an example. Yesterday I came across some new unit tests someone’s agentic AI had written recently. The tests were rewriting the code they were meant to be testing in the test itself, then asserting against that. I’ll say that again: rather than calling out to some function or method belonging to the class/module under test, the tests were rewriting the implementation of said function inside the test. Not even a junior developer would write that nonsensical shit.

    The code those unit tests were meant to be testing was LLM written too, and it was fine!

    So right now, getting an LLM to write some implementation code can be ok. But for the love of god, don’t let them anywhere near your tests (unless it’s just to squirt out some dumb boilerplate helper functions and mocks). LLMs are very shit at thinking up good test cases right now. And even if they come up with good scenarios, they may pull these stunts on you like they did to me. Not worth the hassle.



  • I tried GPT-5 to write some code the other day and was quite unimpressed with how lazy it is. For every single thing, it needed nudging. I’m going back to Sonnet and Gemini. And even so, you’re right. As it stands, LLMs are useful at refactoring and writing boilerplate and repetitive code, which does save time. But they’re definitely shit at actually solving non-trivial problems in code and designing and planning implementation at a high level.

    They’re basically a better IntelliSense and automated refactoring tool, but I wouldn’t trust them with proper software engineering tasks. All this vibe coding and especially agentic development bullshit people (mainly uneducated users and the AI vendors themselves) are shilling these days, I’m going nowhere near around.

    I work in a professional software development team in a business that is pushing the AI coding stuff really hard. So many of my coworkers use agentic development tools routinely now to do most (if not all) of their work for them. And guess what, every other PR that goes in, random features that had been built and working are removed entirely, so then we have to do extra work to literally build things again that had been ripped out by one of these AI agents. smh



  • This hits the nail right on the head. The point of cloud services is to take away all the overheads of building and delivering software solutions that have nothing to do with the actual business problem I’m trying to solve.

    If I want to get a new product to market, I want to spend most of my time making my core product better, more marketable, more efficient. I don’t want to divert time and resources to just keep the lights on, like having to hire a whole bunch of people whose only jobs is to provision and manage servers and IT infrastructure (or nurse a Kubernetes cluster for that matter). Managing Kubernetes or physical tin servers is not what my business is about. All this tech infrastructure is a means to an end, not the end itself.

    That’s why cloud services is such a cost efficient proposition for 98% businesses. Hell, if I could run everything using a serverless model (not always possible or cost effective) I’d do it gladly.


  • I was using the Signal “notes to self” too when taking notes during talks and conferences. Taking quick pictures of the slides in context was also a key thing for me. Exporting these unstructured notes into a useful notes archive is a pain as you say, especially if there is media too.

    I caught myself doing this so often that I ended up building myself an app for this specific workflow. It’s rather simple, just an MVP if you will, but it works well for me. Taking notes works exactly like Signal’s “note to self” but it has some QoL stuff on top of that like separate notebooks and exporting notes and pictures to a single PDF archive. I can then import the PDF archive into Notion, which is my main notes repository. Notion can now parse PDF files and import them as regular Notion pages, which closes the loop for me rather nicely. YMMV ofc

    I haven’t published it to any app stores yet (might do in the future) but the source code is available here if you’re technically savvy and happy to build and install it yourself.





  • Yeah, but there are degrees of vulnerability. Otherwise, things like password strength or MFA wouldn’t matter.

    If all your passwords are fully random, then that’s one less weakness that can be exploited. People can’t make educated guesses about your passwords just from analysing your social media profiles and history, e.g. if you post a lot about Star Wars, it’s more likely your passwords could contain a Star Wars reference.











  • Agreed.

    A lot of the time the cause of bad UX or poor quality code is not the Devs, but management, one way or another. Either through pressure to build more to increasingly delirious timelines or by not looking after their company culture.

    You tend to see nonsensical, disjointed product UX and usability decisions a lot more in bigger, highly hierarchical organisations, with big teams, highly specialised, siloed ICs several levels removed from their end users by layers and layers of middle management fat.

    I imagine if HSBC put out apps like OP’s article claims is because they probably follow a command and control structure like above, where developers are just tiny cogs hyper-focused on low-level tasks in a bigger, complex corporate machine and nobody really understands the full picture.