A new movers list will be coming soon and Thanks!!!!

I am officially done publicly posting about issues and potential workarounds on Virily. The negativity is more than I can take, and frankly, I am moving on.

If I can help you in any way, please send me a message here on Virily. If I can help, I will help. I am not going to post publicly about issues and solutions any longer.

Instead, I am going back to focus on things that are important to me. One of those is the impact of authors on my posts. I have posted the mover list before, based on the current flow on the site, I have shared that list in the past. I will take a look again when the summer gets here and share the list. I am going to modify my criteria a little and will share the new criteria later on b4efore I start the new mover review.

I’ve started looking at other places to share my posts as well. The reality of negativity forces me from time to time to consider other options.

Sometimes you have to consider what your goal is.

Right now, my goal is to share my family history project. I want to share the pictures I have collected from the past. I would also like to share some of the old movies from the 1940s and 1950s that my grandfather took. I suspect I will continue from time to time to publish those on my YouTube channel.  If you liked the When Harry Met Sally post I shared yesterday, I did the extended version on my podcast. You can find that here https://docandersen.podbean.com/e/our-harry-met-sally-story/.To end for today, I want to loop back to Ghostwriter’s Thank you Challenge. I want to extend my original with the following:

Thank you!







And so many others. Thank you for reading. Thank you for commenting.


Wandering down a tech path I should probably stay off of…

I have been sitting out of the “what’s changed” with Virily lately. Partly because I don’t like the nasty comments that come with those posts at times; the other reason being that I am still learning.  As Ghostwriter pointed out, the source of information is critical. I don’t post about the issues and new and exciting new features until I have time to test them.  Recently there are a couple of issues that popped up that I found interesting. So, I did just a small amount of testing to see in fact if it was me or the site having the issue. As a long time computer helpdesk person, I always start with the assumption that the problem is on my side first. That way I don’t have to backtrack if I find out later it isn’t the site itself.

First of all, publishing from drafts. It is an issue that I noticed and began to think about how does that problem manifest itself.  I noticed that when I connected to Virily with Chrome, I was unable to publish a draft. Chrome and Google have changed a couple of security settings in the release they made in April to remove Google + as an option. Those changes, for Chrome, appear to be in how JScript loads. I tried Opera and had no issue publishing drafts. That made me wonder, so, I went back, and disabled add-ins for Chrome. Chrome worked publishing drafts https://www.lifewire.com/disable-extensions-and-plugins-in-google-chrome-4103624 if you want to try that on your computer.

1. Chrome works without add-ins loading, so not sure which add in it is but one doesn’t like Virily.

2. Edge works publishing drafts, but I don’t have any add-ins loaded in the edge.

3. Opera works publishing from drafts

4. Mozilla works publishing from drafts.

5. Safari worked with add-ins loaded.

Now, there is one more issue in this that has to be considered. However, note two verified users were also unable to publish from drafts.  Now, most of us have add-ins and extensions loaded in our browsers. I am not saying that there isn’t a better way. I am simply pointing that by removing all extensions in Chrome, I was able to get a draft to publish (this blog in


Carbon Monoxide Detectors save lives!

Do you monitor the quality of the air in your house? What about the temperature at the various parts of your home that you are in and not in? For example, most days of the year the basement in our house is between 4 and 6 degrees cooler than the main level, In the winter it doesn’t matter because, well we are dressed warmly. In the summer I love it because it is cooler. But in the winter time, air quality matters. It also matters if you shut your house up and run the air conditioning in the summer. The quality of the air you are breathing can cause you to have a weakened immune system and get sick. It is also something that can impact those in your house with allergies.

I have the NetATMO weather stations, based on the system; I use their modules in the basement, main level, and bedroom level of the house. That allows me to verify temperatures, plus check air quality. I also have the one on the main level set to monitor CO. Carbon Monoxide is a colorless odor gas that kills. Every year you hear about people dying from CO poisoning. Knowing, and being able to alarm your house based on a rising CO level is critical! If you do not have a CO alarm in your house, please get one. The life you save is your own. CO detectors should be like Smoke detectors, standard in every house, apartment and recreational vehicle.

(we have a CO monitor in the boat).

The technology to monitor the quality of the air and the presence of contaminants is an interesting study. First of all, the sensors now are much smaller than they used to be. That allows you to have one, two, or even three sessions tucked away in various parts of your house. Have a furnace in your house? Get a CO detector, a furnace in some scenarios can release CO. Have a fireplace, fires generate CO at times. Have a stove? Or an Oven? They also can in certain situations produce CO in your house. While it is easy to forget, it is critical for your health. Next time you are at the store, make sure you buy batteries for your smoke detectors and pick up a CO monitor!!!!


Sometimes failure is an option

Sidebar for the Innovation series a little of the reality of failed innovations. My top list of failed innovations and my perception/opinion as to why they failed!

1. Keecker – homepod integrated speakers and project that rolls around your house. Why did it fail? I don’t think the move away from TV’s has happened quite as quickly as the Keecker team would believe. The reality of creating something that has a robotic control system, as well as integration with android tv, is expensive.

2. Jibo – personal interactions assistant They raised more than 70 million dollars and had a brilliant idea: why did it fail? They didn’t have a market.

3. SingleCue – automation system for your computer but the problem was it lacked integration with much. A small market and the company refocused on the other products they had.

4. Apple Newton, can you be too far ahead of your market? Apple was with the Newton. The revised and delivered the iPad and changed the game.

5. Pebble – the first smartwatch to ship (well the first to start developing the Samsun Gear was the first to ship). Pebble’s issue, the reality of the market. They raised a lot of money on Crowdfunding, but when you penetrate your market and saturate that market, there is no room for growth.

6. Microsoft Bob – the first digital assistant, became Clippy and then disappeared. Except, Bob eventually would become Cortana and then slowly disappear again.

First off, big companies fail. IBM, Microsoft, Amazon, Apple, and others have all launched solutions to the question we didn’t ask. I had a Newton, the one thing that it did better than most of the other devices in that space was handing writing recognition from a stylus. The return of Steve Jobs to Apple killed the Newton forever.

The question when it comes to a great idea, do other people think it is a great idea. My father and before him, my grandfather always used to say, “start off asking ten people if it is a good idea.” Then modify to fit what the ten people thought and go back and ask ten more people. As someone that advises several innovators, I tell them that. It is important that you understand that your market is critical.


More on innovation and use cases…

The concept of language is one that interests me. In part, because over the years, I have been exposed to, but never learned four different languages. The four I’ve spent a lot of time with or around are French, Thai, Malay and Spanish. Of those four, I am more likely to understand Spanish. But, honestly, when Spanish is spoken between two native speakers, I have no chance of translating fast enough. I know that because I’ve tried.  I taught a class in Mexico city once, and a few of the folks in the class asked if they could do their final presentation in Spanish. I had to think about that for a long time. It wasn’t that I figured they were going to curse at me in Spanish, more than I wouldn’t be able to understand fully.

We ended up compromising. One of the team embers wrote down the main concepts of the presentation in English, and I watched the rest of their presentation style. Style points count when you are speaking. If you know your material, people can tell. Then I review the main points with the class from the sheet taken down by the other team member. That bought me additional information, did the lessons taught to make it to the note taker and the speaker. When you are asked, as the class was, to make an impassioned presentation doing it in your native language is much easier overall. Now, I would simply plug in Pilot or Travis and wouldn’t worry about translation!

Technology and innovation continue to evolve. The use case “help me understand Spanish as a non-Spanish speaker” is one that many people want to accomplish or have. Translate languages for me as I move through my day is something that is of value. So to consider the value of translation, we can now bring together two distinct business themes. The first is as mentioned yesterday, a use case. The larger the population of people, the use case supports the other side business die of the problem, the addressable market, increases. You see, if people need and want to use the solution you’ve offered, then your chance of selling your solution increases. The total addressable market is driven by finding use cases that impact a larger group of users. Use cases and total addressable market are critical things for innovators to consider


innovators and use cases…

One of the things I often do in my day job is created use cases. The use cases normally take an idea or a concept[t and push it towards what or how someone accomplishes a task. Use cases are not perfect. For an example, if we took the concept that is Virily, and walked back to the original use case, I suspect that original use case was something like “I want a place to share blogs and pictures easily.” Over time, they, the admin team and development team would then add other functional areas to the site. Use cases for people that didn’t share blogs or pictures. People that like to do polls. Or the people that like to do quizzes. These aren’t additional use cases; they are other functionality.

Use cases often drive to a goal.  One of the things that innovators often miss is the reality of use cases. I have a really good friend that always says there are three types of use cases, my cases, you cases, and us cases. All three are use cases but refer to the type of problem being solved. If you are solving a problem that impacts you, do it! If you intend to solve a problem you have, make sure other people also have the issue. My cases are important; no one likes ongoing issues. But when we love for my case to us case, it becomes more powerful. The US is more than me. That isn’t a diminishing of your problems or my problems overall; it is simply the reality of problems.

The more people that are impacted by a need want, or issue, the larger the potential market is for that overall solution. That is the magic space that innovators want to get to as quickly as possible. The use case they seek is the Us Case. Now, that means sometimes that innovators start with me or you case Where you or if it is me, has a problem that I am trying to solve.  For example, when I used to travel, I always felt bad that I couldn’t speak the language of most of the place I went. The reality of Travis and Pilot, I can now. I also, from a translation aspect, know that being able to comfort a lost child in their native language is often a huge relaxation moment for the child.

That said, the reality of me case was understanding. But a lot of people have that issue. I am making it a US issue.

That is how innovators get products accepted and funded, when they find the US case!


Innovators and failure…

First off, most organizations support the concept of commitment around failure. No one likes it when we fail, and in many cases, we have an organizational desire to move quickly past failure. I think in many cases, there is a great organizational benefit to remembering, recalling, and learning from failure. I’ve had CIO’s and CEO’s tell me I was crazy for saying that but I believe it is true. If you have an organizational failure learning system, then what happens when you fail? You don’t condemn it you learn from it.

Many organizations in the real world also adopt the stop at failure commitment model — very few organizations power through initial failures as de rigor. In the real world, the first two are the models most companies adopt. Failure is a really bad thing.

When you consider the reality of failure in organizations and the commitment that often accompanies that (to and around) it changes the impact on innovation. Just to note, any organization willing to take a risk is supporting innovation, even if they stop at the first failure. This isn’t about stifling innovation.

A commitment to failure forces creative project realignment. If you fail (and we all do at some point), then you have to figure out if your idea has merit and redesign the solution to fit into another project or idea. It’s like a rider attached to a Bill in the US Congress. (Although sometimes the riders attached to the Bill end up being larger than the Bill itself). In this instance, with failure as a wall rather than a fluid part of the project, you end up with a squishier definition of failure. The definition of failure almost becomes a full stop problem. There are few full stop problems that even time can’t solve.

The commitment around failure means you have to consider the risk of failure in your project and have a workaround quickly available. Sometimes this can cause your project to veer off course a little. Clayton Christensen[1] published the innovator’s dilemma several years ago. In that book, he talked about the chosen path of innovation and the actual path being slightly different. He was addressing the concept of commitment around failure, although I doubt that was his intent. It’s my interpretation of his information at this point.

Software Architects, innovation and inclusion

Software Architects are people who consider what is coming when they design what will be there. In those considerations, where does innovation play? Are software architects looking far enough forward to see what may be on the horizon?

Or even should they? Should software architects be looking at the very edge of what is possible? Sometimes past the edge of what we know, things stop being clear.

It’s a balancing act that many software architects struggle with. How far over the horizon should I peak in building my solution. I’ve asked myself and others that question for years. Based on my thinking over the past few months, I’ve put together some simple rules going forward for architects to consider.

[1] Harvard Press “The innovators dilemma” by Clayton Christensen\