We live in a connected world – a world in which personalization and apps are at our fingertips and where your job doesn’t end the second you walk out of the door at 5:00PM. However, we often find that our companies are slower to innovate, adopt, or offer the services we are accustom to outside of our work. We find that IT is still busy staying on top of service desk tickets, than reaching out to the business to improve productivity. As a result, the rapid development of mobility and cloud services has coined terminologies such as “Shadow IT”.
Over the last few years, I’ve been a member of several different systems development teams. Whether working with Java developers on a web portal project or SQL coders on a financial data warehouse, I found that despite using vastly different tools and skill sets, developers were almost always working within a best practices framework. When I first started working with Informatica PowerCenter a few years ago, I watched dozens of tutorials to get started, but struggled to find information related to best practices for many of the scenarios I encountered in my project. Whether you are a new or seasoned Informatica developer, consider implementing these 5 best practices to your development process.
I recently attended CocoaLove, a developer conference in Philadelphia. At that conference there was a talk presented by Austin Seraphin, a man who has been blind since birth. When I first saw that he was going to be speaking about Accessibility I was a bit surprised and I did not quite know what to expect. On the one hand, who is going to care about accessibility more than a blind person? On the other, how is a blind person ever going to use a touch screen device?
One of the challenges of responsive web design that I find most interesting is deciding how to effectively render navigation across all target screen resolutions. Luckily there are flexible frameworks like Bootstrap that make displaying responsive navigation a relatively simple task. However, mobile navigation has been evolving over the past several years, and it can be difficult to keep up with the latest trends. For example, many mobile sites have moved the "hamburger" button from the right hand side of the navigation bar to the left hand side, and the menu now slides in from the side
As you've read on this site and many others, the database world is well into a transition from a relational focus to a focus on non-relational tools. While the relational approach underpins most organizations' data management cycles, I'd venture to say that all have a big chunk of big data, NoSQL, unstructured data, and more in their five-year plans, and that chunk is what's getting most of the executive "mind share", to use the vernacular.
Getting delimited flat file data ingested into Hadoop and ready for use is a tedious task, especially when you want to take advantage of file compression, partitioning and performance gains you get from using the Avro and Parquet file formats.
In general, you have to go through the following steps to move data from a local file system to HDFS.
I recently decided to learn programming in the R language, when looking for a class to help me learn I wanted to choose something that would not only teach me the basics of the language but also how to us it in real world situations. I chose to take a look through some of the Massively Open Online Classes (MOOCs) that are available. Below is a quick review of 3 classes that I took to learn R.
Image carousels are a common need for mobile applications. These can be used to provide users with a familiar experience to view and scroll through images. Thankfully in Windows 8.1 and Windows Phone 8.1 Microsoft has provided useful components to easily create these carousels.
To start creating the carousel I have created a new User Control and named it "ImageCarousel". This control will need to contain a dependency property that holds the image URLs:
It is fairly common in enterprise development to support multiple environments, be it development, a multitude of testing, performance testing, beta and production environments. This requirement is no different for Android development. My current client has close to 20 pre-production environments that support development, various forms of QA, performance, and production support environments.