Code you and us
CMS platforms these days are becoming commoditised. The modelling of most systems lends itself to automation. Giving marketers more flexibility with less need for a developer. This does give developers more room to dive into the real challenges.
It’s what developers love to do most; creating code. So everything from low-code to no-code is what we are not trained, and especially do not live for. However these days with AI and better and better LLMs do come around the corner every day. The world of no-code is exploding and it becomes more promising every day. But ….
After a consumer of tools like ChatGPT and CoPilot, we as developers like to dive deeper into it. How does it work? Where to start? Can I create my own? etc. In this blog we dive deeper into our first steps to run LLM’s on our local machine
Now we have worked for a while with Chaplin framework, I like to share an example about how easy it is to work with this pattern and show you how you can create a more “customer friendly” conversation while defining and programming the application.
It has been a while since we posted our last blogpost. But not without a reason. Today I am happy to share our thoughts on where we have worked on the last year. Start discovering doing product development in our organisation we felt the need of a more scaleable idea of doing software development. The result is Chaplin (The Movie Pattern Practice).
Finally we are going to put everything together. And share our verdict.
Episerver Commerce is a very flexible product that can be customized to suit every e-commerce business needs. Almost every aspect can be customized though the way IOC is implemented in the product. But because everything can be customized to suit your needs does not mean that it’s good at everything, the UI of Episerver Commerce, and mainly the Catalogue part of it is not a walk in the park to work with for everyone.
About how to send context related data or other complex data to an external endpoint using Episerver Forms with valid JSON.
Containers seems to be a nice solutions, but it doesn’t always feel right to use this practice. I am going to share the considerations of using a container and share other features which maybe fits a “container use-case” better.
Sometimes I see blobstorages growing at customers side. It can be the result of a job, or because the storage is used by a couple of developers or because Develop and Test are using the same storage. For all these cases I have created this small script. Which does easily create a clean new container for you.
Codevelo.us 