As generative AI grows in popularity and enterprises scramble to embrace new technology in a scalable, compliant way, it can be difficult to know the right path forward. Your enterprise has already invested in automating processes to free up resources and improve organizational efficiency, but is it enough? This is where intelligent process automation comes into play.

Download a sample report that includes insights into the health of a Snowflake data estate.

A data pipeline is a series of processes that move raw data from one or more sources to one or more destinations, often transforming and processing the data along the way. Data pipelines are designed to automate the flow of data, enabling efficient and reliable data movement for various purposes, such as data analytics, reporting, or integration with other systems.

I have been having quite a bit of fun in this blog series exploring the “sliding doors” (or divergent paths) that organizations can take with their AI and data initiatives. The right door can lead to great value, as I covered in my previous posts on ESG reporting, data products, and responsible AI.

Kernighan & Pike, The Practice of Programming, 1999 Despite constantly changing technologies and the needs of customers, some wisdom seems eternal. Programmers need to test their code. But thorough testing takes time. When we do it well, everything works, and a massive testing effort feels like a waste. However, when we do it badly, our code is often broken, and we wish that we had done better testing. I have some good news for you.

API-database coupling vs. traditional multi-layered architectures: what’s the difference and why does it matter? The main difference between direct API-database coupling and multi-layered architectures is that the former allows the API to interact directly with the database, minimizing latency and complexity, while the latter uses multiple layers to separate concerns.

It is a fairly recent trend for companies to amass GPU firepower to build their own AI computing infrastructure and support the growing number of compute requests. Many recent AI tools now enable data scientists to work on data, run experiments, and train models seamlessly with the ability to submit their jobs and monitor their progress. However, for many organizations with mature supercomputing capabilities, Slurm has been the scheduling tool of choice for managing computing clusters.

Using BigQuery object tables, we analyze unstructured Cloud Storage data with generative AI models and join the results with BigQuery structured data.

For a software engineer, even the basic use of a debugger can save a lot of pain: adding breakpoints (places in the code the program will stop at and expose the current context) is very easy, and navigating from one breakpoint to another isn't difficult either. And with just that, you can say goodbye to a program's many puts and runs. Just add one or more breakpoints and run your program.