Voice recordings are useful at any point in time. If you want to save a lecture (or presentation) that you are attending, or record a voiceover for a project, the iPhone can be your solution. You don’t have to use an old tape recorder, or a standalone recorder. The iPhone’s fantastic technology records high quality voice recordings on demand, whenever you need it.

To get started, look for an application named “Voice Memos.” Most likely, this particular application is found in your Utilities category by default. Once you open it up, you are greeted by a large microphone, indicating you are in the correct application. When you want to start recording, simply tap on the large red button in the bottom left, and you are on your way to begin recording. What is important about recording voices on this application to the highest degree of quality, ensure that your meter in the bottom is within the middle range; with the pointer in the red zone, your recording will be awfully loud, while otherwise, it will be too quiet. Finished recording? Simply tap on the square button, and you have your recording.

What can you do with these recordings? Once you have finished recording, you are able to now share this recording through email or even in a text message; email it to yourself so you can save it on your computer, and listen to it later, or start editing it to put into a movie production, or text it to a friend for their needs.

Structure Rule Language

To aid in the ease of rule authoring, Blaze Software, now Fair Isaac, created the proprietary Structure Rule Language (SRL), an object-oriented programming language designed to enable those with little or no background in software development to pen rules. Although the capabilities of this language are far too extensive to detail in this article, we can examine the basic rule syntax.

Rules in the SRL take the following form:

rule RuleName [at | priority M] is

The interpreted programming language Python has surged in popularity in recent years. Long beloved by system administrators and others who had good use for the way it made routine tasks easy to automate, it has gained traction in other sectors as well. In particular, it has become one of the most-used tools in the discipline of numerical computing and analysis. Being put to use for such heavy lifting has endowed the language with a great selection of powerful libraries and other tools that make it even more flexible. One upshot of this development has been that sophisticated business analysts have also come to see the language as a valuable tool for those own data analysis needs.

Greatly appreciated for its simplicity and elegance of syntax, Python makes an excellent first programming language for previously non-technical people. Many business analysts, in fact, have had success growing their skill sets in this way thanks to the language's tractability. Long beloved by specialized data scientists, the iPython interactive computing environment has also attracted great attention within the business analyst’s community. Its instant feedback and visualization options have made it easy for many analysts to become skilled Python programmers while doing valuable work along the way.

Using iPython and appropriate notebooks for it, for example, business analysts can easily make interactive use of such tools as cohort analysis and pivot tables. iPython makes it easy to benefit from real-time, interactive researches which produce immediately visible results, including charts and graphs suitable for use in other contexts. Through becoming familiar with this powerful interactive application, business analysts are also exposing themselves in a natural and productive way to the Python programming language itself.

Gaining proficiency with this language opens up further possibilities. While interactive analytic techniques are of great use to many business analysts, being able to create fully functioning, independent programs is of similar value. Becoming comfortable with Python allows analysts to tackle and plumb even larger data sets than would be possible through an interactive approach, as results can be allowed to accumulate over hours and days of processing time.

This ability can sometime allow business analysts to address the so-called "Big Data" questions that can otherwise seem the sole province of specialized data scientists. More important than this higher level of independence, perhaps, is the fact that this increased facility with data analysis and handling allows analysts to communicate more effectively with such stakeholders. Through learning a programming language which allows them to begin making independent inroads into such areas, business analysts gain a better perspective on these specialized domains, and this allows them to function as even more effective intermediaries.

Related:

Who Are the Main Players in Big Data?

It’s the eternal conundrum of a hiring manager – you have to hire for every single position in the company without any first-hand experience. How to do it? If you can have a trusted programmer sit in on the interview, that’s ideal, of course. But what if you’re hiring your first programmer? Or what if you’re hiring a freelancer? Or what if company policy dictates that you’re the only person allowed to do the interviewing? Well, in that case, you need some helpful advice and your innate bullshit detector. We questioned programmers and hiring managers and compiled a list of dos and don’ts. Here are some things to ask when interviewing programmers:

Past Experience

Ask the programmer about the biggest disaster of his career so far, and how he handled it. Did he come in at midnight to fix the code? Was he unaware of the problem until someone brought it up? Did someone else handle it?  According to our programmer sources, “Anyone worth their salt has caused a major meltdown. If they say they haven’t, they’re lying. Or very, very green.” Pushing a code with bugs in it isn’t necessarily bad. Not handling it well is bad.

As usual, your biggest asset is not knowing the field, it is knowing people. Asking about career disasters can be uncomfortable, but if the interviewee is experienced and honest then she won’t have a problem telling you about it, and you will get an idea of how she handles mishaps. Even if you don’t understand what the disaster was or how it was fixed, you should be able to tell how honest she’s being and how she handles being put on the spot.