hleszek

AI and blockchain?

For some reason the VibeVoice model from Microsoft (which is also able to clone voices and is also very good) has been deleted from GitHub 10 days ago even tough it was released under a MIT license. But this post shows that the cat is out of the bag for some time already now (post is from 2021) and we have to live with this technology.

Another possibility with this idea is to have a normal clock but with the 3 and the 9 numbers inversed (going backwards at normal speed). Such a clock will be right 4 times per day.

It generalizes to the formula r = -(n - 2)/2, so if we want a clock which is right every second, we could have a clock going backwards 43,199 the normal speed...

It's just a clock going backwards with half the normal speed.

They would ban the developer, or its key or whatever and ask him to register again and not do this again. They won't allow any workaround like this to exist because then the whole system has no purpose, they need to have control.

The only thing that matters is the checksum, because who cares if the destination address is not currently in the blockchain. It is obviously possible to send BTC to a new address which is not already there.

Maybe it's to make it more difficult to train AI video models from YouTube. Think about it, they have the raw footage so could use it if they want, but competitors using scrapers will have slightly distorted video sources.

That's why I started this discussion, hoping that someone would know what happened and also to discuss how to organize an alternative when the repository is archived and discussion is not possible anymore on GitHub.

Backoff, The popular Python decorator library for backoff and retry has been archived on GitHub on Aug 8, 2025.

The project is abandoned, with the last update from Jan 20, 2023.

I would guess like him that no human engineer ever read his application. The less they would have done in that case would be to at least thank him for his work, even if they don't plan to hire him for some reason.

Automated systems, AI screening, and incompetent HR people are the bane of modern recruiting practices.

It's not clear from their page but the editing model is not released yet: https://github.com/QwenLM/Qwen-Image/issues/3#issuecomment-3...

Can humans do randomness? Obviously not and I expect if you ask people for a random number, then odd numbers will predominate.

Now do it in VR and make it fully interactive.

As long as we don't ask it to make paperclips it should be fine.

We should use xcancel instead.

I must have been a little too ambitious with my first test with Claude Code.

I asked it to refactor a medium-sized Python project to remove duplicated code by using a dependency injection mechanism. That refactor is not really straightforward as it involves multiple files and it should be possible to use different files with different dependencies.

Anyway, I explain the problem in a few lines and ask for a plan of what to do.

At first I was extremely impressed, it automatically used commands to read the files and gave me a plan of what to do. It seemed it perfectly understood the issue and even proposed some other changes which seemed like a great idea.

So I just asked him to proceed and make the changes and it started to create folders and new files, edit files, and even run some tests.

I was dumbfounded, it seemed incredible. I did not expect it to work with the first try as I had already some experience with AI making mistakes but it seemed like magic.

Then once it was done, the tests (which covered 100% of the code) were not working anymore.

No problem, I isolate a few tests failing and ask Claude Code to fix it and it does.

Now for a few times I found some failing tests and ask him to fix it, slowly trying to fix the mess until there is a test which had a small problem: it succeeded (with pytest) but froze at the end of the test.

I ask again Claude Code to fix it and it tries to add code to solve the issue, but nothing works now. Each time it adds some bullshit code and each time it fails, adding more and more code to try to fix and understand the issue.

Finally after $7,5 spent and 2000+ lines of code changed it's not working, and I don't know why as I did not make the changes.

As you know it's easier to write code than to read code so at end I decided to scrape everything and do all the changes myself little by little, checking that the tests keep succeeding as I go along. I did follow some of the recommended changes it proposed tough.

Next time I'll start with something easier.

And that paywall is so annoying... As it is further down the page you don't realize it's paywalled and have time to get immersed in the story before you get stopped abruptly.

He pretended he was sick and his money was frozen because of his divorce and needed a lot of money for expensive operations which failed one after another.

Sorry, I'm afraid I can't do that, Dave, you're drunk.

A paralyzed man who relied on a $100,000 exoskeleton lost his mobility when the manufacturer deemed the device too old to repair after only 10 years. Despite the issue being a minor battery malfunction, the company initially refused service due to its outdated model, only doing the right thing after the situation became highly publicized.

Are the weights available since it's based on Meta Llama 3.1 405B?

Who would buy a building like this without the land? How does it make sense?

2008

I started in 2008. This is what I did eventually. Over the years I introduced the small company to Linux, git, defensive programming, linting, continuous integration, Scrum..., but only for the new projects and stayed 13 years there.

That old project though was never fixed though, probably still running that way now.

When I started at my first company, they had a very complex VB application running on dozens of customers around the country, each having some particular needs of course. There was a LOT of global variables (seemingly random 4 uppercase letters) controlling everything.

At some point, the application had some bugs which were not appearing when the application was run in debug mode in Visual Studio. The solution was obvious: installing Visual Studio for each customer on site and teaching the users to run the app in debug mode from Visual Studio. I don't know how they convinced the users to do this and how they managed with the license but it was done.

What happened next was even worse.

There was no version control of course, the code being available on a shared disk on the local network of the company with the code copied over in multiple folders each having its own version, with no particular logic to it either, V1, V2, V2.3, V2a, V2_customer_name, V2_customer_name_fix, ...

After that, when there was a problem for a customer, the programmer went there to debug and modified the code on site. If the bug/problem was impacting other customers, we had to dispatch some guys for each customer to go copy/edit the code for all of them. But if the problem was minor, it was just modified there, and probably saved on the shared folder in some new folder.

What happened next was to be expected: there was no consensus on what was the final version, each customer having slightly different versions, with some still having bugs fixed years before for others.

As the current maintainer of graphql-python/gql, the most popular python client, I have to say that you should definitely try again to get an accurate opinion. A lot of changes have been made around that time and we are quite feature-full and stable right now, with 100% code coverage and good documentation.

A simple list comprehension is quite readable and better IMHO. It is very common and most people will understand directly what it does.

Of course, when you have multiple levels or complex lambdas inside, then I agree that the for loop might be preferable.