About the man

My grinning face. The red hair doesn't distract from the overly-busy background...

So you instinctively click “About” links too, huh?

Welcome. I’m Eric LawlerOne of many on Earth, I might add. There are 28 Eric Lawlers on LinkedIn alone. Tip: You know which one is the real me by the hair….

Through managing software development teams, I help companies keep revenue curves pointed up-and-to-the-right. As a software engineer turned engineering leader, my servant-leadership philosophies and focus of working on the business, not only in the business, drive my results.

(You’ve caught this website in a beta state: In the near future, this section will link you to my portfolio and resume, which explain who I am in action, rather than in mere words. For now, you might be interested in this amusing list of stuff I’ve been paid to do.)

My wife and I have been married for 12 years and known each other for nearly a quarter century now. We’ve expanded our family with a boisterous bunch of boys (four of them, all age 10 and under) and an equally feisty 2-year-old daughter.

“Reformed Evangelical Christian” is the most succinct description of my relationship with Jesus, the foundation of my worldview and source of my strong values.

Outside the office, I’m a serious car enthusiast and gearhead (protip: reduce rotating drivetrain mass to increase smiles per mile) and amateur photographer. During ‘Rona season, I got back into an early love–mountain biking! You can find me on our local singletrack, when I’m not fiddling with the family’s bike fleet. Nothing beats flying across rock gardens at 20MPH…

About the website

When computer-programming/engineering types have a website, it’s traditional to brag about explain the technology used to create and serve the site. I have no idea who actually reads these summaries, but for posterity’s sake…

My goal was to create the fastest-possible website using the brain-dead easiest technical solutions, as I would advise any business. Polite cough. I would actually advise a business to use Netlify and publish their static sites straight from a code repository and not run a dedicated web server.

This website is a static site created by Pelican, a Python static site generator. I added a few custom Python extensions to bend the Jinja2 templating engine to my will.

I created the theme myself—both the desktop and mobile variants. The basis for the theme is Dave Liepmann’s Edward Tufte CSS, which powers the lovely serifed font and gorgeous margin notes you see throughout the site. The code highlighting theme is Solarized Dark, my preferred color theme for… everything.

The website is hosted by Digital OceanWhy not AWS? That question deserves a standalone article. The short answer: Market competition benefits everyone., running nginx and CentOS 7 Linux. #redhatforlife

Lastly, everything is checked into git with my usual level of detail (and delightful sprinkling of wackiness). I’m obsessed with the Annotate feature in the JetBrains IDEs. Eschewing PyCharm, I used my existing copy of PHPStorm throughout development.

How to build this website

…so Eric doesn’t forget. Parallel instructions in the repository readme.md.

This is pretty straightforward. You need pipOkay, no, you don’t technically need Pip, you can install all the Python .py files by hand, of course. And you’ll have to when pip inevitably stops working in ~2028 because the world has moved on to the next great thing., the Python package manager:

  1. pip install pelican
  2. pip install Markdown
  3. pip install webassets
  4. dnf install yuicompressor <– needed for webassets, which installs yuicompressor. Adjust the binary name in the YUICOMPRESSOR_EXECUTABLE setting in pelicanconf.py to match whatever method you use to install the actual compressor.
  5. That’s it! You can now run make devserver from the root directory and navigate to localhost:8000. make rsync_upload will build and publish the site to the remote server.

(Are you a proud member of the 0.001% who use feed readers? Lawler.io has an Atom feed available here, but your reader should automatically discover the feed on any essay page.)