Japanese sources

Japanese-language research, company posts and talks, summarised in English.

24 sources filed

Week 43 · 19-25 Oct

13 sources filed · JA 13

  • B

    Hard-to-read DB schemas make AI development cost 1.9x

    Seven contrasts: naming (orders vs ord), column comments, value meaning ('cancelled' enum vs sts = 9), type (datetime vs char(14)), foreign keys, soft delete (deletedat vs dflg = 'Y'), and price columns (unitpriceexcludingtax vs prca).

    1.9xcost and output tokens for the obscured schema versus the readable one ($0.41 vs $0.21 per run)

  • B

    Ota Ward's AI phone pilot

    FY2025: callers asked about eligibility for subsidised earthquake breakers and furniture anchors.

    ~40%calls the AI handled effectively in the FY2025 disaster-prevention pilot, against an 80% goal

  • C

    Panasonic Connect CHRO: directives don't change people

    The inherited B2C culture (good, cheap, fast, top-down execution) was too heavy and slow for B2B work, where staff must read each customer's needs and act on their own.

    2022year Panasonic Connect was carved out as a B2B company in the holding-company restructure

  • B

    Automating sentiment on all X mentions with Jev

    Three questions per post: relevance (is the service the subject, not just named), one of eight categories, and five-level sentiment with an instruction to read sarcasm by intent.

    ~$5/monthJev classification cost; X API reads at $0.005 per post are the main expense

  • B

    LayerX's in-house background coding agent "haro"

    Motivation: local machines run out of memory before people run out of attention when running parallel worktrees on a large monorepo; generic products fit the codebase and internal tools poorly.

    55-60%share of the monorepo's daily PRs created through haro by October 2026

  • B

    Matching engineers to projects with Jev vs. LLMs and embeddings

    Data: five fictional projects and eight fictional engineers (40 pairs), drafted by Claude and reviewed by a person, including hard cases such as an overqualified tech lead and a vague self-assessor.

    0.87 / 0.78 / 0.47Kendall tau-b against Opus 5.5 labels for Jev, Haiku 4.5 and the ruri embedding model

  • B

    Saga City: generative AI in daily municipal work

    Structure: a mayor-chaired DX headquarters, one DX promoter per division, Code for Japan as support team.

    ~70%share of Saga City staff using generative AI (ChatGPT) in a June 2026 survey

  • B

    AI writes, reviews and QAs; I started thinking of my role as director

    Four skills: ship (ticket to merge, including CI fixes and replies to review comments), plan-checker (design review by other agents before risky work such as migrations or auth changes), pr-checker (parallel review by aspect, with a second agent challenging each finding) and devqa (runs QA scenarios in the dev environment and files bugs).

    211PRs the author created and merged to main in 16 business days (24 Sep to 16 Oct 2026)

  • A

    What we saw after removing code review

    Concepts are GitHub issues with Why, Outcome, Boundaries and AI Findings, sized minor, quick or full.

    97% to under 10%share of merged PRs with a human approval, before versus after April 2026

Week 42 · 12-18 Oct

11 sources filed · JA 11