New 42-day free trial
All Tags
21 blog posts tagged "Technical support"
Smarty™ earns silver at Best in Biz Awards 2023 for Support Department of the Year
By Trent Howell on December 13, 2023
We're delighted to announce that Smarty has been honored with the Silver Award in the Support Department of the Year category at the 13th annual Best in Biz Awards. We want to emphasize what this recognition means for you, our customers and partners. At Smarty, our primary focus is providing the best supported, documented, and easiest-to-implement address APIs and data. Winning Silver in the Support Department of the Year category speaks volumes about our commitment to delivering an outstanding customer experience.
Address verification for fun and profit: Using Go SDK
By Andrew Townsend on April 26, 2023
In our recent webinar, Ryan Cox, one of our highly skilled API developers, walked through setting up and using the Smarty Go SDK. The webinar covered various essential topics, from obtaining the SDK to understanding the ins and outs of implementation. Ryan explained that the Smarty Go SDK is easily accessible on GitHub. He then moved on to discuss the key differences between embedded keys and secret keys. Embedded keys are ideal for client-side applications because they provide limited access and don’t reveal sensitive information.
New feature: Log into Smarty with your Google account
By Davin Perkins on October 11, 2022
You've asked for it, and now you’ve got it. The next time you log into your Smarty account, you’ll see the option to log in to Smarty using your Google account. In this blog, we'll cover how to:Merge an existing Smarty account with GoogleVerify your loginCreate a new free Smarty account with GoogleMerge an existing Smarty account with GoogleMerging your account with your Google account will not affect your available lookups, security keys, or any other part of your Smarty account. Merging your Smarty account will:Increase security by reducing the number of managed passwords and how often you have to enter your password.
What is hybrid cloud? Is it better than on-premise or cloud software?
By Davin Perkins on September 28, 2022
When considering business software tools for Customer Relation Management (CRM), Business Intelligence (BI), Geocoding, Address Validation, and more, most organizations are either looking specifically for on-premise options, cloud options, or they’re still debating between the two. On-premise and cloud have been dueling each other for many years. However, a new challenger has entered the ring: hybrid cloud. What is hybrid cloud?A hybrid cloud environment uses a mix of on-premises infrastructure, private cloud services, and public cloud services—such as Amazon Web Services (AWS), Microsoft, or Google.
Common mistakes when calling Smarty APIs
By Andrew Townsend on July 28, 2022
There are two types of frequent errors: 401 "Authentication Required" errors, and 402 "Payment Required" errors. If you keep reading, you can learn about both, as well as these other hot topics:Status code 401 - Authentication requiredHow to authenticate API requestsCommon mistakes in client-side requestsCommon mistakes in server-side requestsStatus code 402 - Payment requiredWhen in doubt, contact supportStatus code 401 - Authentication requiredIf you're seeing this error there's a chance that there's an issue with your API key, there's a mistake inside your client-side request, or a mistake in the server-side request.
5 principles for creating stupidly brilliant JavaScript applications
By Andrew Townsend on April 11, 2022
Have you ever tried to add a minor feature to your application only to discover that you’ll have to re-write large blocks of code first? Or maybe you’ve spent hours deciphering hundreds, or perhaps thousands, of lines of existing code just to find out a task only required two lines of additional code. If you’re like most developers, you’ve wasted countless, frustrating hours wading through immensely complicated code trying to force it to do things it wasn’t built for. In his presentation, Mike Manwill, Frontend Team Lead here at Smarty, discussed 5 principles to help you create stupidly-simple applications that are maintainable, extendable, and bug-resistant.
SECURITY ANNOUNCEMENT: Removing old TLS versions
By Jonathan Oliver on October 17, 2019
TLS (and its predecessor SSL) are cryptographic protocols that provide authentication and data encryption for clients connecting with web servers. As new vulnerabilities are discovered, older cryptographic protocol versions are deprecated to maintain secure environments. On Tuesday, January 21, 2020, Smarty will require clients to use TLSv1. 2 or greater to connect with Smarty APIs without interruption. Clients using TLSv1. 0 or TLSv1. 1 will no longer be able to connect. Please refer to our documentation for more information: https://www.
Go naming conventions
By Michael Whatcott on October 18, 2018
It's been said that naming is one of the two hardest problems in computer science, along with cache invalidation and 'off-by-one' errors. (See what I did there?) Do you ever find yourself wondering what policies and practices you could adopt to make your life easier when reading code you wrote months ago? Or maybe you're up at night wishing you knew how to write code in such a way as to maximize adoption and convenience for your users? Well, look no further because we've anticipated the need, solved the problem, and now we're sharing our knowledge and wisdom at no charge, all out of the goodness of our hearts in this comprehensive, totally no-nonsense (nudge, nudge, wink, wink) style guide of Go naming conventions.
Cloning private dependencies in Docker and Go
By Jonathan Oliver on September 13, 2018
One topic that seems to come up repeatedly on Stack Overflow or other online forums is the topic of how to go get private dependencies. Specifically, if I have a private Git repository on Github or Bitbucket, how do I bring that code locally via the go get tool such that automated builds can produce a clean, consistent build without interaction from a user? This problem is largely solved for public Github dependencies but continues to be a challenge for private dependencies. To reiterate, if you're only cloning publicly available dependencies, you probably won't be reading this post.
Let's build an xUnit-style test runner for Go!
By Michael Whatcott on July 2, 2018
Writing test functions in Go is easy:package stuff import "testing" func TestStuff(t *testing. T) { t. Log("Hello, World!") } Running test functions is also easy:$ go test -v === RUN TestStuff --- PASS: TestStuff (0. 00s) stuff_test. go:6: Hello, World! PASS ok github. com/smartystreets/stuff 0. 006s Preparing shared state for multiple test functions is problematic. The usual recommendation is to use table-drive tests. But this approach has its limits. For us, xUnit is the ideal solution.
Scanning CSV in Go
By Michael Whatcott on May 5, 2018
For the purpose of this article, consider the following CSV data, slightly modified from the docs for encoding/csv:csvData := strings. NewReader(strings. Join([]string{ first_name,last_name,username, "Rob","Pike",rob, Ken,Thompson,ken, "Robert","Griesemer","gri", }, "\n")) Here's how you read the data, line by line, using the Reader provided in that package:reader := csv. NewReader(csvData) for { record, err := reader. Read() if err == io. EOF { break } if err != nil { // handle the error.
Testing in Go by Example: Part 6
By Michael Whatcott on September 25, 2017
For this installment of the Testing in Go series we'll be talking about a grouping of packages that facilitate general-purpose comparisons in various contexts. Since the most common context is testing it seemed like this series was the right place for the discussion. We generally refer to these comparison functions as assertions (cue ominous background music and spooky sound effects). You may have already read the opinions found on the Golang FAQ related to assertions. "Why does Go not have assertions?"Go doesn't provide assertions.
Our testing tools
By Michael Whatcott on November 3, 2016
IntroductionTL;DR: Choose an approach to software testing that helps your organization create the best possible end results. That might mean using and/or creating a few tools and/or libraries along the way. Or, maybe not. What follows is a description of what we do at SmartyStreets, couched as a response to Dan Mullineux's equally valid way of doing things. The costA favourite test helper library, with some simple test assertion functions clearly has some value. . . They [testing libraries] are not so bad, but they come at a cost, defer to avoid them.
How to setup a tinc VPN
By Jonathan Duncan on October 23, 2015
I was given the task of setting up a tinc VPN so that we could test performance for comparison against other VPN systems. This task took much longer than it should have. For that reason, I am making this post to help me and others remember how to do it again in the future. Installing tinc is straightforward enough. You can download the latest release and build it or install it from your favorite package manager. The configuration for tinc lives in /etc/tinc. The configuration is what seems to be the hard part of getting tinc to work.
Performance testing with Phoronix
By Jonathan Duncan on October 5, 2015
Not every server is made equally. On dedicated servers, the hardware varies widely. On virtual and cloud servers, the resource allocations also vary widely. Some servers are CPU-optimized for maximum computing power. Others focus on having a lot of memory. Some servers are built to have a good balance of all system resources. Hardware aside, we require many differing tasks of our servers. Some applications are processor hungry, some need large amounts of disk space, while others take up a lot of memory.
Testing in Go by example: Part 5
By Michael Whatcott on September 15, 2015
For this installment of the Testing in Go series I'll share a really nifty way to deal with time in your unit tests. When the behavior you are testing depends on the current time it can be tricky to assert on the results because the current time is a moving target. So, usually we end up resorting to approximations in our assertions that, while functional, always bother me a bit. In some cases, depending directly on the system's current time prevents acceptable test coverage. Consider this trivial example, which defines a calendar service with a method that identifies the current quarter of the current calendar year:File: calendar.
Testing in Go by example: Part 4
By Michael Whatcott on August 11, 2015
I think it's time for a slight detour. In part 1 we covered the basics of testing in go. In part 2 we covered a few slick ways to execute tests. In part 3 we covered some of our recent endeavors at Smarty to build on the basics. Toward the end of that post, we went into some detail regarding our approach to assertions. The assertions referenced in the GoConvey project are actually their own separate project that are imported into GoConvey. The nice thing about separating the assertions into their own separate project is that they can be used, well, separately.
Testing in Go by example: Part 3
By Michael Whatcott on May 11, 2015
ReviewWelcome to part 3 of our "Testing in Go" series. If you're new here, feel free to catch up before reading on. In part 1 of this series I eluded to our perceptions of the standard testing tools provided by the Go tool and the standard library and what was missing for us. We all have different expectations of a testing tool and so it's no wonder that so many have been created. Part 2 of the series focused on how we have made the act of running tests effortless and automatic. IntroductionIn this post and the next few posts I'll focus on our approach to writing actual tests.
Testing in Go by example: Part 1
February 27, 2015
Here's part 1 of our "Testing in Go" series. IntroductionThinking about trying Go? You won't regret it! It's great that testing is baked into the "testing" package from the standard library and the corresponding go test command (which has all sorts of useful and interesting flags). We'd like to show you how easy it is to get started using the built-in testing tools and introduce you to some tools we've created. This is the first installment of a series designed to do just that. All you have to do is create a file named like *_test.
Testing in Go by example: Part 2
February 27, 2015
Here's part 2 of our "Testing in Go" series. If you're new, feel free to catch up before reading on. BasicsYou've already learned how to execute tests in Go for a single package. $ go test There's a bit more to it, though. You can run any package from anywhere if you provide the import path. For example, this command runs the actual tests for the "testing" package from the standard library:$ go test -v testing If you've already run go get github. com/bradfitz/http2 you can execute those tests from anywhere with this:$ go test -v github.
Your Convey needs more focus
February 7, 2014
One of the great benefits of TDD/BDD is that you usually don't have to spend much, if any time at all in a debugger. To enter a debugger is to admit a loss of control over the system under test. Even so, there are times when you do need to debug something, even if you're maintaining the discipline. Lately, most of my coding is in GoLang. Coming from using an IDE almost exclusively to write Python (using PyCharm) and C# (using VS and ReSharper), and knowing how great the visual debugging tools are it's hard to fathom using a console-based debugger for GoLang code.