Bert Hubert

Yeah, no, that was very impressive. And they should do more of that.

Yeah, no, that was very impressive. And they should do more of that.

Well, that is in New Zealand. That's what you're referring to, probably. Yes. Yeah. So they had a law that was passed, which was not good for the indigenous people in New Zealand. And then they got really upset. And then the indigenous people or the people affiliated with them in parliament actually performed the whole song.

Well, that is in New Zealand. That's what you're referring to, probably. Yes. Yeah. So they had a law that was passed, which was not good for the indigenous people in New Zealand. And then they got really upset. And then the indigenous people or the people affiliated with them in parliament actually performed the whole song.

a protest song in government, which is really a very important thing in New Zealand. But it was, I think, a great way of making a point. And I have not, I cannot imagine US Congress breaking out into a song. Oh, goodness gracious. Please, no.

a protest song in government, which is really a very important thing in New Zealand. But it was, I think, a great way of making a point. And I have not, I cannot imagine US Congress breaking out into a song. Oh, goodness gracious. Please, no.

Yeah, so it was invited. So I'm a very part-time technical advisor to the Dutch government also, to what you would call the FEC, the electoral board. And they built this software for tabulating the national elections. And they are revamping it. And they said, look, would you take a look at our code? Can you tell us what you think about it?

Yeah, so it was invited. So I'm a very part-time technical advisor to the Dutch government also, to what you would call the FEC, the electoral board. And they built this software for tabulating the national elections. And they are revamping it. And they said, look, would you take a look at our code? Can you tell us what you think about it?

And I looked into it and I found that they were doing sort of more or less standard 2025 software development. And then I wondered, and that means having like 1600 dependencies. Because if you have a Node.js built project these days and you install it, it will, for starters, pull in like a thousand dependencies. And then you haven't done anything yet even.

And I looked into it and I found that they were doing sort of more or less standard 2025 software development. And then I wondered, and that means having like 1600 dependencies. Because if you have a Node.js built project these days and you install it, it will, for starters, pull in like a thousand dependencies. And then you haven't done anything yet even.

And so I looked into that and I thought, well, this is not going to be something that's viable for the next 10 years. because these dependencies change all the time and NPM might go away for the next 10 years. So I turned that into a study. What would you do these days if you had a like 10 year software project?

And so I looked into that and I thought, well, this is not going to be something that's viable for the next 10 years. because these dependencies change all the time and NPM might go away for the next 10 years. So I turned that into a study. What would you do these days if you had a like 10 year software project?

And I went to Mastodon, that is really good social network to ask these kinds of questions because they're like full of nerds. And they're my people. And so I asked them, I said, look, what are your thoughts for anyone doing long-term software development? And we had people weigh in that have a software with an 80, and not 18, 80-year horizon. Wow.

And I went to Mastodon, that is really good social network to ask these kinds of questions because they're like full of nerds. And they're my people. And so I asked them, I said, look, what are your thoughts for anyone doing long-term software development? And we had people weigh in that have a software with an 80, and not 18, 80-year horizon. Wow.

And these are people that study and have to measure the radioactive decay of nuclear waste. And they are tasked with measuring and supporting that for the next 80 years. And so they spent quite some time thinking about this stuff. And it turns out that actually it's sort of modern software development.

And these are people that study and have to measure the radioactive decay of nuclear waste. And they are tasked with measuring and supporting that for the next 80 years. And so they spent quite some time thinking about this stuff. And it turns out that actually it's sort of modern software development.

It's like sort of the complete opposite of what you would do if you want to have software that works 10 years from now. And in the sense that we have these huge, that's even building software is fragile right now.

It's like sort of the complete opposite of what you would do if you want to have software that works 10 years from now. And in the sense that we have these huge, that's even building software is fragile right now.

So if you just, not even that it does the same thing, but if you want to build a sort of standard 2025 software project, you need a working internet connection and like hundreds of servers around the world that supply you with data even before your software runs. And that is not something that is a healthy thing to have if you want to promise people that it will work 10 years from now.

So if you just, not even that it does the same thing, but if you want to build a sort of standard 2025 software project, you need a working internet connection and like hundreds of servers around the world that supply you with data even before your software runs. And that is not something that is a healthy thing to have if you want to promise people that it will work 10 years from now.