John Simmons HyperText

You are here: Home / Helpful Articles

How the Prince and the Pauper both got the website they needed

By

Once upon a time, there was a Prince and a Pauper. The Prince was wealthy and successful enough, but knew that he could become the king with a highly focused digital marketing presence, one that allowed him to rule all of the land even before his IPO. The Pauper also needed a good digital marketing presence so that he could stop being a Pauper and at least become a noble person.

The Prince sought out the wisest consultant in all the land, and discovered that his local Web Cobbler was actually a WP Elevation Certified consultant who could help him align his deepest desires and transform them into marketing magic. He had to make a fair investment in time and money, but the results were worth it, and soon his website functioned like a golden goose, and he was more successful than ever, turning not lead, but leads into gold. His castle flourished, and he could afford to add on the ultimate man cave and she shed.

The Pauper said to himself, “Oh if only I could obtain the highly focused work of that Web Cobbler, and obtain golden eggs for myself, but alas, I am a Pauper, and must bootstrap my lowly solopreneur startup with minimal funds, while sticking to the principles of the “profit first” book, so that my accountant does not cast me into the debtors austerity.”

The Web Cobbler, overhearing the sighs of the Pauper said, “You know, I have a product just for you, that will not drain your coffers, or make your accountant groan. I have an AI wizard that will create a site for you in minutes based on your business type. All you have to do is edit content and images, and you too can begin climbing the beanstalk of success. While it may not have all of the nuances of the Prince’s site, it will serve you well to get you going. And I will always make available a clear upgrade path to you when you are ready.

The Pauper said, “Oh, edit it myself? What if it is too hard or I get stuck?”

The cobbler said, “I think you will find it pretty easy, seeing that you already can use the yon word processor, but if you get stuck, or have questions, help is always available. In fact, the first bit of help is free!”

The Pauper was pleased and told the cobbler to set him up. In no time at all, he was up and running, and he left the impoverished village where he lived, promising to come back and help all of the other villagers when he could.

At long last, the Prince became a king, and the Pauper became a noble in his court. The king offered to make the web cobbler a permanent member of his court (with pre-IPO stock options!), but the cobbler declined, saying, “No thanks, I do well enough, and I have to be here to help the next Prince and Pauper when they come to town. And look! here they come now!”

Both Princes and Pauper can get what they need: Start Here!

https://biz-on-ramp.com

Only need a simple website? – An AI can build your site in 2 minutes!

By

I major in building websites that are highly-focused digital marketing presences. These require a serious analysis of your offerings and potential customers in order to position your business precisely.  While I maintain that this is the best approach to creating a lead generating machine, there are some businesses for which this is overkill:

  • A solopreneur with no startup capital, trying to bootstrap a business from the ground up.
  • A simple or local retail shop that basically needs an online brochure to let their customers find them.
  • A small cottage industry that only needs very simple eCommerce, such as an online store.

If you are in one of these categories, I have developed a simple and inexpensive way to get up and running quickly.  An AI bot that can take your basic business information and build you a site in about 2 minutes!

Unlike other similar offerings with simple automated site creation, I offer three very important features:

  • Professional help to start with, and when you need it later
  • The ability to get the same professional content as high-end sites, when you want it.
  • A painless path to upgrade to enterprise-grade sites when you are ready to go from simple startup to pro IPO.

If you have been holding off on your website due to expense or complexity, check out the new offering:

https://biz-on-ramp.com

DocOps: Technical Communication is becoming more agile.

By

[markdown]

I have written a few manuals for companies in the wafer fab research and development space, e.g. , Silicon Valley companies that *actually do something with silicon!* These tend to be older industries, with older engineers and conventions. They like their technical manuals delivered in MS Word. I deliver in Word to these folks, but the documentation usually starts getting written in something more modern.

While I love projects that touch real silicon, I have become more interested documentation that crosses my system administration and software roots in the [DevOps world](https://devops.com/).

###DITA is still popular

A lot of technical communications departments are using XML. [Docbook](http://docbook.org/whatis) has largely given way to [DITA (Darwin Information Typing Architecture)](http://www.xmlmind.com/tutorials/DITA/). DITA is custom made for Tech Pubs and Reuse. Topics, Concepts, Tasks, References & Glossentries are strongly typed and validated snippets of technical information which are assembled as manuals, help systems or other documents as needed via a book map or map. The XML transforms into whatever content type or style is needed. The benefit is highly resuable technical writing.

This method has both [benefits and costs](http://idratherbewriting.com/2015/01/28/10-reasons-for-moving-away-from-dita/). The agility of snippet reuse does not alway translate into agility of writing, or of being in sync with developer flow. It also tends to isolate Tech Pubs from overall development. The trend in development is agile teams using tools like GitHub, and [integrating technical writers into agile teams](http://idratherbewriting.com/2017/01/28/technical-writing-trends-for-2017/).

###DocOps will take over in 2017

The latest expression of this trend was demonstrated by Andrew Etter of Palantir, who [gave a talk on Modern Technical Writing at the Society for Technical Communications Silicon Valley Chapter last month](https://www.youtube.com/watch?v=NmyvIB7zL8o) and also [published a book with the same title](https://www.amazon.com/Modern-Technical-Writing-Introduction-Documentation-ebook/dp/B01A2QL9SS).

Etter’s approach anticipated my own: Write Snippets in a lightweight markup language like Markdown, use the same git or GitHub repositories as developers, and transform/convert the documentation into whatever formats are needed. This approach creates the same benefits as formal DITA, without the added expenses, isolation or bottlenecks (of course [even markdown can be converted to DITA topics](https://github.com/jelovirt/dita-ot-markdown)).

The agile development in technical documentation is getting called DocOps, to match the blurring of lines between development and IT in Devops. [Check out this article on the DocOps trend](https://www.liquidplanner.com/blog/the-docops-trend-applying-agile-and-devops-to-technical-documentation/).

[/markdown]

Corporate Writing Doesn’t Have to Sound Like It’s Written by Committee

By

We’ve seen this phenomenon at work: perfectly lucid writing being turned into unintelligible hash.  Dilbert creator Scott Adams even turned this tendency into the ultimate prank. I knew a pastor who had a plaque on his wall that read “For God so loved the world, that He didn’t send a committee.”

In the Harvard Business Review this month, is a piece that addresses this tendency, and ways to fix it.  The usual suspects are involved: roles that are not clearly defined, and management structures that impose conflict rather than clarity.  There are some gems in this piece, so be sure to give it a look.

Documentation Avoidance for Programmers!

By

“This past week on the WTD Slack forum, there was a bit of discussion around a recent presentation titled ‘Documentation Avoidance for Programmers.’ In the presentation, Peter Hilton lays out a series of tips on how programmers might get out of writing documentation.”

Some of these are funny enough to end up in a Dilbert strip, like saying, “It’s on the wiki” (even when you know it’s not).

And then there are more practical ideas, such as “getting others, namely technical writers to create the documentation.”  This is a great idea! Not only do most developers hate writing documentation, but they often aren’t very good at it, since their investment in code does not always translate to good documentation.

Programmers and engineers would usually rather be coding and building things instead of explaining them to others. With documentation, it can take a lot of effort and multiple tries before you get the organization and flow of logic just right and because “experts are hampered by the curse of knowledge. They know too much and can’t identify the assumptions, needed knowledge, and other building blocks of basic that users need.”  A good technical writer can develop documentation that is audience specific, including developer documentation.

For a good programmer, writing documentation is a secondary skill at best. More importantly, it is a waste of a good programmer’s time.

The only thing worse than using a developer to write documentation, is using an engineer to write marketing materials.  I’m sad to say that this also happens! With a few exceptions, you end up with lesser marketing materials, and have wasted expensive engineering hours to do it.  It is better for a seasoned writer to get the engineers input, and then deliver a great product so that the engineer has time to do the same.

The latest web ui fad, until you are sick of it, and then what?

By

It has become apparent that UIs and Web pages benefit/suffer from fashions nearly as much as clothing!  While Steve Jobs and Mark Zuckerberg may have eschewed fashions in favor of zen simplicity, most of the world wants a refresh in what they wear and look at.  Thus as intuitively simple skeuomorphic interfaces gave way to flat and colorful, it didn’t matter that UI guru Jakob Nielsen complained that the flat interface reduced discoverability and led to low information density.  There are other points of contention, and flat interfaces have their selling points in a responsive universe.

But while interfaces change to adapt to new technology, it is also possible that people just want something new to look at.  MacOSX Aqua seemed cool when it first became available, and Apple tried to go after countless attempts to rip it off.  But now it does look dated.

Web UIs seem to suffer more than anything else. It seems like just when a convention yields fast clean easy UIs, a new fad or technology comes in and wipes it out.  One hot fashion that I am completely sick of is “Infinite Scrolling”. I can see the arguments in favor – simplicity, a single action and point of focus, and ease in delivering the single call to action.  But it was only a few years ago that web pundits advised against forcing people to scroll. Even Nielsen has warned that this is not a good idea in several instances.

Here is an article explaining 7 reasons why Infinite Scrolling is probably a bad idea.  Of course it is a bad idea, except when it isn’t! There is no such thing as one size fits all.  Consideration of audience, content and usability should be part of every design.  Usability testing is always a good idea.

Necessary Evils with Moving Parts: Inkjet Printers

By

One of my tiny niches in the support arena, is local desktop support. A large amount of that is getting a printer to work or getting a machine to work with a printer. Multifunction printers have become a standard piece of equipment, but have some very nice features. You can now print from nearly every device and from anywhere on the internet.

But even without moving parts, these machines tend to be a source of frustrations and problems. It is sometimes worth upgrading to a laser printer, but not in every case. People often ask me what they should buy. Many years ago, I considered HP to be the gold standard, but their quality slipped alongside general company woes. Five years ago, I would have recommended a Canon, and they have done some good engineering, but now you can’t always rely on every model to be a winner from them either.

The evaluation of printer quality is a moving target. Therefore, it is best to do fresh research when looking to do a purchase or a replacement.

Here is a nice list put together by Best Reviews that is a good starting place if you are in the market for a new multifunction inkjet.

…..And despite the scare tactics from printer companies who claim that any other ink cartridge then their own will destroy the printer, I still buy third party ink at places like Cartridge World.

Miscommunicated requirements is top issue for distributed teams

By

I use Sococo Teamspace as one of my means of online collaboration.  Sococo has recently conducted a survey about the issues that plague distributed teams, especially in a cross-cultural context.  You can read the article here, but one chart stood out in my mind:
miscommunicated_requirements“Miscommunication about requirements” is the top issue, and “Different views on quality” also caught my attention. All of these problems can be dealt with, but those two require a special effort to communicate.

Philip Crosby, and his “zero defects” definition of quality, understands that requirements and quality are inherently linked as follows:

  1. Quality is defined as conformance to customers’ requirements
  2. The system for improving quality is prevention
  3. The performance standard is zero defects—a commitment to conform to requirements
  4. The measurement of quality is the price of quality.

This means one of the biggest issues in development by a distributed cross-cultural team can be dealt with by clarifying requirements. The functional and/or technical specification document can be part of the means of clarification of both requirements and quality.  By making sure that requirements are clear and understood, major issues can be resolved.

It is possible to adapt a functional specification for a variety of cross-cultural situations and also various agile methodologies.

Telling the story of your requirements in a functional specification is one of the things I can help you with. See my Tech Pubs page and contact me for ideas!

How to get started using Opensimulator

By

If you have been perusing my 3D Web page, you know that Opensimulator is a piece of technology that I have been investing time in and keeping my eye on.  I have links to some rudimentary instructions for getting online/in-world, but there is also a good introduction on the Hypergrid Business blog.

Hypergrid Business is a primary source for seeing what business and education are doing in OpenSim.

Check out this article: What is OpenSim?

LinkedIn
LinkedIn
Share
Facebook
Twitter
RSS