huijzer

Ever since I switched to Forgejo (could do Gitea or other self-hosted too), my outages have gone down to basically zero. It’s only down when I do maintenance but since I’m not pushing code at the same time it doesn’t matter

Very Biblical title (or anti-Biblical depending on how you look at it).

Genesis 1:3, "And God said, Let there be light: and there was light."

Say we have a trivial function like this

    func below_ten()
      if 10 < x
        println(“true”)
      else
        println(“false”)
      end
    end

Now what would a test for these two paths test? It would basically be writing down the same - easy to understand logic - in a less generalized way. Good perhaps to ensure that this function doesn’t accidentally change over time but apart from that it wouldn’t add much value.

> Untyped languages often have tests that effectively implement a type system as software grows and the developer count grows. That seems like a waste…

Nicely put. A very verbose type system that is also placed too far away from the definitions indeed

> 100% test coverage

I don’t believe in 100% test coverage. Especially outside some very specific cases, it just adds a lot of code with little to no value.

It sounds essentially like 1984. Not that the world needed him for that though because with the most recent Samsung TV scandal about microphone and camera spying on users it seems also that fiction became reality to a certain extent.

> A coworker recently remarked that lean seems like a new foundational language family that every programmer should be able to read

Extraordinary claim requires extraordinary evidence.

Why? I’ve worked a bit with proving systems in my studies, but it seems to me that it is very hard to turn precise mathematical statements into useful programs. Perhaps for the core logic, but GUIs or any other state with the outside world is going to be difficult it seems to me

> haven't fully realized/felt the cost implications of trainwreck software yet

As long as the API is private or not dependent on by automated systems and you have good test coverage, you can get away with bad code IMO since you can always refactor. If it looks stupid but it works (and can be refactored/fixed/improved later if needed) it aint stupid.

From my few months of work, that seems likely yes. I'm way stronger in core and legs now.

I don’t know where you live but here in the Netherlands we always turn the power off first. (Another thing I like about the trades so far are jokes like this.)

Thanks! That's kind of you

I'm in ship construction (industrial)

I have done multiple studies and they were always technical, so the company took a shot and hired me and would train me on the job. So far it's going well. They say I'm picking up stuff quickly and I occasionally help the head engineers with problems on their computers. This would probably be the same for most programmers. Reading drawings, connecting electrical circuits, and doing troubleshooting is surprisingly similar to programming.

> No, programming and math is basically what AI research is.

Most importantly, in these fields results can be easily verified which means that if you have enough compute, that you can generate correct training data. OpenAI had an early story - which could be a lie of course - about how they tried to train a robot but the actuators would be toast before the robot would have learned. Math and programming doesn't have such problems.