I would have said “Test Driven Development” but I want to make it clear that what I’m talking about is writing test first, or at least simultaneous to writing the code. Not sometime after, even if that after is immediately after.
Software integration used to be the customer’s headache in the days of on-premise solutions, but the cloud has changed all that. So why are we still talking about it? This article includes a weekly roundup of top API and integration articles from MuleSoft.
Finding relationships that should not be there is a great use case for Neo4j, and today the author wants to highlight an example of why: One of the hardest things for SQL based systems to do is cross-check the incoming payment information against existing data looking for relationships that shouldn’t be there.
This article includes a link roundup of the very best articles of the week about SaaS and cloud platforms. Topics include entrepreneurial investment, e-mail and work productivity, SaaS platform vendors, and SaaS metrics that you need to hear about.
This article brings heavy emphasis to what exactly Application Services Governance is, and focuses specifically on the best practices to accelerate safe delivery. Application Services Governance is a mechanism to achieve business agility, build a responsive IT organization, and optimize IT effectiveness.
Headroom.js is a lightweight, high-performance JS widget (with no dependencies!) that allows you to react to the user's scroll. As you scroll down the page the header will be hidden, but when the user tries to scroll back up the page it will display the header bar.
Scalable Vector Graphics (SVG) are available in the latest browsers, but there are some inconsistencies. If the last mile were closed, then bloggers would appreciate the speed improvement (and scaling) for end-users.
Looking for some shortcuts to make Android development easier? This post provides just that when it comes to the Android Debug Bridge. It's a no-frills collection of useful adb commands, covering essentials such as checking connected devices, installing/uninstalling applications, starting an activity, and more.
In MongoDB, the replication oplog is a capped collection, with a fixed size on disk, and therefore the amount of history (measured in days) varies as the application makes changes faster or slower. In TokuMX, capped collections are handled differently.