1. 12
    1. 3

      Damn expired SSL cert. Feels like it’s been forever since I’ve seen one of those. Especially because it’s a Let’s Encrypt.

      1. 1

        It’s fixed now. Apparently my automation needs a little work.

        1. 2

          No worries happens to everyone.

    2. 2

      Unfortunately, building a comfortable and fast development environment is a surprising amount of work. I started a personal project… and two weeks of evenings all I have managed to build is one primitive API endpoint.

      Can you give more details on context? This sounds like a crazy amount of time. For example, the Django tutorial will leave you with a decent development environment, requiring maybe 30mins setup if you don’t know what you are doing.

      Are we talking about microservice architecture, or SPA with a host of build tools and libraries etc?

      1. 3

        It’s an API in Go. It’s all public if you’re really curious. There’s only one service right now so “microservice architecture” is overselling it a bit, but that’s the spirit. I started from scratch, and none of it has been incredibly complicated, there’s simply a lot to do. For instance, I like docker compose for a development environment, but it takes a bit of time to get just right. Then I need a self-signed TLS cert, and figure I ought to script that. And so it goes. There are handful of things like this that are simple enough but can easily consume the two hours or so I can get on a good night, so, yes, it’s taken me two weeks. If I had worked on it full time it probably would have only been a day or two.

        Django would have been faster. If I recall the origins of Django correctly, it was built for quick projects that would have been meaningless if they took very long, so they invested a lot into that 30m project start time. Those investments haven’t been made for any Go project that I know of. Revel is probably the closest, but it has a non-standard way of doing things and I avoid it.