Suggestions
Joel Cochran
Azure Big Data | Automation | Cloud & Software Development
Joel Cochran is the Vice President of Technology at Causeway Solutions, LLC.12 In this role, he is responsible for overseeing the company's technological initiatives and strategies.
Background and Experience
Prior to joining Causeway Solutions, Joel served as a Technical Evangelist on the Microsoft Campaign Technology Services team.2 In this capacity, he worked with numerous campaigns and committee partners throughout the country during the 2016 presidential campaign cycle, providing technical expertise and support.2
Joel has an extensive background in the technology industry, with his career dating back to 1992.4 He began his professional journey as a Staff Sergeant in the US Army before transitioning to the private sector and joining HTE, Inc.4
Education
Joel Cochran received his education from Liberty University3, though the specific degree or field of study is not mentioned in the available information.
Current Role and Responsibilities
As the Vice President of Technology at Causeway Solutions, Joel plays a crucial role in:
- Overseeing the company's technological infrastructure
- Developing and implementing technology strategies
- Ensuring that the company remains at the forefront of technological advancements in the data and analytics field
Location
Joel is based out of Valparaiso, Indiana, United States5, although Causeway Solutions has its main office in Metairie, Louisiana.1
Joel Cochran's expertise in technology, combined with his experience in political campaigns and data analytics, makes him a valuable asset to Causeway Solutions as they provide data services and actionable analytics to clients across various sectors.
Highlights
As I celebrate my 7th anniversary at Causeway Solutions, I'm reflecting on the data engineering and technology changes I’ve experienced during my tenure.
Causeway Solutions was a customer of mine when I worked at Microsoft, and I was able to see first-hand the challenges they had with very large datasets. They were using large SQL Server VMs and I introduced them to Polybase, which cut their ingestion processing time in half. This was one of my first real experiences in large-scale data-engineering and it was very rewarding. Shortly after, I joined Causeway Solutions full-time.
Causeway Solutions had just begun adopting Azure Data Lake Analytics (ADLA), which was a Microsoft proprietary Massive Parallel Processing (MPP) offering in Azure. The code language in that system was U-SQL, a mashup of C# and SQL. I remember really liking that language, but apparently I'm in the minority on that one: I once asked the Synapse team to bring it back - the request was politely declined. ADLA had its share of problems, but it was the first time we were able to really process large amounts of text files in Azure Blob Storage. Among ADLA's challenges, the complete lack of an interactive mode was the most problematic for us. Plus there was the time I personally crashed the ADLA service by implementing a Regular Expression that was too large for the deployed version of .NET, but I digress.
Azure SQL Data Warehouse (SQLDW) Gen1 was too limited, but when Gen 2 released it finally had the features we needed. We spent a fair amount of time and energy migrating our workloads to SQLDW, but it paid off in the long run. This was the first time we were able to run interactive queries over our data and get results in a reasonable timeframe. We learned a lot about performance tuning, partitioning, and distribution schemes in the process.
A couple years into this phase, Azure Synapse arrived and we became early (pre-GA) adopters. It was the natural successor to SQLDW, which was rebranded "Dedicated Pools" in Synapse but was really SQLDW Gen3. As we learned more about Serverless SQL and Spark Notebooks, we quickly gravitated to a purely Storage based infrastructure. We heavily leverage Pipelines, Data Flows, and Notebooks to process frequent but irregular updates from numerous sources. Synapse has worked extremely well for us and serves today as our primary Data Engineering platform.
That does not mean we are set by any stretch! We have worked for the past year with Microsoft Fabric primarily in support of our Power BI and Reporting needs. While the promise of Fabric is not yet fully realized, it is exciting to see what may be possible in the near future. As we push further into the Fabric realm, I fully expect more of our processes to migrate to "Fabric first" solutions.
That's five major systems in seven years. It has been a great time full of changes and challenges. I'm excited to see what comes next!
https://lnkd.in/ej44d5dE
This grabs my attention because it reflects my own concerns as a technologist: “When AI is mentioned, it tends to lower emotional trust, which in turn decreases purchase intentions,” he said. “We found emotional trust plays a critical role in how consumers perceive AI-powered products.”
