Re: Ganache And Implementing The New

For a long time I would test contracts on testnets versus using any local environments. I would see scripts and code for contracts that I knew worked, starting out with simple tokens, and just push out .sol files through Remix (where you can do unit testing), compiling and interacting with the contract and testing functionality. 

It was, and is, easy for simple tokens and contracts, and even to a certain extent, large and more involved contracts if you know the code and what you want to do. 

And there's only so much you can do as Solidity isn't an all encompassing program language.

I'm not saying it's for every project or group, or that you shouldn't have a local environment like you do with so many other frameworks/languages/systems--but it fits within that ecosystem and you can cleanup code/waste.

But then I found Ganache and I'm still using it, eschewing other tools.

Because I honestly just need that for the type of projects I'm doing.

While I have to sometimes implement the very latest for different domains, for others, I can peripherally know what's new, but not necessarily implement it and use something "less new" regardless of support and other updates.

Again, I'm not saying you shouldn't be using something like Hardhat, I'm just saying I understand you if you are not.

It's a balance.

AI Will Kill The SaaS? Me Thinketh...Maybe?

I was reading this article on Medium and I think there's a lot of validity to it for a number of reasons but first, a snippet from the article:

The beating heart of this software will be AI and LLMs. In some cases, these entire workflows might be automated, where no UI is needed, and AI just navigates a series of API calls to do the job independently.

Don’t believe this is possible today? Here’s an example of how an intern at a YC startup built an AI-powered invoice processing pipeline instead of paying $16K for a SaaS tool. It took him, wait for it… two hours.

But, as the article also goes on to say, customized apps and processes, which are needed for business, and which AI can help create--still doesn't make it a SasS killer.

Why?

Because AI will augment SaaS, and Enterprises will still like SaaS because of software agreements, liability, coding and security resources, et al.--I agree. 

But it will change. It will depend on the company. And I'm not saying it's the right decision. 

AI helps automate tasks. Some of that is custom code and applications and processes. 

If you do business like everyone else does business what then makes you unique?

You have to have some SaaS.

But for customized processes, what makes you standout--you didn't really need SaaS anyway.

So maybe this isn't even a thing?

Hmmm.