This month’s update to Hutch’s Big Book of DevNotes is fairly minor. I’ve added some new content to help with testing in Varnish, particularly how to test that you’ve removed a header. I’ve also spent a bit of time on the overall layout, so that printing individual chapters makes more sense. Putting the chapter name in the header helps, as does having the free-culture license in the footer.
I’ve put together a book containing a few chapters on some of the technology I’ve been using based on notes and actual experiences. It’s early days, and I plan to improve and expand upon this beginning, but I hope that it’s useful. The topics I’ve included for this initial draft are Docker, LaTeX, Magnolia CMS, and Varnish Cache v4, and while there are plenty of notes and pages both online and in print for the first two, there’s scant little on Varnish 4 (it’s mostly for earlier versions), and not all that much on Magnolia CMS either beyond the official documentation. I hope that you find something useful here that helps you.
Continue reading →
At some point in the SDLC it becomes necessary to carry out performance tests to make sure that what you are building will function to an acceptable level.
There are a few things you can take from this statement:
- “at some point” doesn’t have to be the end of development
- it should be part of the lifecycle
- you have to do it, it’s necessary
- tests don’t just happen, you have to perform them
- “what you are building” implies that you focus on the things you can control
- and finally, “at an acceptable level” means you should have a goal or objective.
In the vast majority of projects, these considerations are left until the end. I think it’s worth discussing the implications of this, as it’ll really help make the tests worthwhile and help you get the most out of the developed software.
Finally, after many months of waiting, I received my Steam Link & Steam Controller. For those who don’t know what this is, the Steam Link is more-or-less a wireless HDMI connection with some bells and whistles, a sort of reverse Chromecast. It connects to a PC and streams the display, audio, and controls so that you can use a living room television without having to drill holes in walls and run cables, or move the computer. Because it’s for gaming, it needs to be extremely low latency and for the most part it succeeds. The controller, as you might have guessed if you haven’t already seen one, is a wireless handheld device designed to work with traditional keyboard and mouse games. It too succeeds in some ways, but both have flaws and rough edges that really need polishing to make it appeal to those used to more mainstream offerings from Sony and Microsoft. Continue reading →
Just for giggles, and because my current role has a site that has many forms of advertising, I thought I would see what would happen if I put it on my own site. Here is what knowledge I have gained from the two weeks it has been present on here.
I needed a lightweight, simple, fast tool to check a long list of URL links from a plain text file, so I decided to write a small application in Rust. If you’ve not come across Rust before, it’s a high-performance, low-level language that offers memory safety without garbage collection, type inference, and great concurrency support. It’s a young language but shows great promise, and is ideal for this kind of application.
Having produced a simple first version of the application and posted it on GitHub (https://github.com/antonyh/link-checker) I thought it might be useful to look at the code and explain how it works.
Adding vanity URLs in CQ5 is a little cryptic and the documentation provided doesn’t help much. It’s especially not clear when domain mapping and URL rewriting has been configured.
I’ve started to put together a public wiki for CQ5 & AEM6 resources, unimaginatively titled ‘AEM Developers’. It can be found at http://www.aemdevelopers.com/ and is hosted on WikiDot. I’m using it as a place to promote links to articles that are useful, a blog roll, and profiles of developers and companies specialising in Adobe AEM. There’s an events section too that hopefully will fill out nicely as time goes on.
Please sign up and add any blogs or links to guides, and add comments to the pages that are already there. You’re all invited.
So, AEM6 has the option of using MongoDB instead of TarPM, and Solr instead of Lucene. What does this mean to the developers who work with CQ5, those who are looking to get into AEM, and the architects who are designing and planning implementations?