Five Ways Data Can Help Prevent Major Incidents – DZone Big Data

Regardless of how hard you try, major incidents will occur. How you use major incident data will determine how much of an impact an incident will have on your business, your customers, and your revenue. The last step that should be in your MIM process is arguably the most important: prevention.
However, your organization can affect how often major incidents occur and how impactful they are. All the mitigating actions you take come down to collecting, sharing, and using data effectively.
How you use data has a fundamental impact on five key activities:

  1. Recognize and respond.
  2. Triage and restore.
  3. Resolve.
  4. Collect information and review.
  5. Prevent.

Regardless of how hard you try, major incidents will occur. How you use major incident data will determine how much of an impact an incident will have on your business, your customers, and your revenue. The last step that should be in your MIM process is arguably the most important: prevention. However, your organization can affect how often major incidents occur and how impactful they are. All the mitigating actions you take come down to collecting, sharing, and using data effectively. How you use data h

Source: Five Ways Data Can Help Prevent Major Incidents – DZone Big Data

The Complete Guide to Remembering What You Read – Better Humans

How Memories Are Created

There are two types of memories:

  1. Memories you make a conscious effort to form.
  2. Memories you form unconsciously through experience.

The first type of memory is stored in your hippocampus. It’s what happens when your new neighbor John introduces himself to you and you go: “John, John, John, John, John…” in your head, over and over again, to not forget it.

The second type is stored in your neocortex. When you went to Disneyland with your grandparents for the first time, got ice-cream, it fell on the floor, and the nice lady behind the counter gave you a new scoop, this experience ends up there.

Source: The Complete Guide to Remembering What You Read – Better Humans

PowerBuilder Legacy Modernization | PB Application | FAQ

What is ModernizeNow? How do I engage SoftSol to migrate my PowerBuilder applications?

  • SoftSol is well-known as a leader in software modernization solutions—the partner of choice for leading public and private-sector companies like the US Department of Defense, HBO, Genentech, and CalPERS.
  • With ModernizeNow, companies can now take advantage of these same proven tools and approaches through an easy-to-use, low-cost, lighting fast, web-based service. While previously companies may have felt migration only made sense for large-scale, critical applications, ModernizeNow makes it simple and cost effective to migrate both small and medium-sized PowerBuilder applications to web-based Java or .NET platforms.
  • Simply sign up for an account, upload your selected code, and indicate your preference for either .NET or Java. Within 48 hours, we’ll send you a secure link where you can view and test your migrated application at no cost or obligation. If you are fully satisfied with the results, you can decide to purchase the migrated code.
  • ModernizeNow is ideal for small to medium-sized applications requiring 1:1 migration. If you are looking to make substantial enhancements to the application during the modernization process or if you would like to customize the architecture component mapping, contact SoftSol and one of our Solutions Architects will work with you to design a solution tailored to your unique requirements.

Source: PowerBuilder Legacy Modernization | PB Application | FAQ

10 Algorithms and Programming Courses to Crack Coding Interviews – DZone Agile

To be honest with you, getting your first job is never easy. It is, in fact, one of the hardest things in your life and you need to put your best effort to find a job in your dream company. Most of the computer science graduates dream of working for GoogleFacebookAmazonMicrosoft, and Apple but only a few programmers clear their difficult coding interviews.
The single most important reason for failing those coding job interviews is the lack of knowledge and practice. If you don’t don’t know much about what to learn then you are bound to fail, hence it becomes increasingly important that you prepare hard in advance.
Unfortunately, I learned this a little too late, after spoiling my chances at Microsoft and Amazon, but you don’t need to. You can learn from my experience and prepare better for your programming job interviews.
So, the big question is, how do you prepare for coding/programming job interviews? Which subjects should you read up on? Which questions will you need to solve? How do you deal with coding and other technology related questions?
When I was hunting for my first job there wasn’t much help available; we were totally reliant on our textbooks of programming languages and data structure to prepare for interviews, but things have changed in last 10 years.

Source: 10 Algorithms and Programming Courses to Crack Coding Interviews – DZone Agile

Cognitive bias cheat sheet – Better Humans

Sounds pretty useful! So what’s the downside?

In addition to the four problems, it would be useful to remember these four truths about how our solutions to these problems have problems of their own:

  1. We don’t see everything. Some of the information we filter out is actually useful and important.
  2. Our search for meaning can conjure illusions. We sometimes imagine details that were filled in by our assumptions, and construct meaning and stories that aren’t really there.
  3. Quick decisions can be seriously flawed. Some of the quick reactions and decisions we jump to are unfair, self-serving, and counter-productive.
  4. Our memory reinforces errors. Some of the stuff we remember for later just makes all of the above systems more biased, and more damaging to our thought processes.

Source: Cognitive bias cheat sheet – Better Humans

Cognitive bias cheat sheet – Better Humans

Great, how am I supposed to remember all of this?

You don’t have to. But you can start by remembering these four giant problems our brains have evolved to deal with over the last few million years (and maybe bookmark this page if you want to occasionally reference it for the exact bias you’re looking for):

  1. Information overload sucks, so we aggressively filter. Noise becomes signal.
  2. Lack of meaning is confusing, so we fill in the gaps. Signal becomes a story.
  3. Need to act fast lest we lose our chance, so we jump to conclusions. Stories become decisions.
  4. This isn’t getting easier, so we try to remember the important bits. Decisions inform our mental models of the world.

Source: Cognitive bias cheat sheet – Better Humans

Design Thinking for Enterprise Architects – A Conversation with Mayank Saxena – The Open Group Blog

There’s been a lot of talk lately in the tech industry about Design Thinking. What is Design Thinking, and how do you define that term?
There are two aspects in the presentation I’m giving in Singapore, and that is talking about digital and talking about design thinking. The goal is to stitch them together and put an architectural overlay on them.
My premise is that, when we speak about digital, which has become a new fad word, we’re not doing something different. If I speak to one person, they’re talking about business transformation. If I speak to another, they’re talking about digital transformation. But underlying all these transformation efforts, we’re doing the same thing and that is providing value to the customer, as well as how that value is generated changes in wake of innovations available today.
There are two ways to provide this value. One being outside-in and other inside-out. Outside-in is about gathering outside experiences inside the organization like the brand experience, customer perception, etc. And inside-out is about when organizations typically go into reinventing their own processes to realize outside expectations.

Source: Design Thinking for Enterprise Architects – A Conversation with Mayank Saxena – The Open Group Blog

Ten Immutable Laws Of Security (Version 2.0) – Roger's Security Blog


You might have known the 10 Immutable Laws Of Security since quite a while. It is kind of the “collected non-technical wisdom” of what we see in security respeonse being it in Microsoft Security Response Center or in our Security Product Support.
There is now a version 2, which is still as important as version 1 was. The 10 Laws are:

Law #1: If a bad guy can persuade you to run his program on your computer, it’s not solely your computer anymore.
Law #2: If a bad guy can alter the operating system on your computer, it’s not your computer anymore.
Law #3: If a bad guy has unrestricted physical access to your computer, it’s not your computer anymore.
Law #4: If you allow a bad guy to run active content in your website, it’s not your website any more.
Law #5: Weak passwords trump strong security.
Law #6: A computer is only as secure as the administrator is trustworthy.
Law #7: Encrypted data is only as secure as its decryption key.
Law #8: An out-of-date antimalware scanner is only marginally better than no scanner at all.
Law #9: Absolute anonymity isn’t practically achievable, online or offline.
Law #10: Technology is not a panacea.

Source: Ten Immutable Laws Of Security (Version 2.0) – Roger’s Security Blog

Software-defined data center – Wikipedia

Software-defined data center (SDDC; also: virtual data center, VDC) is a marketing term that extends virtualization concepts such as abstraction, pooling, and automation to all data center resources and services to achieve IT as a service (ITaaS).[1] In a software-defined data center, “all elements of the infrastructure — networking, storage, CPU and security – are virtualized and delivered as a service.”[2] While ITaaS may represent an outcome of SDDC, SDDC is differently cast[by whom?] toward integrators and datacenter builders rather than toward tenants. Software awareness in the infrastructure is not visible to tenants.
SDDC support can be claimed by a wide variety of approaches. Critics see the software-defined data center as a marketing tool and “software-defined hype,” noting this variability.[3]
In 2013, an analyst[which?] projected that at least some software-defined data center components would experience market growth. The software-defined networking market is expected to be valued at about USD $3.7 billion by 2016, compared to USD $360 million in 2013.[3] IDC estimates that the software-defined storage market is poised to expand faster than any other storage market.[3]

Source: Software-defined data center – Wikipedia