pretty thrilled with this new site I've done for 2018. I've battled for years on how to present myself – and I think this layout and the simplicity of it, with it's focus on Projects and a CV, and personal stuff tucked away was the best approach.

"Projects" is big deal because I've no longered categorized or filtered what I do with "web design", "web app", "plugins", "logo design", tags. I've always hated that. What I do is projects, some years its more design, others its more code, some projects encompass all categories. This simple list of projects better defines my scope and current interests.

I've reduced the verbose blog section into more of an index., which is much more appropriate for the small number of visitors that come in to those posts from Google. Showing excerpts or the full post was unnecessary.

My "artwork" which I am proud of, but I do not do so much anymore, has been tucked away, which cleans up my portfolio "Projects", but still exists to those interested in browsing.

It's built on Gutenberg, which was lots of fun. Coded a few custom blocks for all the RECENT boxes. Also tapped into WP REST API which was similarly fun.

Really excited – 2018 has been a great year so far.

Eat. Sleep. Code.

not sure if is super incredibly smart, or just anti-conformity boat rocking. Don’t get me wrong, they’ve done an absolutely beautiful job with their stack, setup, and logic on everything.. They’re two-factor app logic to WordPress, sounds like people very very intelligent found a solution to a problem. & I’ve read all the whys and hows for all tools.. But I’m not sold – may be it’s just an advance programming setup, that in my mind and abilities I lack the concepts of, but as a WordPress theme developer, I can’t see any reason underscores with browsersync and an IDE or server that handles LESCSS, and controlled with github wouldn’t be just as good.. Theme image optimizing surprises me as a selling feature, I mean – who even uses images in themes anymore? svgs and font icons and gradients – everything else is WordPress Media controlled.

Still will give it a shot, but not sure this is a good use of time.

I feel like I’m the only person who uses sunsetΒ to have a light theme in the night, and dark in the day.


Alternative to the hoverbar, cost about a dollar instead of forty, ends wrapped in elecratical tape. Mounted to a Dual-monitor bar, on a standing desk. My setup is getting higher.

Although I have to modify my custom 18″ deep desk to 24″ deep to house the large base of the standing desk. Time to setup my office properly, only’ve been here for a year now.

🐣 Really finding Emoji’s come in handy for tagging visual cues. I do enjoy the selection, and the detail in each icon, but I really don’t use them or like adventuring outside of my “Frequently used” section. I’ve got it down to basically using just eight:

Categorizing / Tagging

πŸ‘¨πŸΌβ€πŸ’» Daily / work
βš” Anything related to my own projects


βœ… Good
⚠ Note / Be aware
πŸ”₯ Holly $#%@%@#$% urgent

πŸ™…πŸΌβ€β™‚οΈ nope


πŸ˜‚ ha
πŸ€¦πŸΌβ€β™‚οΈ oy vey

🎯 Setting all my sights and extra time on node.js for the rest of the summer.

🀞🏻 My hope for Gutenberg is huge. WordPress lacks the page builder experience, leaving third party plugins to fill the void. These third party plugins aren’t built by a community of WordPress developers, they’re built by directed companies – companies seeking profit, and under the push of their customer support requests. These plugins lean towards easier interfaces that match their brand, more this and more that. & as every developer knows, that means more libraries, more icon sets, more external resources. Albeit an enjoyable user experience, but so much added ontop of WordPress.

For example, the number of scripts that DIVI builder includes is understandably needed, but too much, it always makes me cringe when looking at the source code. Only some of it is compressed as well, bloating the sites and lowering rendering scores.

Gutenberg, driven by developers instead of customers – developers who care about the footprint, I believe will be more efficient, using existing libraries instead of including new, using dashicons instead of custom, and so on (React exempt, but who cares, that’s the backend of the site). I’m betting the result will be a page builder thats easy to use with enough this and more that in the backend, but still doesn’t bloat the front end.

🀯 Following the development of Gutenberg is crazy – the WordPress core is set in 5th gear for using React as the main editor interface, solutions for shortcodes and metabox’s not around yet, but will likely be phasing out PHP/MySQL for Javascript.

Public Service Announcement: if you’re using DIVI Builder as a template system. Use classnames for your moduals/rows where you can, instead of using the Setting’s DESIGN tab. This will give you much better change-control, especially while doing responsive tweeks.

πŸ˜‘ Sendmail not working on Amazon EC2/Lightsail Ubuntu 16.04.

Sendmail and me, well, we don’t get a lot. Previously it was FQDN’s and hostname issues that caused mass problems, this time, it was something new: I had a problem with with PHP’s Sendmail emails landing in spam instead of the inbox.

I read all the warnings about AWS’s emails ending up in spam “no matter what.” Despite having two other AWS machines that have no issue, it was confusing why this install was having issues. I settled on the problem being AWS issue and figured, “oh this is what everyone’s talking about.” The online solutions to this issue all took me to AWS SES, an overkill service, as I just needed an email or two a week, but I needed the issue resolved.

While trying to solve my issue and trying to get SES to work, everything was amiss – no matter if I tried to fix postfix, sendmail, or setup the remote smpt server for SES through sendmail, everything broke and wouldn’t work. I was constantly hit with error after error:

sendmail Cannot write ./blahblah (bfcommit, uid=0 No such file or directory
localhost postfix/postdrop warning: unable to look up public/pickup: No such file or directory
NOQUEUE: SYSERR(root): hash map "access": unsafe map file /etc/mail/access.db

I’d start over, redo it, and land in the same place – then get hit with some more permission issues. I can handle all errors that come my way typically in an hour, but this was pressing far beyond that.

😬 As it turns out, my problems and solutions were two fold:

  1. The IP Amazon gave me was blacklisted. Gah! So simple. Luckily the environment wasn’t too big, not too many A Records, and I easily got a new Elastic IP. Lesson learned: when AWS always check it.
  2. Reboot after reinstalling sendmail and postfix. A simple apt-get remove/purge and fresh install‘s, then a reboot, made everything work as expected.

πŸ“± Some people appreciate the art of a well organized app icon layout. Others have interesting outdoor hobbies. I am the former. Behold. Only two apps off screen: Health and Wallet because no one actually uses either them in Canada afaik.