Ignoring tech debt because it’s expensive doesn’t make the problem go away — it only kicks the can down the road. Businesses should approach technical debt as a routine, scheduled part of their development process.
One of the more remarkable turnarounds in recent American culture has been the embrace of sports betting and online gaming. What was once considered a vice and relegated to relatively few in-person jurisdictions has quickly exploded into the mainstream and online. Like with any growth industry, this has had cascading consequences for others that work … Read More
Following my post about the Chariot Data Engineering interview, I received some comments along the lines of “wait, you don’t test their SQL skills?!?” Actually, we do: after loading up the test data into Redshift, the candidate creates three progressively difficult queries. But by then, I’m pretty sure they’ve got the skills we need, because … Read More
Our development teams are structured as extensions of every client and are committed to helping them achieve their goals and look great in the process.
Successful collaboration requires great two-way communication. That sentiment is core to our product design philosophy here at Chariot Solutions. A critical part of our job is to help balance client and user needs against a project’s budget and technology realities. This is especially true when building a minimum viable product (MVP). If budget and technology … Read More
We asked our team at Chariot about common omnichannel pitfalls, and how companies of any size can overcome or avoid them.
My last few posts have focused on Redshift and Athena, two specialized tools for managing and querying Big Data. But there’s a meme that’s been floating around for at least a few years that you should just use Postgres for anything data-related. It may not provide all of the features and capabilities of a dedicated tool, but is one less thing to learn and manage. Should this advice also apply to your data warehouse?
Recently, a project I worked on was considering using Electron as a fallback technology for an initial Progressive Web Application. At the time, the assumption was that since Electron uses Chromium, a browser, it should allow application developers to not only use the features of a PWA but also gain native access to technologies, such … Read More
Some key architecture decisions to help you drive brand awareness and revenue through seamless customer experiences.
I’ve always been a fan of database servers: self-contained entities that manage both storage and compute, and give you knobs to turn to optimize your queries. The flip side is that I have an inherent distrust of services such as Athena, which promise to run queries efficiently on structured data split between many files in a data lake. It just doesn’t seem natural; where are the knobs?
So, since I had data generated for my post on Athena performance with different file types, I decided to use that data in a performance comparison with Redshift.
