I hereby claim:
- I am johndturn on github.
- I am johnturn (https://keybase.io/johnturn) on keybase.
- I have a public key whose fingerprint is E999 1862 B530 13D4 3451 15E2 0801 6015 E2DD B7D9
To claim this, I am signing this object:
I hereby claim:
To claim this, I am signing this object:
With so much in the cloud these days, I find that it's become easier and easier to justify wiping my machine totally, and starting fresh. The pain of getting all your data transferred has mostly vanished away with the adoption of storing basically all of my most important data in various cloud repositories.
That being said, there are still plenty of things that need downloading and configuring on a fresh machine. To avoid the hassle of looking at the same GitHub repos over and over again for installation, and trying to remember all of the small command line tools that I had installed, I figured it was time to write down the things that I need on each machine.
I use the Quiver App quite frequently for code samples, general notes, etc... However, I've never been able to find a theme for it that really satisfied my love for Monokai. So, similar to my custom Monokai theme (based on the VSCode Monokai theme, which I call Monokai+) for Jetbrains products, I've created this theme for the Quiver app.
The initial theme was based on the Dark Ulysses theme. It's a great base theme, but since I write almost exclusively in Markdown in the editor, I found the Markdown cells needed some Monokai goodness. Hence, Monokai+ for Quiver was born.
Feel free to take it, add to it, or comment for improvements.
Note: As I mentioned, I write basically all of my notes in the Markdown cells in Quiver; therefore, I haven't really touched the theme for the other cells. If there are updates that you'd like to see there, feel free to update it.
The Dependent Picklist feature in Salesforce is an incredibly powerful tool for keeping data clean and organized. Through setting up relationships between different fields, an Admin can filter available values in certain picklists based on the value of other fields.
Unfortunately, many Admins discover that, despite configuring dependent picklists for objects like Leads, that functionality disappears as soon as they generate a Web-to-Lead form.
Wouldn’t it be great to maintain that data cleanliness in the Leads generated by those that fill out your HTML forms? Turns out the code necessary for this is pretty straightforward.
When working with Web-to-Lead forms, you might run into a situation where you'd like to integrate the form with your frontend framework (React, Vue, Angular, etc...). This can be accomplished quite easily using whatever HTTP library you're most comfortable with.
To demonstrate this, let's take a look at an example Web-to-Lead form, and the JavaScript required to post Leads to a SFDC org.
<html lang="en">
I've been baking with a sourdough starter since about 2016. When I first started, I kept pretty close to the recipes and techniques listed in Flour, Water, Salt, and Yeast (FWSY), by Ken Forkish. Following Ken's advice as outlined in his book, I made some pretty great bread. However, after doing it for about a year, I decided to start to experiment with some changes.
Unfortunately, in my experiments I didn't make very good bread. So, I wanted to learn more about the process, and figure out what I was doing wrong. Ultimately, I wanted to gain more baking intuition. After working at it, and experimenting with different makeups of a sourdough starter (referred to by many as a levain), I was able to learn some things that I felt weren't adequately communicated in other blogs, forums, and YouTube videos. That, or I was just too hard-headed, and needed to experience bad outcomes to learn.
There are tons of conflicting advice and recipes onlin
How to host and correctly run a Node CometD client on Windows Server (2019+) for connecting to a Salesforce instance in order to listen to Platform Events. These instructions are also specifically for accessing a Windows Server instance running in Azure.
Today I woke up and realized that a power surge a while back had taken down our Unifi controller without me realizing. I went to log in to check on firmware updates for the network only to see that I couldn't log in at all. I guess that's the benefit of hosting your controller via a CloudKey Gen 2 with a built-in on-device battery vs. on a Raspberry Pi like I do.
That said, restoring from scratch was actually super easy, given that I had regular backups. Here's the process and some additional reading that I used.
ssh
or through a command line interface