I've recently made a change in employment and I'm now Lead Product Evangelist at @Kentico 🎉🥳
Are you a member of the #Kentico community? I'm here to support you 💪
For details about my journey to this role and what I'll be doing next, read on 🧐...
linkedin.com/posts/sean-g-wr…
A first class integration with htmx has been a priority for some time. @dpraimeyuu graciously handed off his experimental branch to me. Huge kudos to him for starting off the project!
I'm tickled pink to announce the official beta of version 1.x!
nuget.org/packages/Falco.Htm…
Over the next few weeks I'll be putting out some blog and video content on NServiceBus, zero-to-hero style, based on my experiences with the framework and the tooling around it. Very excited to kick this series off!
NServiceBus is a framework packed full of features for implementing messaging and workflow orchestration in .NET applications. @KyleMcMaster has started a series on this here: bit.ly/43cfRkb#NServiceBus
Interested in learning more about accessibility tools and technology for captioning?
@edmistond provides a great list of the options available. This is helpful for those consuming the captions and the people speaking.
Could be very enlightening for conference organizers 🤯!
A post that's been rattling around in my brain for about two years, though it's much simpler now than it would have been two years ago.
Have you wondered what automatic captioning tools can help with accessibility? I have a post for you: davidedmiston.com/post/2023/…
Are you looking to implement effective custom activity tracking in Xperience by Kentico? Check out my latest blog post for a step-by-step guide: dev.to/byteminds_agency/acti…#kentico#dxp
4 years ago today was day 1 of @Kentico Connection 2019 - the last in person Connection event.
Since then the virtual events have been great, but I cannot wait to see everyone in person next month for @Kentico Connection 2023!
The realization might be that some of your operations are just straight CRUD and the DTO is extra cruft. Replicating models where it matters and not everywhere.
I'm getting tired of the "how will it scale?" argument.
Nearly anytime someone asks a question about self-hosting, using container-based solutions, or anything that isn't "serverless," there's at least one person who responds with "How will it scale?" thereby discouraging people from using tried and tested methods that have been used for years.
At this point, I'm starting to wonder whether these folks understand how powerful modern hardware is and how little resources most applications need or that the scale they are talking about is far beyond what most will ever need.
Seriously, if you're thinking about self-hosting your services or going with anything that isn't "serverless," don't let any such arguments discourage you. Statistically speaking, scaling will never be a problem for you, and if it is, you can always throw more hardware at it (which is very cheap).
I've been watching some HTMX talks. And I know that it's hard to recite the history of the web without making some simplifications, but I guess I will point them out anyway :D
history of the web according to HTMX:
- web 1.0 with no JS only HTML
- web 2.0 with SPA and JSON communication for everything
- return to the form with HTMX
The history of the web how I remember it:
- turning websites into apps happened before we had proper CSS and JS
- 1996-1997 when the first ActiveX and Java applets happened (just a few years after CSS and JS were invented)
- in the 2000s we had Flash and Silverlight
- in the 2000s we had XMLHttpRequest. Do you notice something? It's not JSON HTTP Request. Because that was intended to exchange HTML or XML
- all of this was firmly in the web 1.0 era. But we already had app vs website split