logo
Kurashizu Blogwhere ideas flow
  • Home
  • News
  • Blog
  • About
  • Home
  • News
  • Blog
  • About

© 2026 Kurashizu. All rights reserved.

Admin·New Post·Service Status
Powered by Cloudflare·01.11.26
← Back to news

Guide to data tools landscape for developers

Original article
sinja.io|50 points|12 comments|by OlegWock|Jul 16, 2026

Navigating the Data Tooling Ecosystem: A Developer's Primer

Have you ever stepped into a data-centric project and felt like everyone was speaking a foreign language? Perhaps you've felt like an outsider during those "watercooler" chats where the air is thick with jargon you don't recognize.

"I used to think software engineering and data science were basically the same thing—just adjacent fields. I knew what a notebook was, so I figured I'd be fine. I was wrong."

Upon joining a data-focused team, I quickly discovered a humbling truth: I knew almost nothing. Beyond the notebook, there was a massive universe of tools, workflows, and processes that I couldn't name, let alone understand. This gap in knowledge was a blocker; if I didn't understand how these tools interacted or how a data scientist actually worked, I couldn't design a better UI or suggest meaningful features.

After an exhaustive period of reading, interviewing colleagues, bothering strangers online, and analyzing client pain points, the fog finally lifted. I realized there wasn't a comprehensive "Rosetta Stone" for software engineers entering the data space. Even though I've moved on from notebook development, my passion for data stuck, and I've continued working in the field—this time focusing on tools for analytical specialists.

I've written this guide to condense that learning curve for other "lost" developers.

🎯 Who is this for?

Let's be clear: I am trying to teach you how to become a data scientist. This is not a course on statistics, a manual for administering a Spark cluster, or a tutorial on building Metabase dashboards.

Instead, this is for the developer who needs to understand the context of the data team's conversations.

What we will cover:

  • The general data lifecycle.
  • Where data originates and how it is stored.
  • How data is processed and eventually visualized.
  • The specific roles within a data team and the tools they use.

Note: We won't be doing deep-dive comparisons or installation guides. That would make this article an encyclopedia.


🔄 The Data Lifecycle

To understand the tools, you first have to understand the flow. Data isn't just "there"; it moves through a pipeline.

Data Flow Illustration


👥 The Four Flavors of Data Professionals

In many companies (especially startups), these roles overlap. However, conceptually, they break down into four distinct types.

1. The Analytical Type

These specialists are the "interpreters." Their goal is to extract business insights and present them to stakeholders.

  • Primary Tools: SQL, Excel, and BI (Business Intelligence) platforms like Tableau.
  • Typical Workflow: They might write a query to find the churn rate per region and then build a dashboard to show marketing why customers are leaving.

Example Calculation: They might calculate the churn rate using a formula like: Churn Rate=Customers Lost during PeriodTotal Customers at Start of Period×100\text{Churn Rate} = \frac{\text{Customers Lost during Period}}{\text{Total Customers at Start of Period}} \times 100Churn Rate=Total Customers at Start of PeriodCustomers Lost during Period​×100

2. The Scientific Type

These are the "deep divers." They don't just report what happened; they try to predict what will happen using statistics and experimentation.

  • Primary Tools: Python and the scientific stack (pandas, scikit-learn), almost always working within notebooks.
  • Typical Workflow: Using the same churn data as the analyst, they might build a model to identify the correlation between specific user behaviors and the likelihood of leaving, then run an A/B test to validate a solution.
# A simplified glimpse into a Scientific Type's notebook
import pandas as pd
from sklearn.linear_model import LogisticRegression

# Predicting churn
model = LogisticRegression()
model.fit(X_train, y_train)
predictions = model.predict(X_test)

3. The Engineering Type

The "architects." They build the plumbing that makes the other roles possible. Without them, the analysts and scientists would have no clean data to work with.

  • Primary Tools: Apache Spark, various databases, cloud infrastructure (AWS/GCP/Azure), and Python.
  • Typical Workflow: They build pipelines to ingest raw transaction data, standardize the schemas, and load it into a warehouse. They also scale the "scripts" written by scientists into production-ready reverse ETL pipelines.

4. The Machine Learning (ML) Type

The "AI specialists." Their focus is specifically on the creation and maintenance of AI models.

  • Focus: This ranges from small-scale classification models (e.g., is this user a bot?) to massive Large Language Models (LLMs) that are fine-tuned for company-specific data.

📊 Summary Comparison Table

RolePrimary GoalKey ToolsCore Skill
AnalyticalBusiness InsightTableau, SQL, ExcelData Interpretation
ScientificPrediction/TestingNotebooks, pandasStatistics/Modeling
EngineeringInfrastructureSpark, Cloud, WarehousesPipeline Architecture
ML TypeAI ImplementationPyTorch, TensorFlow, LLMsModel Training/Tuning