Show, Not Tell | Technical Blog of Walter Yu
Title: Show, Not Tell | Technical Blog of Walter Yu
Description: As Github repositories and accounts become more like resumes, the README for our software projects are become more important as the first impressions to is ranked 0 in the world (amongst the 40 million domains). A low-numbered rank means that this website gets lots of visitors. This site is relatively popular among users in the united states. It gets 50% of its traffic from the united states .This site is estimated to be worth $0. This site has a low Pagerank(0/10). It has 1 backlinks. has 43% seo score. Information

Website / Domain:
Website IP Address:
Domain DNS Server:, Rank

Alexa Rank: 0
Google Page Rank: 0/10 (Google Pagerank Has Been Closed) Traffic & Earnings

Purchase/Sale Value: $0
Daily Revenue: $0
Monthly Revenue $0
Yearly Revenue: $0
Daily Unique Visitors 0
Monthly Unique Visitors: 0
Yearly Unique Visitors: 0 WebSite Httpheader

StatusCode 200
Content-Type text/html; charset=UTF-8
Date Mon, 08 Aug 2016 09:51:21 GMT
Server Apache Keywords accounting

Keyword Count Percentage Traffic Sources Chart Similar Website

Domain Site Title Show & Tell DVD Video Invitations Eventer - show and tell your talks Graphics Tutorials-Show and Tell Graphics Yu Yutopia Smartphone Blog Home - Shelley's Show and Tell Show and Tell Productions Show and Tell Meg Show And Tell Workshops Show and Tell Films Bindle - A show & tell for gear Alexa Rank History Chart aleax Html To Plain Text

Show, Not Tell | Technical Blog of Walter Yu Show, Not Tell Technical Blog of Walter Yu Skip to content Home About ← Older posts Writing Good README Docs (Benefits & How-To) Posted on July 25, 2016 | Leave a comment As Github repositories and accounts become more like resumes, the README for our software projects are become more important as the first impressions to prospective users and/or future employers. That said, it is important to invest the small amount of time to make a lasting impression. The README can serve as an after-thought when we are engrossed in our code; however, it is the first thing that prospective users sees and open-source software projects are often graded on their documentation. I would suggest approaching the README as a living document to be updated throughout the life of a project. As new features and requirements come about, then update the document periodically. Treat it as a periodic task to be completed, and it will be less of a chore. If starting a new README, I would suggest the following: Know Your Audience – Write for your intended audience in an approachable manner without too much technical jargon. Write with detail for the technical users but also broad enough for prospective employers and/or management who may not understand the lingo of your domain, language and/or framework. Keep It Simple – I personally love lists (such as this one) so bulleted lists go a long way to illustrate your points and all they required are an asterisk before each one in markdown syntax. Shorter sentences and paragraphs make the points easier to grasp. Stay Organized – Use headings liberally in your document to organize your thoughts and convince your reader. After all, we all wish to make a point so that our read is sold on our product, i.e. our project and/or work. Writing style is a deep and broad topic but in general, write in a voice that is comfortable to you, professional and cuts to the point. Respecting the audience by communicating effectively and efficiently goes a long way. Some other points for writing style that I find useful are as follows: Write in Your Voice – Assume that the README is completely public since it is posted online (or may be circulated), so keep things professional but also in your own voice. Avoid slang which seems unprofessional and/or lingo/jaron which may throw off your audience. Retain Your Audience – Stay organized, hit the key points then move on. Treat the README as an email being directed to a future employer or supervisor – write professionally and to the point without belaboring the point. Have Fun – Make your points but add that hint of personality when writing in your own voice. Avoid slang but write in a tone that is informative, instructive and not too stiff. In conclusion, the README is a public document that sets the first impression and tone for your audience and drafting/updating it is a small investment of time that can go a long way so please be sure to invest in it. Leave a comment Posted in Projects Laravel Deployment to Web Server (Outline) Posted on July 11, 2016 | Leave a comment Laravel applications often need their permission settings to be set when deploying to a live server for the first time. That said, here are some steps that helped me when first deploying onto Digital Ocean: Part 1 – Clone repo and generate new app key/.env file: 1. “git clone ” 2. “composer install” 3. “php artisan key:generate” 4. Clone .env file from local source (not in repo) Part 2 – Create/set permission folders (steps 5-8 are new): 5. “mkdir bootstrap/cache” 6. “touch bootstrap/cache/service.php” 7. “mkdir storage/framework/sessions” 8. “mkdir storage/framework/views” 9. “sudo chown -R www-data storage” 10. “sudo chown -R www-data bootstrap/cache” Leave a comment Posted in HES Geocoding, PHPUnit/TDD & D3.js (PHP & Laravel) Posted on June 27, 2016 | Leave a comment Listed below are the packages/tools which I used for my CS-15 final project, which may help any readers looking to start their own Laravel apps in PHP. Geocoding: Convert address into lat/long, useful for Google Maps, etc. Geocoder Package: Notes: Install using “composer require willdurand/geocoder” Documentation is useful and outlines how to work with the Geocoder class/methods getLatitude & getLongitude methods return values to plug into Google Maps API, etc. TDD: Catch errors as code base grows and becomes more complex PHPUnit (Installed with Laravel – example tests included): Notes: Integration tests help test by process, e.g. logging in, viewing pages, etc. Changes within MVC stack may result in errors elsewhere (regression testing) Ideally, tests are written concurrently with development code PHPUnit output can be sparse, so options are useful Verbose output: “vendor/bin/phpunit –verbose –debug –tap” PHP Integration Testing Tutorial: Integration Testing Example: Regression Testing: Data Visualization & Charts: Display user data using visualization/charts D3.js: C3.js (Add-on): Notes: D3.js is a great tool but may require lots of time depending on chart/feature C3.js provides similar functionality with a simpler API/interface Basically comes down to putting data into arrays, then passing into D3/C3 D3.js & C3.js: Leave a comment Posted in Projects ← Older posts Links LinkedIn Twitter Subscribe to Blog via Email Enter your email address to subscribe to this blog and receive notifications of new posts by email. Email Address Recent Posts Writing Good README Docs (Benefits & How-To) Laravel Deployment to Web Server (Outline) Geocoding, PHPUnit/TDD & D3.js (PHP & Laravel) Database Primer: ERD Diagram, Normalization & MySQL Workbench Atom & Chocolatey Package Manager (For Use with Windows & CMDer) Proudly powered by WordPress. Theme: Coraline by Whois

Registry Domain ID: 1525254080_DOMAIN_COM-VRSN
Registrar WHOIS Server:
Registrar URL:
Updated Date: 2016-01-24T02:53:05Z
Creation Date: 2008-10-22T05:07:12Z
Registrar Registration Expiration Date: 2016-10-22T05:07:12Z
Registrar: FastDomain Inc.
Registrar IANA ID: 1154
Registrar Abuse Contact Email:
Registrar Abuse Contact Phone: +1 801 765 9400
Reseller: BlueHost.Com
Domain Status: clientTransferProhibited (
Registry Registrant ID:
Registrant Name: WALTER YU
Registrant Organization: STORMSAVVY
Registrant Street: 3200 REVERE AVE
Registrant City: OAKLAND
Registrant State/Province: CALIFORNIA
Registrant Postal Code: 94605
Registrant Country: UNITED STATES
Registrant Phone: +1.5105520532
Registrant Phone Ext:
Registrant Fax:
Registrant Fax Ext:
Registrant Email: KHARMA@GMAIL.COM
Registry Admin ID:
Admin Name: WALTER YU
Admin Organization:
Admin Street: 1500 PARK AVENUE UNIT 313
Admin State/Province: CALIFORNIA
Admin Postal Code: 94608
Admin Country: UNITED STATES
Admin Phone: +1.6264222706
Admin Phone Ext:
Admin Fax:
Admin Fax Ext:
Registry Tech ID:
Tech Organization: BLUEHOST.COM
Tech Street: 550 E TIMPANOGOS PKWY
Tech City: OREM
Tech State/Province: UTAH
Tech Postal Code: 84097
Tech Phone: +1.8017659400
Tech Phone Ext:
Tech Fax: +1.8017651992
Tech Fax Ext:
DNSSEC: unsigned
URL of the ICANN WHOIS Data Problem Reporting System:
Last update of WHOIS database: 2016-01-24T02:53:05Z
For more information on Whois status codes, please visit
The data in the BlueHost.Com WHOIS database is provided
to you by BlueHost.Com for information purposes only,
that is, to assist you in obtaining information about or related to
a domain name registration record. BlueHost.Com makes
this information available "as is," and does not guarantee its
accuracy. By submitting a WHOIS query, you agree that you will use
this data only for lawful purposes and that, under no circumstances
will you use this data to: (1) allow, enable, or otherwise support
the transmission of mass unsolicited, commercial advertising or
solicitations via direct mail, electronic mail, or by telephone; or
(2) enable high volume, automated, electronic processes that apply
to BlueHost.Com (or its systems). The compilation,
repackaging, dissemination or other use of this data is expressly
prohibited without the prior written consent of
BlueHost.Com. BlueHost.Com reserves the
right to modify these terms at any time. By submitting this query,
you agree to abide by these terms.
UNLIMITED storage, bandwidth and domains on one account. Also receive a *FREE* domain for one year when you host with