I use AI coding agents every day. I believe they are reshaping how we build software, and I think the teams that adopt them deliberately will outperform those that don't. I am not writing this to warn you away from AI-assisted development. I am writing this because the loudest voices in the AI enthusiasm camp are also the most allergic to discussing what can go wrong. And that worries me more than
Data is no longer treated as a byproduct of business operations and has become one of the most valuable organizational assets. Every interaction on a banking application, e-commerce platform, hospital system, logistics network or social media service generates data continuously. As organizations increasingly adopt digital workflows, cloud platforms, machine learning systems and real-time applicati
In modern data-driven organizations, managing and analyzing data efficiently is critical. OLAP (Online Analytical Processing) and OLTP (Online Transaction Processing) are both integral parts of data management, but they have different functionalities. Understanding how they differ, and how they complement each other is essential for anyone working with data systems. Online Transaction Processing (
SQL is widely known for data querying and manipulation but systems do grow; data becomes larger; processes become repetitive and operations become sensitive. SQL has some features which enables it to be considered a fully fledged programming language. Some of the features which I discuss in this article are procedures, functions and transactions. Each of these concepts serve distinct purposes. Sto
On Second Thought — Episode 06 The ORM hides the SQL. The cache hides the ORM. The service mesh hides the services. The operator hides the YAML, which already hid the kubelet, which already hid the container, which already hid the process. By Tuesday, nobody quite remembers what the original problem was. They are too busy configuring its sixth wrapper. This is the post about that wrapper. When som
選定理由 Paper: https://arxiv.org/abs/2512.01020 【社会課題】 【データの設計と従来技術の限界】 Issue Tree（法的論点ツリー）に変換し、葉ノードに対しルーブリック基準を適用可能にした。原告・被告・裁判所の主張をツリー構造で整理した約24,000インスタンスのデータセットを構築。評価軸は「論点カバレッジ」と「正確さ」の2次元。以下がサンプルである： 【原告の主張】被告は540万円を支払え └─【原告】保険金の支払い義務がある ├─【原告】死亡は突発的・偶発的な事故だった │ └─【原告】餅を食べて窒息死＝外因による傷害 │ └─【被告】死因は既往症の可能性が高い └─【裁判所の結論】突発的事故と認定 ただし窒息死は証明不十分 この
Every team experiences incidents. The teams that grow stronger from them are the ones that take postmortems seriously — not as blame sessions, but as structured learning opportunities. Yet most postmortems end up as a wall of text nobody reads twice, filed away and forgotten until the same incident happens again six months later. This guide walks you through writing postmortems that genuinely chan
If you are stepping into the world of data engineering or analytics, you have likely been hit with a wave of storage buzzwords like data lake and data warehouse. In this article, we will demystify these terms so you can understand exactly where your data belongs. Imagine you just launched a business. You need a system to record daily operations every time a customer buys a product, updates their