April 03, 2015

Python Programming Resources
This is a comprehensive list of Python Programming resources. Python is a widely used general-purpose, high-level programming language. Its design philosophy emphasizes code readability, and its syntax allows programmers to express concepts in fewer lines of code than would be possible in languages such as C++ or Java. The language provides constructs intended to enable clear programs on both a small and large scale. It was named by Guido van Rossum, the creator, after Monty Python’s Flying Circus.

SQL SERVER – 3 Common Mistakes of Agile Development
Most of the development shops that I’ve worked have struggled with the ongoing battle to get features built and shipped on a schedule that satisfies business requirements. Good developers are proud of their craft, and want maximum time to create; business needs features to go out the door quickly in order to compete. These goals are often in conflict with each other. Agile methodologies (such as scrum) try to help balance this tension by encouraging active conversation between business and development, and continuously delivering working software that is flexible and adaptable to change. In the shops where I’ve seen agile development fail to deliver, I’ve noticed the following 3 bad habits

Navigating I/O Flows/Networks to Enhance the Governance Management Cycle
Since its legacy versions, COBIT has explained the relationships among activities in several processes systematically and organically, showing I/O flows/networks, which is one of the strongest points of difference from other frameworks, guidelines or standards. However, COBIT 5 has transformed its I/O flows/networks, changing the unit of I/O relationships from processes in COBIT 4.1 to management practices. Thus, I/O flows/networks to support the governance management cycle must be traced back to processes as outlined in the conceptual model of business case processes in the article “The Business Case as an Operational Management Instrument—A Process View”6 (the “article”)

What Lies Beneath the Data Lake
Closely related to the quality issue is data governance. Hadoop’s flexible file system is also its downside. You can import endless data types into it, but making sense of the data later on isn’t easy. There’s also been plenty of concerns about securing data (specifically access) within Hadoop. Another challenge is that there are no standard toolsets yet for importing data in Hadoop and extracting it later. This is a Wild West environment, which can lead to compliance problems as well as slow business impact. To address the problem, industry initiatives have appeared, including the Hortonworks-sponsored Data Governance Initiative.

Scotched eggs: Is this the death of the Easter egg?
Easter eggs have not undergone the same levels of scrutiny of the rest of the code, he says, and there may be vulnerabilities attached to them. "They still happen, but they're less likely to be little bits of code, more likely to be hidden in documentation or code comments," adds Brendan Quinn, a software architect in London. "Actual executable stuff hidden in code is something that people are trying to eliminate. With varied success around the industry." The argument goes if a manufacturer can't stop developers from sneaking in benign undocumented features in, how can you be sure they've not inserted a backdoor, too.

The interoperable Enterprise
IT customers have each experienced the frustration of trying individually to get key IT suppliers to fix this problem. Many have also tried collaborative efforts, both within their own industry and across industries, to marshal collective procurement $ to bring pressure on the supply side. Also for too long IT suppliers have had to deal with large lists of vague and ambiguous requirement statements. ... To further these aims, The Open Group is evolving this business scenario that describes the problem caused by the lack of interoperability. The Open Group will use this business scenario to achieve convergence around the real business issues that IT suppliers should be addressing on behalf of their customers, and to set in motion an empowered team of our technical champions to work with The Open Group in setting the standards agenda to address these problems.

Toolkits for the Mind
Switching languages altogether wasn’t an option. Facebook had millions of lines of PHP code, thousands of engineers expert in writing it, and more than half a billion users. Instead, a small team of senior engineers was assigned to a special project to invent a way for Facebook to keep functioning without giving up on its hacky mother tongue. One part of the solution was to create a piece of software—a compiler—that would translate Facebook’s PHP code into much faster C++ code. The other was a feat of computer linguistic engineering that let Facebook’s programmers keep their PHP-ian culture but write more reliable code.

The Hierarchy of Needs for Analytics
We see too many organizations that achieve success with one minor analytics project and then try to live off that glamour, like middle-aged suburbanites reminiscing about that epic night out in college. What these companies really need to do is scale their analytics efforts – turn that one success into the first of many. In order to do that, there are series of steps an organization must take, and certain needs that must be met. You may be familiar with Maslow’s Hierarchy of Needs, developed to explain the needs of the human race in pyramid form, from the most basic to the most advanced. In that spirit, we’ve developed our Hierarchy of Analytics Needs.

Make sense of cloud service brokers
That lack of consistency is frustrating. It's easy to define the business case. However, it's not easy to map that to the providers. Despite the differences in what each offers, CSBs clearly have a great deal of value if you use them appropriately: providing a common mechanism to access public and private cloud computing services, ensuring that these services are both cost-effective and deliver as expected. I hope some CSB standards will emerge; that would help the industry gain more traction. I know this space will change a great deal in the next few years, so today's selection might not be right tomorrow. Choose carefully, and be able to change your CSB approach in the future.

Fifteen Years of Service-Oriented Architecture at Credit Suisse
The sheer size of the landscape, the technical and architectural heterogeneity, and the need for dynamic development and tight integration create a very challenging environment for application integration. Credit Suisse strategically responded to these challenges by placing integration architecture in the spotlight, emphasizing the decomposition of the overall IT system into clearly defined subsystems decoupled through SOA.2 This article reports on Credit Suisse’s journey over the past 15 years. Why 15? Because 15 years ago, two events fundamentally challenged the traditional enterprise architecture: one, there was a need to replace existing systems because they had reached the end of their useful life cycle, and two, it became clear that, with the Internet, banking services had to be offered via new technical channels that were largely

Quote for the day:

“The task of leadership is not to put greatness into humanity, but to elicit it, for the greatness is already there.” -- John Buchan

No comments:

Post a Comment