| |

WordCamp US 2019 – Code Like A Writer – Alex Ball

ByTim Nolte Updated on

Writing Principles

  • Punctuation Saves Lives
  • Separate your metaphors
    • separate your concerns
    • making good comments

Coding Principles

  • Syntax
  • Form – code formatting
  • Spellcheck – code linting
  • DRY – Don’t repeat yourself
    • Redundant words just take up time
  • Code is Poetry
    • Being creative
    • Clean and concise
    • Doing as much as it can with as little as possible
  • In Stories Someone Usually Dies in the End
    • In AJAX function wp_die() at the end.

Technical Architect

A Christ-follower, husband, father, and WordPress Developer with Forum One.

Similar Posts

Tuesday Interval Training Run And Virtual 5K
/ /

Tuesday Interval Training Run And Virtual 5K

ByTim Nolte Updated on
A big shout out to Automattic for promoting the WWWP5K virtual run and matching donations to your favorite charity. #wwwp5k #HWI #Run4Water #WhyIRun #RiverBankRun Automattic matching donations: http://timn.me/wwwp5k2020 Give the gift of clean water: https://timn.me/2020HWI Also on: MastodonMastodon TwitterTwitter InstagramInstagram
Neovim - Editing WordPress Plugin File
/ /

WordPress Development On A Chromebook, Termux, & Neovim

ByTim Nolte Updated on
So about 6 months ago I decided to make some changes to my personal development environment. I’ve been using a Chromebook as my primary machine since about 2013. I first purchased an Acer C710 for my wife to use but compared to our Macbook Pro it was a frustrating and subpar experience for her, not to mention she was a heavy Adobe Suite user. Since sharing the Macbook Pro was challenging I set out to use the Chromebook as me development machine. Originally I went with the crouton option. It was pretty sweet to have a full Linux environment alongside Chrome OS. I was then running a full LAMP environment with PhpStorm as my IDE. This worked OK, I had performance and stability issues at…
WPGR: Learn about the Developer Tools in your browser
/

WPGR: Learn about the Developer Tools in your browser

ByTim Nolte Updated on
Firefox Developer Tools – Topher Inspector – look at HTML/CSS behind a web page Responsive Display Mode Console – look for errors (security/resource loading issues) Different results depending on when you open – loading vs loaded Debugger – for JavaScript Style Editor – for changing CSS Performance – monitoring page load performance Network – Storage – Local browser items, page cache, cookies, etc. Chrome Developer Tools – Brian Shortcuts – keyboard commands to open dev tools (CTRL-OPT-I[Mac OS X]/CTRL-SHIFT-I[ChromeOS]) Docking – SHIFT-CMD-D(Mac OS X) / CTRL-SHIFT-D(Chrome OS) Elements (inspector) Styles – Filter allows for viewing specific CSS states (i.e. :hover) Add specific element styles Color Swatch – has a color picker, can save swatches Computed Styles View a visual representation of spacing See the CSS that…
WordCamp GR 2017 – WP-API: The Good, the Bad, and the Ugly – J Andrew Scott
/

WordCamp GR 2017 – WP-API: The Good, the Bad, and the Ugly – J Andrew Scott

ByTim Nolte
J Andrew Scott – http://rubberchickenfarm.com/ History of APIs RSS Advantages Fast & reliable Easy to consume Almost no technical footprint Disadvantages Read-only Static content No authentication No user-driven content (i.e. comments, favorites, etc) DIY API Advantages Dynamic content User-driven content App & user authentication Roles & permissions based Connected applications Disadvantages DIY OAuth Redundant URI scheme Mediocre performance Large technical footprint WP-API Advantages Succinct URI scheme Improved performance Small technical footprint Available in WordPress core Disadvantages Granular transactions No batch uploads Increased number of API calls What once required 2 web servers now required 12-15 servers WP-API Disadvantage Factors & Solutions Number of content types Solution: consolidate endpoints Volume of individual API calls Solution: batch processing endpoints Frequency of individual API calls Solution: page-level caching Lessons…
The Road Of Lifelong Learning To Be A Better Developer – Using Git Better
/ / /

The Road Of Lifelong Learning To Be A Better Developer – Using Git Better

ByTim Nolte
As a developer and, in some areas, a perfectionist I’m always after better #development practices when working collaboratively. An I personally find value in the #commit history. As a #git user I appreciate detailed case from @ecampidoglio on the proper way to keep a clean commit history. The Case for Pull Rebase

Leave a Reply

Your email address will not be published. Required fields are marked *

This site uses Akismet to reduce spam. Learn how your comment data is processed.