Discover how My DJ Cloud ensures data consistency and integrity with Hybrid Logical Clocks (HLC). Learn about timestamp generation, conflict resolution, and handling concurrent updates across devices.
After previous failed attempts to get Devin.ai to do some real-world work I had it try some real junior stuff. The results are better.
My first interaction with Devin AI! Can it migrate a Vue.js 2 application to Vue.js 3?
Discover the journey of transitioning from BlogEngine.net to Zola and GitHub Pages for a simpler, more efficient blogging experience. Learn how to migrate your blog, maintain essential features, and enjoy the benefits of static site generation with minimal maintenance. Perfect for developers seeking a hassle-free, Markdown-based blogging platform.
This is my second post in the series around Sitecore module development as well as a follow up post to Sitecore needs a NuGet feed for their assemblies.
I maintain a fairly well used "Field Fallback Module", which was released in June 2012. The code for this module is available on GitHub and it has been setup with a very simple build process that has remain unchanged since day one. The module isn't under heavy development, but there have been a couple bugs reported lately. I took this opportunity to revisit the build and deploy process and see if we couldn't modernize it a bit.
In the Sitecore Slack Team's #TDS channel there was a Team Development for Sitecore feature request from Robbert Hock. It was:
This is a call to action for Sitecore to start hosting a NuGet feed of all common Sitecore assemblies. However, lets take a look at how the Sitecore development process has changed over the years.
A very common feature request we get for Team Development for Sitecore at Hedgehog is that people want code generation to create a file per Sitecore template in their project. Currently, when TDS code generation runs it will create a single file with all of the code inside of it. Using partial classes it enabled developers to extend the class with their needs, in a separate file, all the while keeping the code generated part in a file that can be overwritten and updated at any time by TDS. This is very much like the way Linq-to-SQL works.
From time to time we get feature requests for Team Development for Sitecore to support multiple sub-items with the same name as shown below.