Archive for RB

Coffee Could Save Your Life

A team of German researchers reports that four cups of strong coffee a day might be the recipe for a healthy heart, especially for older adults. The researchers think they have discovered how coffee improves heart health and how much caffeine we should drink each day to see the best benefits. The researchers studied how a jolt of caffeine could improve the way cells inside our blood vessels work — essentially, by making certain proteins inside older adult cells perform more like young and nimble ones.

coffee improves heart healthThe researchers found that caffeine promotes the movement of a protein called p27 into mitochondria in the heart. The study was published in the journal PLOS Biology. Study leader and molecular biologist Joachim Altschmied told Business InsiderWhen you drink four to five cups of espresso … that seems to improve the function of the powerhouses of our cells, and therefore seems to be protective.”

Scientists have for years noticed that coffee drinkers seem to be less likely to die from all sorts of causes, including heart disease, stroke, or diabetes. Perhaps the best evidence yet for this comes from two massive studies: one of more than 400,000 people in the US by the National Institutes of Health, and another of more than 500,000 Europeans. Both studies found that regular coffee drinkers were less likely to die from any cause than people who don’t regularly drink coffee.

People who drink coffee seem to be less likely to die from heart diseaseCoffee is also associated with a whole host of other health benefits, including a lower risk of liver disease (cirrhosis), a lower risk of developing certain kinds of cancer, lower rates of dementia and Alzheimer’s, and a reduced risk of depression. It’s also great for your heart — people who drink three or four cups a day may be 19% less likely to die from cardiovascular disease.

Mr. Altschmied said that drinking the equivalent of about four shots of espresso a day could help reduce the risk of heart attacks, especially for people who are obese or prediabetic. He told BI that coffee can help some peopleIt will not replace other things … Keep on doing your sports, eat healthy, and add coffee to your diet.

BI says you could try green tea if you don’t drink coffee. Green tea has similar levels of caffeine and could also be an effective way to boost heart health.

It’s important not to overdo it with the new recommendation, as too much coffee can quicken your heartbeat and cause other health problems the article warns. But drinking up to six cups a day should be OK, cardiologists say, and may even reduce arrhythmias in people with irregular heartbeats.

One caveat: What works in a hypercontrolled test environment for mice, may not be the same results as what happens when you drink a cup of joe at home. Mr. Altschmied said, “If I had four cups of espresso and you had four cups of espresso, we cannot guarantee that we reach the same level in the blood.

He also cautioned that the coffee-drinking advice might not hold for people who have cancer. He explained that caffeine can make blood vessels grow, providing more oxygen to fuel tumors.

rb-

Sounds to me that a couple of cups of coffee are not only good, but they are also good for you. Our ol’ friend Joe will not harm you, and it might help your heart and circulatory system stay work better for a longer time.

Related article

 

Ralph Bach has been in IT long enough to know better and has blogged from his Bach Seat about IT, careers, and anything else that catches his attention since 2005. You can follow him on LinkedInFacebook, and Twitter. Email the Bach Seat here.

 

The Lost Art of Effective Flow Charts

The Lost Art of Effective Flow ChartsPracticing project managers know that there are many times when reality clashes with the PMI world. One of the real-world PMI visions of PM life is the “Business Analyst” role. Despite what the Project Management Institute (PMI) thinks, PMs have to do other jobs. One of the “non-PM” jobs I often have to take on is “Business Analyst.” and one of the Business Analyst tools I often use are flow charts.

Flow chartYes, the flow charts that we learned about in high school Basic computer programing class. The flow chart can help you communicate with your business users better. A well-done flow chart can describe and break down a process for easier explanation and help you improve a process. More importantly, creating a flow chart helps you understand the process and look for improvements.  It also helps you focus on each individual step, without feeling overwhelmed by the bigger picture.

Flow charts are one of the 7 basic Tools and Techniques called out in the PMBOK Project Quality Management knowledge area. The other PMBOK Quality Management tools and techniques are histogramPareto chartcheck sheetcontrol chartcause-and-effect diagram, and scatter diagram. (rb- Know this for the PMP exam)  The is an ISO standard for flow charts, ISO 5807:1985 – Information processing — Documentation symbols and conventions for data, program and system flowcharts, program network charts, and system resources charts for $120.00 US.

Flow Chart Basics – To draw a flowchart, develop a list of the tasks and decisions made during a process, and write them down in order. Enter the purpose (start/stop/decision/etc.) of each symbol within the shape and connect them with arrows to show the direction of the flow.

Flow Charts are usually drawn using standard symbols; however, some special symbols can also be used when required. If you use non-standard symbols people may not understand them and you will fail to clearly communicate your message. Below are some commonly used symbols for charting processes…

Start - StopUse this shape to represent an event which occurs automatically. Such an event will trigger a subsequent action, for example 'receive telephone call', start or stop.
ProcessUse a rectangle to represent an event which is controlled within the process. Typically this will be a step or action which is taken. In most flowcharts this will be the most frequently used symbol.
Connector
Use a line with an arrow to indicate the direction of the process flow.
DecisionUse the diamond shape to represent a decision point in the process. Typically, the statement in the symbol will require a 'yes' or 'no' response and branch to different parts of the flowchart accordingly.
SubroutineThis shape is used to represent a pre-defined process. The text in the shape should be a descriptive name of the process it represents. The process that it represents must be defined elsewhere.
DocumentFlowchart Document SymbolUse this shape to for a process step that produces a document.
PauseThis shape is used to indicate a waiting period.
On page linkUse a pair of circles to replace long or confusing lines on a flowchart page.  The name or reference for the other process should appear within the symbol.
Off page linkUse this shape to represent a point at which the flowchart connects with another on another page . The name or reference for the other process should appear within the symbol.

The following are some flowcharting tips:

  1. Keep it simple
  2. Begin by listing each step of the process using the symbols above – just put your ideas on paper (screen?) and correct them from there. It will surprise you how much you learn about your organization in this process.
  3. The usual direction of the flow is from left to right or top to bottom.
  4. Put an arrowhead on the flow line to show the decision process.
  5. Only one flow line should come out from a process symbol.
  6. Only one flow line should enter a decision symbol, but two or three flow lines, one for each possible answer, should leave the decision symbol.
  7. Only use one flow line in conjunction with the terminal symbol.
  8. Use only brief descriptions in standard flow chart symbols. If needed, use an annotation call-out to describe the step more clearly.
  9. Use two on-page reference symbols to cut the number of flow lines in a complex diagram.
  10. Avoid crossing flow lines.
  11. Ensure that the flowchart has a logical start and finish.
  12. Challenge your flow chart to make sure that it’s an accurate representation of the process.

You can use Microsoft (MSFT) Visio, Word, or even Excel to build flowcharts. There are a number of flow chart creation tools online – Draw.io, Pencil Project (“free”) Gliffy online (“free”).

rb-

flow charingYou can use the flow chart as a process improvement tool. Make sure that it represents the current state and then you can use it to discuss changes to the process with your users to make sure it represents the most efficient way of doing the process.

Related article

 

Ralph Bach has been in IT long enough to know better and has blogged from his Bach Seat about IT, careers, and anything else that catches his attention since 2005. You can follow him on LinkedInFacebook, and Twitter. Email the Bach Seat here.

RIP Yahoo Messenger

Do yRIP Yahoo Messengerou remember Yahoo Messenger? It was popular in the late ’90s and early 2000s when there were only two messengers to communicate with your friends and family. Well … the remnants of Yahoo nee Verizon recently announced the end of Yahoo Messenger. Verizon (VZ)/Yahoo announced that they will disable the Yahoo Messenger service after July 17th, 2018. (rb- yes Yahoo Messenger was still a thing – in the face of Apple‘s (AAPL) FaceTime, Telegram, Snapchat, and Facebook‘s (FB) WhatsApp).

According to the Oath website, YIM had 122.6 million users at its peak. In the FAQ announcing the shutdown, Yahoo said, “We know we have many loyal fans who have used Yahoo Messenger since its beginning  … As the communications landscape continues to change over, we’re focusing on building and introducing new, exciting communications tools that better fit consumer needs.” If you’re looking for a Messenger replacement from Yahoo, they recommend Squirrel, which is in closed beta and by invite only. But why?

YIM leaves a dubious security legacy, as all “free” web products do. In 2007 there were reports that up to 75%  of the users in Yahoo Messenger were SPAMBots. In 2010 all Yahoo systems and customer email accounts were hacked by the Chinese military in “Operation Aurora.” In Operation Aurora the Chinese also attacked Adobe (ADBE)Dow Chemical, Google (GOOG) Juniper Networks (JNPR)Morgan Stanley, Northrop Grumman (NOC)Rackspace (RAX), and Symantec (SYMC).

In 2014 The Guardian reported that The British intelligence agency Government Communications Headquarters (GCHQ)’s secret mass surveillance program Optic Nerve and National Security Agency (NSA) were indiscriminately collecting still images from Yahoo webcam streams from millions of mostly innocent Yahoo webcam users, among other things creating a database for facial recognition for future use. Optic Nerve takes a still image from the webcam stream every 5 minutes. Also in 2014 Yahoo was also hit by a hack that affected around 500 million people.

mass surveillanceIn September 2016, The New York Times reported that Yahoo’s security team, had pressed for Yahoo to adopt end-to-end encryption sometime between 2014 and 2015, but senior leadership resisted, “…because it would have hurt Yahoo’s ability to index and search message data.”

In 2017 Yahoo announced that all of its customer’s accounts were compromised. Allegedly Yahoo did not detect the full extent of the 2013 hack until  4 years later. In 2017, Yahoo announced that all 3 billion accounts were compromised.

YouYahoo can download your chat history for the next 6 months at this download request site. Yahoo will email your chats to you. If you have anything you want to save from Yahoo Messenger, it’s a good idea to get a copy, because users will be unable to sign in to the service after July 17th.

rb-

YIM is not the first long-standing chat app to shut down – AOL Instant Messenger shut down December 15, 2017. But Yahoo Messenger was one of the few old-school messaging services left.

Related article

Ralph Bach has been in IT long enough to know better and has blogged from his Bach Seat about IT, careers, and anything else that catches his attention since 2005. You can follow him on LinkedIn, Facebook, and Twitter. Email the Bach Seat here.

Independence Day 2018

Independence Day 2018

Independence Day

 

Related articles

 

Ralph Bach has been in IT long enough to know better and has blogged from his Bach Seat about IT, careers, and anything else that catches his attention since 2005. You can follow him on LinkedInFacebook, and Twitter. Email the Bach Seat here.

Software Testing and the Project Manager

Software Testing and the Project ManagerShh- don’t tell PMI, but as practicing Project Manager’s we all know that resources are limited. Sometimes the PMBOK process just won’t work. Resources are limited. One of the most limited resources I see is testers. After all, nobody wants to pay for someone to try to break things all day long – That’s what users are for. That is why a Project Manager can find themselves taking on the additional task of validating and testing software.

For the uninitiated, there is a difference in mindset between validating and testing. When you are checking that the finished product meets your project requirements, you are validating.

  • Add a new customer? Check!
  • Edit a customer? Check!
  • Don’t permit deleting customers who have transactions associated with them?

Testing, however, shouldn’t be so structured. And there are some good tricks from Stout Systems that a project manager can rely on to find some bugs.

Software testingDo stupid stuff

When writing code, developers know what kind of data is supposed to go into a field. Good developers will error-check to make sure that stupid data isn’t being entered. But that doesn’t always happen. So when testing, try to enter numbers where letters go or letters where numbers go. Try to enter symbols—especially symbols that are used in programming like the various kinds of brackets <> or {} or () and the various punctuation marks like ! or @ or # or &. (rb– Make your CISO happy and read up on SQL Injection attacks and try a few of them.)

Another stupid thing to do is to be click-happy. Click on one control and then another control before the application has a chance to execute the first action. Impatient users do this all the time, as do users who have mistakenly clicked the wrong place.

Get two copies of the same web page open, delete something from one place, and then try to edit it in the other place. You’ll blow it up most of the time, and get an unintelligible error message.

Open a page up, do nothing, click the SUBMIT button. You should get validation errors that tell you that you didn’t fill in the required fields. But an amazing number of times the application will just blow up on you with another unintelligible error message.

Regression test

One of the most common problems in software development is that adding a new feature causes something else to break. Regression testing is testing what was there before to make sure that it still works—just as it did before. If you were previously able to add, edit, and delete customers—but only if no transactions were associated with them—then by George you should start your testing by making sure that you can still do this.

Regression testThis should include using test records that you created before, too. So you add a new customer, edit the newly added customer… good, still works. Now open up a test customer you created previously. Can you still edit it? Maybe not! The new feature may have added fields to the database. The old records don’t have any information in those fields—but the information is marked as required—and the application cannot handle it.

The author points out that one of the biggest shortcomings she has witnessed in developer testing is that they test the new feature, sometimes with many use cases, but they don’t go back to validate that everything from before still works. It is lazy, lazy, lazy not to have someone on the team regression test the full application unless you are certain that the new features couldn’t have touched the old ones. But…hmm…are you really certain?

validate that everything from before still worksLook at things like a user

Developers are notoriously bad at certain niceties. Deliberately produce error cases and then read the error message that you receive. Is the message in techno-speak or is it easy to understand? Does it have typos? Grammatical errors?

Are the labels for the controls properly spelled? Is the capitalization consistent? The author says she often sees a mix of title case (where nearly every word is capitalized) and sentence case (where only the first word is capitalized). Some developers capitalize every word they think is important. Let’s face it: they didn’t major in English, so they shouldn’t be expected to get these things right. But there is no reason the application should be released widely with such simple-to-fix mistakes.

Look at the user interface itself. Are columns aligned in the layout? Are the margins uniform? If there is a style guide, is it being followed (the right colors, the right fonts, the right point sizes, the right button types, etc.).

Look at things like a userCan you understand what you’re supposed to be doing? Sometimes a simple thing like changing the text used for a label on a control makes a big difference. And sometimes adding a tool-tip with an explanation that’s too long for a label makes a big difference.

Then check out the workflow

Can you actually get around in the application? Or do you need more navigational controls to take you where you want to go? If it’s frustrating to you, then count on it being frustrating to an end-user.

Use IE. The article says most developers prefer Google Chrome, so that’s the browser where all of their testing is done. He makes it a habit to do all of his testing in Internet Explorer. Each browser has peculiarities, so this exposes a number of bugs that developers never encounter. (rb- Will you have control of what browser the users will access your site from? Don’t forget about older versions, Firefox, Safari, IE 9 anybody?)

Its not rocket scienceNone of the things that are described above are rocket science. A good tester is going to do things substantially more like a rocket scientist than a Business Analyst or Technical Writer will ever achieve—test automation, database comparisons, validating data outputs, calculations, etc. But all the areas above, when tested and fixed, go a long way to improving the end user’s experience and acceptance of the released product.

Rb-

This kind of software testing will help the team develop much less fragile or brittle code. That saves a lot of heartache in the long run.

Happy bug hunting!

Related article

Ralph Bach has been in IT long enough to know better and has blogged from his Bach Seat about IT, careers, and anything else that catches his attention since 2005. You can follow him on LinkedIn, Facebook, and Twitter. Email the Bach Seat here.