In this article, the author presents the library and conversion functions used in the conversion process from RTF files into DITA format. A few steps go into it: conversion from RTF to HTML, from HTML to XML, and from XML via XSLT to DITA.
In this short article I'll show you how you can improve your IntelliJ experience when using IntelliJ with Git source code management.
Learn Java SE 8, from a pair of masterful teachers. Given the book’s pros and cons this may not be the best choice for someone new to both programming and Java, but if you are already a developer and want to add Java to your skill set, or just an introduction to the new features of Java 8, it is well worth the price.
DevOps is a fundamental shift in the IT methodology and we are super excited to be a part of the industry. 2014 will be year of rapid innovation and scaling adoption. It should be exciting for all involved.
Automated User Interface (UI) testing has a deserved reputation for being a morass of low-value, high-cost pain. Developers are already over-burdened trying to get the work in front of them completed and into the delivery pipeline.
This month's Continuous Delivery industry update includes: Electric Cloud launches two new automation and build tools, IBM launched a simplified environment manager, Codeship gets a redesign, CFEngine Enterprise 3.6.0 is out, Chef issue tracking is updated, the CloudBees and Serena partnership, and more.
Nhan Ngo, a QA engineer at Spotify, made a series of illustrations about visualizing Continuous Delivery that are available under a Creative Commons license. She's done an amazing job at making a concept easy to visualize that many are unable to understand even after a great deal of educating.
Big news Thursday in the tech world: the Supreme Court ruled unanimously in Alice Corporation Pty. Ltd. v. CLS Bank International that an abstract idea isn't patentable.
Ensuring software quality is a challenging task in the current dynamics with aggressive timelines, changing business requirements, increasing enterprise-level constraints and demanding user experience expectations.
I’ve recently been following the #isTDDDead debate between Kent Beck (@kentbeck), David Heinemeier Hansson (@dhh), and Martin Fowler (@martinfowler) with some interest.
Most businesses depend on third parties to reliably deliver products or services to their customers. E-commerce sites rely on delivery services. Broadcasters rely on cable and satellite providers. And web platforms rely on cloud infrastructure to keep their systems accessible.
While the artifact of Test Driven Development is test code, what you get out of test driven development far exceeds the test themselves. Another thing TDD does is that it prevents feature creep on the part of developers. By coding to the test, you reduce this urge.
New developers joining a project will often find that the project won't build cleanly on their machine, and hours of time will be sunk into setting up the project so work can start. Counter this by using continuous integration to build your project from scratch.
The good news is that open source projects release newer versions of their components that address newly found vulnerabilities. Bug-free alternatives are available. But making use of these newer more secure versions, relies on ensuring your organization has a process to identify these defects easily and early.
I remember back in late 1990s when I discovered Socket communication and how that can help back-end processes to provide information to the outside world.
One of the great things about Angular is that it does not make us extend anything, and we can just use plain old Dart objects. This enables testing them without any help from the framework. There are, however, cases where it becomes problematic, especially when testing decorators and components.
The point here is that the balance for your organization ought to reflect your actual practices. Whether you consider past practices or anticipated practices is an interesting thought exercise, but you should be considering something.
I am pleading with developers to stop building Plato's cathedral. Software development is not about populating an unseen world with perfect widgets. It is about building the appropriate structures such that both you and the computer can agree about what happens when you execute the program.
Why write unit tests? They validate current and future implementations. They measure code quality. They force you to write testable, loosely coupled code. They’re cheaper than manual regression testing. They build confidence in your code. Use this checklist to be sure your tests are really useful and to the point.
How to convert Spring 4 ListenableFuture to Java 8 CompletableFuture and back
Make sure you didn't miss anything with this list of the Best of the Week in the DevOps Zone (June 6 to June 12). This week's topics include 5 things about open source components, a story about TDD, why DevOps matter, the rise of the DevOps movement, and using private and final in open source software.
This is about a simple testing technique that is probably obvious, but I’ll share it anyway.
le_java is one of several libraries that allow you to send log data directly to your Logentries account from your application.
I did a very unscientific twtpoll recently regarding what brought each of us into open source. Plenty of people took the time to vote or retweet, so I thought I'd loop back around and let you know how it looked overall when the poll closed.
Validation is crucial part of development. From argument checks to validating workflows, pipelines, input/output boundaries we run checks to make sure that an application will behave correctly. I like to see the business processes before the implementation and try to express myself via code in that manner.