# Peter Fulop > Peter Fulop — Senior Data Engineer writing about career growth, leadership, data engineering, and AI-assisted development. Peter Fulop is a Senior Data Engineer writing for software and data engineers about scalable data platforms, AI-assisted engineering workflows, and Staff-level technical leadership. The site contains practical essays and technical notes rather than beginner tutorials or product documentation. ## Profile - [About](https://peterfulop.tech/about/): Senior Data Engineer focused on scalable data systems, AI-assisted workflows, and Staff-level technical leadership. - [Resume](https://peterfulop.tech/resume/): My professional resume ## Primary topics - [AI-Assisted Development](https://peterfulop.tech/tags/ai-assisted-development/): Practical guidance on coding agents, AI-assisted engineering workflows, code quality, and keeping human judgment at the center of software delivery. - [Engineering Effectiveness](https://peterfulop.tech/tags/engineering-effectiveness/): Practical essays on the technical and organizational habits that help engineering teams deliver useful work without sacrificing system health. - [Engineering Judgment](https://peterfulop.tech/tags/engineering-judgment/): Practical essays on making sound software and data engineering decisions under uncertainty, including tradeoffs, risk assessment, YAGNI, and responsible AI use. - [Staff Engineering](https://peterfulop.tech/tags/staff-engineering/): Practical guidance for senior engineers developing Staff-level influence through technical direction, sound judgment, visible impact, and trust. - [Claude Code](https://peterfulop.tech/tags/claude-code/): Practical Claude Code workflows for agent teams, Git worktrees, Python tooling, and reliable AI-assisted software development. - [Python](https://peterfulop.tech/tags/python/): Practical Python engineering guidance on code quality, logging, uv-based workflows, developer tooling, and maintainable software practices. ## Categories - [Career notes](https://peterfulop.tech/categories/career-notes/): Growth, promotions, levels, mindset - [Communication](https://peterfulop.tech/categories/communication/): Writing, speaking, influence, feedback - [Engineering Culture](https://peterfulop.tech/categories/engineering-culture/): Team dynamics, trust, collaboration, and healthy engineering habits - [Leadership](https://peterfulop.tech/categories/leadership/): Technical leadership, mentoring, trust, and helping engineering teams become more effective. - [Productivity](https://peterfulop.tech/categories/productivity/): Focus, time management, getting things done - [Shaping with AI](https://peterfulop.tech/categories/shaping-with-ai/): AI tools, workflows, impact, prompt engineering - [Technical notes](https://peterfulop.tech/categories/technical-notes/): Data engineering, system design, architecture ## Recent writing - [Using AI to become a team multiplier: a mindset that makes the people around you more effective - part 1](https://peterfulop.tech/p/how-ai-can-help-you-become-a-team-multiplier-part-1/): A practical reflection on building a team multiplier mindset with AI: sharing context in code reviews, learning together through pair programming, and writing documentation that helps the whole team move faster. - [Software solutions do not start with code](https://peterfulop.tech/p/software-solutions-do-not-start-with-code/): I can move from idea to code faster with AI, but the real work still starts before that: asking better questions, spotting constraints, and building the right mental model. - [Switching from doing to directing](https://peterfulop.tech/p/switching-from-doing-to-directing/): As AI takes over more of the mechanical work, engineers at every level need to learn how to direct, verify, and own what gets shipped. This article reflects on why that mindset should start early, not only at senior level. - [How I used Cortex Code Desktop to assess the risks in Snowflake's upcoming behavior change bundle](https://peterfulop.tech/p/using-cortex-code-desktop-to-assess-snowflake-behavior-change-bundle-risks/): Snowflake rolls out semantic and breaking changes through behavior change bundles. Before a bundle becomes the default, there is a window to test how those changes might affect your workloads. In this article, I show how I used Codex and later Cortex Code Desktop to assess the risks, identify likely breakpoints in our Airflow and dbt pipeline, and map out likely fixes before the bundle lands. - [Effectiveness anti-patterns — part 6: YAGNI: don’t abstract before the second use case](https://peterfulop.tech/p/yagni-dont-abstract-before-the-second-use-case/): A practical YAGNI story from data engineering: keeping a CI workflow intentionally narrow until the second real use case appeared. - [From principles to production](https://peterfulop.tech/p/from-principle-to-production/): Why AI makes engineering fundamentals more important, not less, and how they shape real production decisions. - [How I improved AI-generated Python code by setting clear instructions](https://peterfulop.tech/p/improving-ai-generated-python-code-quality/): A reflection on turning one AI-generated Python prototype into reusable coding-agent guidance: clearer implementation boundaries, stronger quality expectations, and a shared quality bar before prototypes become real tools. - [Effectiveness anti-patterns — part 5: when good work is invisible work](https://peterfulop.tech/p/invisible-work-make-the-work-legible/): A reflection on invisible work in platform and data engineering teams: why success often looks like silence, why the work-speaks-for-itself instinct breaks at the senior-to-staff transition, and what I have tried to make my work more legible to people I don't sit next to. - [Parallel agents hit a human limit faster than a system limit](https://peterfulop.tech/p/parallel-agents-hit-a-human-limit-faster-than-a-system-limit/): Running multiple coding agents in parallel feels like a speed win until the bottleneck becomes the person trying to supervise all of them. - [Effectiveness anti-patterns — part 4: meeting overload](https://peterfulop.tech/p/meeting-overload-attendance-isnt-contribution/): A reflection on meeting overload: why every invitation deserves real scrutiny, why three to four meetings a day make focused engineering work much harder, and why leaving the room when I cannot contribute can be the responsible move. - [How to set up a Claude Code agent team workflow: from parallel tasks to peer review](https://peterfulop.tech/p/how-to-set-up-a-claude-code-agent-team-workflow/): A practical walkthrough of setting up Claude Code agent teams with clear roles, task ownership, communication rules, review steps, and lightweight output contracts. - [Orchestrating parallel subagents for data collection, exploration, and reporting](https://peterfulop.tech/p/orchestrating-parallel-subagents-for-data-collection-exploration-and-reporting/): A hands-on case study of using Codex subagents to coordinate data collection, preparation, and Slidev report generation in parallel.