What You Can Read on David Yardy PE

David Yardy PE is a consulting site for web and mobile application work, and the reading material on it falls into three areas: technical articles, software delivery insights, and profile/experience pages. It is most useful if you want practical guidance on building or delivering client-based, client/server, or cloud-based software—less so if you are looking for product documentation, tutorials with step-by-step code, or pricing information.

The Three Content Areas

The site describes its offering under three headings, each with a "Read Insights" entry point:

The homepage frames all of this around a single goal: helping clients "achieve success in the mobile landscape" through custom solutions that provide insights, tools, and support.

Technical articles and delivery insights

This is the core reading. The site positions its writing as combining "deep industry expertise with cross-industry experience" to bring clients "innovative solutions and practical delivery guidance." In practice, that means content aimed at people making delivery decisions—how to approach a build, what experience from other industries applies, and where the practical risks sit—rather than reference material.

Profile and experience

The Profile section supports the consulting pitch: it is where the claimed industry depth and cross-industry experience are substantiated. Read it if you are evaluating whether the consultant's background matches your project type.

Consulting services description

The services page describes the shape of engagements—custom, packaged, and hosted—and the development models covered: client-based, client/server, and cloud-based. This is descriptive scope, not a rate card.

What You Won't Find (Based on the Site's Own Content)

• No pricing signals. The site lists no prices, pricing pages, or payment platforms. Do not assume services are free or that terms are published elsewhere on the site.
• No stated login or access restrictions on the reading material—but the site also does not confirm open access, so treat availability as unverified until you visit.
• No product manuals or API references. The content is consulting-oriented, not documentation for a specific product.

How to Decide Whether to Read It

• Worth your time if you are scoping a web or mobile project and want delivery-oriented perspective from a consultant with cross-industry experience, or you are evaluating this consultant for an engagement.
• Skip it if you need hands-on tutorials, code samples, or a comparison of vendors—the site's own description points to insights and guidance, not instructional content.
• Start with the Insights section for the articles, then the Profile section if you are assessing fit for a specific project.

One caveat: the site's own summary is brief, so the depth and frequency of the technical articles can only be judged by browsing them directly. Use the three "Read Insights" links on the homepage as your entry points.