At OMG, many of our backend microservices are written in the Go Programming Language. Among a few other things, Go is primarily famous for having extremely efficient, first class concurrency support.

Go’s primary form of concurrency is called a goroutine. Goroutines, like coroutines in other languages, allow for asynchronous programming. At a low level, Go’s runtime multiplexes these coroutines onto OS threads, providing parallelism in addition to concurrency. While many other languages have something similar, Go's goroutines are primitives, built into the base language, and the Go runtime manages them extremely efficiently.

Big Data is one of the most popular buzzwords and truth is, we generate a lot of data. That said, data does us no good unless it contains meaning. Data is power.

Problem is, the data can be as varied and diverse as the people using it, leading to messy data and ambiguity in insights. A majority self-serve platform like OrderMyGear can easily lead to messy data when one person types “Spirit Wear”, another types “spirit gear”, yet another types “Spiritwear”, and unfortunately another types “spriit wear”.

Testing: The final frontier (or in TDD, the initial frontier). There are a ton of ways to do it but in general, it’s hard to know what to test. With all the different testing frameworks out there, it’s also pretty hard to choose how to test. At OrderMyGear, when it comes to unit testing, we wanted the ability to test using something that would work for our internal UI framework library as well as our micro-ui server-side rendered apps.

Building a robust website is no small task. Countless articles have been written about pieces of the end-to-end process: the initial stages of ideation and user research activities that define what could be built; the myriad of design-centric artifacts that define what will be built and how users will interact with it; and the engineering processes that define how it will come to life. When working in cross-discipline teams, it should all flow naturally from one team to another to a finished product.

That all sounds very “waterfall” doesn’t it?

If you have any experience developing web interfaces, you have most likely encountered pagination. When there is too much data to present at once, pagination allows the user to explore the data one batch at a time. A common alternative to pagination is scrolling. At first glance, paging and scrolling are interchangeable ways to present data. Both display the same information to the user in the same order. 

If you’re a developer, then you’ve probably heard the acronym “CI/CD”: Continuous Integration / Continuous Deployment. When creating a new application we often start with the CI part by setting up some kind of an automated build pipeline. This pipeline can run all sorts of things, including:

Every company does Engineering hiring and onboarding differently - and OMG is no exception. The OMG culture is a rare find, and it all starts with the way we interview, hire, and onboard our new OMG’ers.

So you’ve decided to use React for your app. Congratulations, you’ve made a fantastic choice. Over the past few years, React has become the leading JavaScript library for building web applications. The whole idea of building a web app without a JavaScript library or framework may seem antiquated at this point. 

Every week in March, we will be highlighting some OMG'ers so you can get a feel for the people behind the magic! The OrderMyGear Engineering Team consists of some of the top talent in the software engineering field, occupying the entire third floor of the OMG Office. Meet a couple of the faces behind the magic that build the modern, reliable, and simple OrderMyGear platform...