magic VS sakila

And while we're at it, if you count commits as cognitive work, Magic had 8,007 at the time I closed its source code. Later it's been accumulating some roughly 570 additional commits. 99% of these commits are done by yours truly.

Magic Cloud is the name of our platform. Magic is what allows us to deliver our AI solutions - So writing about our technology's security basically implies writing about Magic Cloud's security.

In the island of Cyprus, I'm the by far most productive GitHub developer with some roughly 12,000 commits. If you check out my username which is "polterguy", you will only see me on 4th place or something - However, this is because GitHub resets commits back to zero if you change your email address, and I really don't give a sjit, so I've not bothered to fix it. If you want to know "my credentials", then look at my work.

Hence, by creating small reusable AI functions, such as we've got the ability to do at AINIRO, any human being can prompt engineer a rich and complex AI app together, allowing his or her users to use natural language to interact with the software.

We already have several clients that are using our AI chatbot for these purposes - However, probably the best use case is our own software system, which is highly complex, and therefor difficult to initially understand. We get a lot of questions about Magic Cloud, and even though I love answering these questions, a lot of questions can be automated by the AI.

I've got an AI chatbot company, and because of that, I have to somehow relate to Google code. Google code is everywhere, and creating a website without using Google code is almost impossible for these reasons. Google Analytics being one reason, and Google reCAPTCHA being another reason. If you've got a website, there's a 99% probability that your site is running some Google code.

As an additional bonus, it completely eliminates all Postman script kiddies, since the client must be able to execute code to create a valid token. It also eliminates reusing the same token for multiple servers, since each server has their own unique public key - In addition to that you get to market your AI chatbot as "powered by Blockchain technology", and you can actually say that out loud with a straight face, without lying ... 🤪

As an AI chatbot provider, we need some serious bot protection to prevent malicious users from creating bots that attacks us. Google reCAPTCHA of course is "the industry standard" here, which I'm sure most readers are aware of.

I just swapped out Google Analytics with Plausible for AINIRO.IO. It’s only been a week, but so far I am super jazzed about it. First of all, Plausible doesn’t use cookies, so I can completely drop all cookie disclaimers and popups I had because of GDPR. Second of all, the site scores significantly better on load time. This results in a 10x better user experience for my website visitors, while making sure the website is still 100% conforming to GDPR laws.

After having owned an AI chatbot company for more than a year, I finally did what I'm supposed to do before I even start a company; I did a Competitor analysis - And o'boy should I have done it earlier.

Can somebody that's like super smart on React tell me what would be needed to implement this thing in React? The current stuff is Angular, and its code can be found here. What I would need is as follows.

Sorry guy and gals, we just published a new feature in our CRUD generator, and it's basically an AI system that 100% perfectly replaces the human software developer with machine learning algorithms, so you won't be needed anymore at work. Sorry about that, but maybe you could learn how to play the violin ...?

My business is CRUD, literally. In fact, I've got a company around the axiom of CRUD. We're a handful of employees, we've got some VC funding, and we literally "do CRUD" 100% of our time one way or another. Of course, this implies having to think of a lot of other things, such as authentication, authorisation, security, etc - But the basic axiom around which we evolve is that life is too short to having to manually create CRUD apps.

For the record, I would not recommend anyone to stuff 2 billion records into a MySQL database, but it is possible, and Magic handles it just fine. Of course, simply counting 2 billion records takes minutes, and in order to be able to even use it in a Hyperlambda generated CRUD backend you'd have to apply some super aggressive server-side caching constructs, but it is possible as you can clearly see from the following screenshot.

And of course, the code generated by our system is easily several orders of magnitude higher quality, according to every single neutral metric we use to measure quality. In fact, run this code through one of your frontend/Angular developers if you want to assess it from a quality perspective. I guarantee you that he won’t find a single bug in it! Then realize that this code is running here. Try it out for yourself by logging in with admin/admin.