DEV Community: Dylan Pierce

Connect WooCommerce to FraudLabs Pro without code

Dylan Pierce — Fri, 11 Mar 2022 15:59:52 +0000

⚡️ Welcome to the 2nd installment of the Pipedream Speed Run! ⚡️

In this series, we'll create a Workflow from start to finish in 5 minutes or less.

This week we're featuring a brand new integration that was just included in our component repository by the folks over at FraudLabs Pro.

FraudLabs Pro specializes in preventing fraud with machine learning tools, and customer verification tools like SMS verification.

In this episode we're going to connect a WooCommerce store to FraudLabs Pro's SMS verification. That way every new order placed on our WooCommerce store will automatically be sent a verification code via text message.

Want to see a specific workflow tutorial? We're taking submissions!

https://form.jotform.com/220694247042049

Save your up arrow key, use history more

Dylan Pierce — Thu, 09 Jan 2020 14:40:02 +0000

One common day to day scenario we face everyday is reusing a terminal command that we carefully crafted maybe hours before we went on a ~reddit binge~ rabbit hole during other work.

To find a past used command I would normal just keep pressing the up arrow key until I finally found the command I was looking for.

However, history is really simple and saves you time and typing. Check it out.

$ history

12100  git commit  --allow-empty -m "triggering deployment"
....
12107  ga app/controllers/
12108  ga app/models
12109  gst
12110  gcmsg "Adding some missing methods for user authentication"
12111  gp

history is kind of self explainatory, it shows your shell command history.

The first column is the command ID, whereas the 2nd column is the string of the command itself.

You might be tempted to reach out to your mouse to copy & paste the command you were searching for, but there's a better way:

$ !<command entry ID you want>

So for example, if I were to enter !121000 it would pluck the command with the ID 121000 and now it appears in my terminal prompt like magic. Woo!

Extra Fun

You can utilize Linux pipe operators to search your history for specific things, maybe you want to see your last copy operations:

history | grep cp

This will give you a last of your last cp commands. Now you can find where you lost that file you meant to copy to your home directory.

Extra Extra Fun

To make life even easier you don't even have to spend the mental energy piping commands or reading your history line by line.

Built in you can use a search function that's activated with ctrl + r. It will activate a reverse search, this allows you to search for past commands by name.

For example, enter history then ctrl + r. You'll be greeted with a prompt similar to (depending on your *nix environment):

bck-i-search:

You can type in the beginning of the command you're racking your brain for, and it'll give you the first result of the last command you ran beginning with your search term. Amazing.

What's your JAMstack backend of choice?

Dylan Pierce — Fri, 03 Jan 2020 14:23:21 +0000

I've tried both Airtable, Netlify, and clay.run for adding simple functions & database support to my JAMstack powered blog.

Was curious if there are other options out there. The less infrastructure setup the better.

Release :: PHP to Ruby learning series

Dylan Pierce — Tue, 07 Aug 2018 00:40:42 +0000

After months of writing and burning midnight oil PHPtoRuby is finally available for your viewing pleasure for free.

https://phptoruby.io

PHPtoRuby is the result of the lessons I've learned after transitioning to Ruby development after ~ 10 years of PHP development.

I was frustrated by the beginner focused Ruby books. I already had production PHP experience in several frameworks - including Laravel, Symfony, Lumen, Silex and of course vanilla PHP.

I wanted just someone to explain a Ruby concept with a PHP equivalent example. Since I couldn't find a decent resource, I decided to sit down and create it.

If you're interested in Ruby because you've heard great things about Ruby on Rails (which it does live up to it's name, trust me) - then you should give this short book a shot before heading over to the Rails Tutorial.

This book will give you a head start into understanding the philosophical and syntactical differences between PHP and Ruby. It will also explain some of the key differences in web hosting, namespacing, type hinting, and even touch on the IoC container debacle.

I wrote this for the PHP developer that has at least some OOP experience, but if you don't I explain the PHP concepts as well.

So check it out, it's the easiest way to become a server side ployglot if you've already learned the language that powers a third of the internet.

Dylan Author of PHPtoRuby