[{"data":1,"prerenderedAt":884},["ShallowReactive",2],{"blog-blog_en-page-7":3},{"posts":4,"totalPosts":883,"totalPages":183,"currentPage":171},[5,341,450,554,711,789],{"id":6,"title":7,"body":8,"cover":325,"date":326,"description":327,"draft":328,"extension":329,"meta":330,"navigation":331,"path":332,"seo":333,"stem":334,"tags":335,"__hash__":340},"blog_en\u002Fen\u002Fblog\u002Fki-coding-assistenten-im-produktiveinsatz-was-teams-wissen-muessen.md","AI Coding Assistants in Production: What Teams Need to Know",{"type":9,"value":10,"toc":320},"minimark",[11,15,20,23,58,62,65,91,300,304,307,316],[12,13,14],"p",{},"AI coding assistants have moved from experiment to standard tool in many development teams. The adoption rate is high, but structured rollouts with clear governance remain the exception. This creates risks that only become visible once the damage is done.",[16,17,19],"h2",{"id":18},"what-ai-assistants-do-and-do-not-do","What AI Assistants Do and Do Not Do",[12,21,22],{},"Using tools like GitHub Copilot or Cursor makes sense when strengths and limitations are clearly understood:",[24,25,26,34,40,46,52],"ul",{},[27,28,29,33],"li",{},[30,31,32],"strong",{},"Strengths:"," Boilerplate code, familiar patterns, test scaffolding, and documentation comments. Here, AI assistants accelerate development measurably.",[27,35,36,39],{},[30,37,38],{},"Weaknesses:"," Domain-specific context that only exists within your own system. AI assistants have no knowledge of internal conventions, historical decisions, or system boundaries.",[27,41,42,45],{},[30,43,44],{},"Architecture is not a strength:"," AI assistants understand syntax, not architecture. Suggestions that are syntactically correct can be structurally wrong.",[27,47,48,51],{},[30,49,50],{},"Hallucinating with confidence:"," AI-generated code often appears complete and trustworthy even when it is not. This increases risk rather than confidence.",[27,53,54,57],{},[30,55,56],{},"Same review standards as human-written code:"," AI-generated code must go through the same review process as any other code. There is no shortcut.",[16,59,61],{"id":60},"what-teams-should-clarify-before-adoption","What Teams Should Clarify Before Adoption",[12,63,64],{},"Four questions must be answered before production use:",[24,66,67,73,79,85],{},[27,68,69,72],{},[30,70,71],{},"Data privacy and cloud models:"," Which code is sent to which cloud model? Proprietary code, customer data, and regulated areas require explicit rules.",[27,74,75,78],{},[30,76,77],{},"Review process for AI-generated code:"," Who reviews, how, and with what focus? AI-generated code must not be treated as more trustworthy than manually written code.",[27,80,81,84],{},[30,82,83],{},"Responsibility when AI-generated code causes a bug:"," If AI-generated code causes a production incident, who is accountable? This question must be answered before the incident occurs.",[27,86,87,90],{},[30,88,89],{},"Which areas are suitable?"," Not every part of the codebase is appropriate for AI-assisted development. Security-critical, regulated, or highly complex areas require special care.",[92,93,98],"pre",{"className":94,"code":95,"language":96,"meta":97,"style":97},"language-yaml shiki shiki-themes github-light github-dark","# Governance checklist: AI coding assistants\ndata_privacy:\n  - cloud_model_documented: true\n  - proprietary_code_excluded: true\n  - customer_data_protected: true\nreview:\n  - ai_code_review_mandatory: true\n  - review_focus: [\"Architecture\", \"Security\", \"Domain logic\"]\naccountability:\n  - bug_process_defined: true\n  - escalation_path: \"Tech Lead\"\nsuitable_areas:\n  - allowed: [\"Boilerplate\", \"Tests\", \"Documentation\"]\n  - restricted: [\"Security\", \"Database migrations\", \"Authentication\"]\n","yaml","",[99,100,101,110,121,137,149,161,169,181,210,218,230,243,251,276],"code",{"__ignoreMap":97},[102,103,106],"span",{"class":104,"line":105},"line",1,[102,107,109],{"class":108},"sJ8bj","# Governance checklist: AI coding assistants\n",[102,111,113,117],{"class":104,"line":112},2,[102,114,116],{"class":115},"s9eBZ","data_privacy",[102,118,120],{"class":119},"sVt8B",":\n",[102,122,124,127,130,133],{"class":104,"line":123},3,[102,125,126],{"class":119},"  - ",[102,128,129],{"class":115},"cloud_model_documented",[102,131,132],{"class":119},": ",[102,134,136],{"class":135},"sj4cs","true\n",[102,138,140,142,145,147],{"class":104,"line":139},4,[102,141,126],{"class":119},[102,143,144],{"class":115},"proprietary_code_excluded",[102,146,132],{"class":119},[102,148,136],{"class":135},[102,150,152,154,157,159],{"class":104,"line":151},5,[102,153,126],{"class":119},[102,155,156],{"class":115},"customer_data_protected",[102,158,132],{"class":119},[102,160,136],{"class":135},[102,162,164,167],{"class":104,"line":163},6,[102,165,166],{"class":115},"review",[102,168,120],{"class":119},[102,170,172,174,177,179],{"class":104,"line":171},7,[102,173,126],{"class":119},[102,175,176],{"class":115},"ai_code_review_mandatory",[102,178,132],{"class":119},[102,180,136],{"class":135},[102,182,184,186,189,192,196,199,202,204,207],{"class":104,"line":183},8,[102,185,126],{"class":119},[102,187,188],{"class":115},"review_focus",[102,190,191],{"class":119},": [",[102,193,195],{"class":194},"sZZnC","\"Architecture\"",[102,197,198],{"class":119},", ",[102,200,201],{"class":194},"\"Security\"",[102,203,198],{"class":119},[102,205,206],{"class":194},"\"Domain logic\"",[102,208,209],{"class":119},"]\n",[102,211,213,216],{"class":104,"line":212},9,[102,214,215],{"class":115},"accountability",[102,217,120],{"class":119},[102,219,221,223,226,228],{"class":104,"line":220},10,[102,222,126],{"class":119},[102,224,225],{"class":115},"bug_process_defined",[102,227,132],{"class":119},[102,229,136],{"class":135},[102,231,233,235,238,240],{"class":104,"line":232},11,[102,234,126],{"class":119},[102,236,237],{"class":115},"escalation_path",[102,239,132],{"class":119},[102,241,242],{"class":194},"\"Tech Lead\"\n",[102,244,246,249],{"class":104,"line":245},12,[102,247,248],{"class":115},"suitable_areas",[102,250,120],{"class":119},[102,252,254,256,259,261,264,266,269,271,274],{"class":104,"line":253},13,[102,255,126],{"class":119},[102,257,258],{"class":115},"allowed",[102,260,191],{"class":119},[102,262,263],{"class":194},"\"Boilerplate\"",[102,265,198],{"class":119},[102,267,268],{"class":194},"\"Tests\"",[102,270,198],{"class":119},[102,272,273],{"class":194},"\"Documentation\"",[102,275,209],{"class":119},[102,277,279,281,284,286,288,290,293,295,298],{"class":104,"line":278},14,[102,280,126],{"class":119},[102,282,283],{"class":115},"restricted",[102,285,191],{"class":119},[102,287,201],{"class":194},[102,289,198],{"class":119},[102,291,292],{"class":194},"\"Database migrations\"",[102,294,198],{"class":119},[102,296,297],{"class":194},"\"Authentication\"",[102,299,209],{"class":119},[16,301,303],{"id":302},"why-this-matters","Why This Matters",[12,305,306],{},"Teams that adopt AI tools without structure often see short-term speed gains followed by long-term quality problems. Inconsistent patterns, creeping technical debt, and code paths that are difficult to trace are typical consequences of unstructured rollouts.",[12,308,309,310,315],{},"A structured enablement program prevents exactly this. The ",[311,312,314],"a",{"href":313},"\u002Fen\u002F#packages","AI Enablement"," guides teams through governance, adoption strategy, and review processes that protect the long-term value of these tools.",[317,318,319],"style",{},"html pre.shiki code .sJ8bj, html code.shiki .sJ8bj{--shiki-default:#6A737D;--shiki-dark:#6A737D}html pre.shiki code .s9eBZ, html code.shiki .s9eBZ{--shiki-default:#22863A;--shiki-dark:#85E89D}html pre.shiki code .sVt8B, html code.shiki .sVt8B{--shiki-default:#24292E;--shiki-dark:#E1E4E8}html pre.shiki code .sj4cs, html code.shiki .sj4cs{--shiki-default:#005CC5;--shiki-dark:#79B8FF}html pre.shiki code .sZZnC, html code.shiki .sZZnC{--shiki-default:#032F62;--shiki-dark:#9ECBFF}html .default .shiki span {color: var(--shiki-default);background: var(--shiki-default-bg);font-style: var(--shiki-default-font-style);font-weight: var(--shiki-default-font-weight);text-decoration: var(--shiki-default-text-decoration);}html .shiki span {color: var(--shiki-default);background: var(--shiki-default-bg);font-style: var(--shiki-default-font-style);font-weight: var(--shiki-default-font-weight);text-decoration: var(--shiki-default-text-decoration);}html .dark .shiki span {color: var(--shiki-dark);background: var(--shiki-dark-bg);font-style: var(--shiki-dark-font-style);font-weight: var(--shiki-dark-font-weight);text-decoration: var(--shiki-dark-text-decoration);}html.dark .shiki span {color: var(--shiki-dark);background: var(--shiki-dark-bg);font-style: var(--shiki-dark-font-style);font-weight: var(--shiki-dark-font-weight);text-decoration: var(--shiki-dark-text-decoration);}",{"title":97,"searchDepth":112,"depth":112,"links":321},[322,323,324],{"id":18,"depth":112,"text":19},{"id":60,"depth":112,"text":61},{"id":302,"depth":112,"text":303},"\u002Fimg\u002Fblog\u002Fki-coding-assistenten-cover.jpg","2026-03-17","GitHub Copilot, Cursor and others are productive in many teams. What teams really need to know before introducing AI tools into development.",false,"md",{},true,"\u002Fen\u002Fblog\u002Fki-coding-assistenten-im-produktiveinsatz-was-teams-wissen-muessen",{"title":7,"description":327},"en\u002Fblog\u002Fki-coding-assistenten-im-produktiveinsatz-was-teams-wissen-muessen",[336,337,338,339],"AI","Developer Tools","Engineering Leadership","Software Quality","BkFokuFPV5vW77XGDsMq_81AKNV2OihlFVqWtONUUXg",{"id":342,"title":343,"body":344,"cover":438,"date":439,"description":440,"draft":328,"extension":329,"meta":441,"navigation":331,"path":442,"seo":443,"stem":444,"tags":445,"__hash__":449},"blog_en\u002Fen\u002Fblog\u002Farchitekturentscheidungen-bewerten-ohne-entwickler-zu-sein.md","How to Evaluate Architecture Decisions Without Being a Developer",{"type":9,"value":345,"toc":433},[346,349,353,356,382,386,389,421,423,426],[12,347,348],{},"Non-technical founders face a structural challenge: they need to evaluate technical decisions they did not make and may not fully understand. The right approach is not to learn to code, but to ask the right questions.",[16,350,352],{"id":351},"questions-every-founder-should-ask","Questions Every Founder Should Ask",[12,354,355],{},"Four questions are sufficient to assess the quality of thinking behind technical decisions:",[24,357,358,364,370,376],{},[27,359,360,363],{},[30,361,362],{},"\"What are the three assumptions this architecture depends on?\""," Someone who cannot answer this has not thought the decision through. Someone who answers easily has a foundation.",[27,365,366,369],{},[30,367,368],{},"\"What breaks first if our user count doubles?\""," This tests whether scalability was actively considered or only implicitly assumed.",[27,371,372,375],{},[30,373,374],{},"\"How long would it take to onboard a new senior developer?\""," Long onboarding times are a reliable indicator of missing structural clarity in the architecture.",[27,377,378,381],{},[30,379,380],{},"\"What would we do differently if we built this today?\""," This opens honest conversations about technical debt and reveals whether the team reflects on their work or becomes defensive about it.",[16,383,385],{"id":384},"red-flags-in-technical-presentations","Red Flags in Technical Presentations",[12,387,388],{},"When a team presents technical decisions, there are warning signs that are recognizable without a technical background:",[24,390,391,397,403,409,415],{},[27,392,393,396],{},[30,394,395],{},"Complexity presented as sophistication:"," Good architecture is explainable. When complexity is sold as a quality marker, a simpler path often existed.",[27,398,399,402],{},[30,400,401],{},"No mention of trade-offs:"," Every architecture decision has costs. Someone who names none either did not consider them or does not want to communicate them.",[27,404,405,408],{},[30,406,407],{},"Only \"how\", never \"why\":"," Technical teams who only describe how something works but not why it was built that way provide no sound basis for decisions.",[27,410,411,414],{},[30,412,413],{},"Resistance to external review:"," Good architecture withstands scrutiny. Resistance to it is not a sign of quality.",[27,416,417,420],{},[30,418,419],{},"Every problem requires a rewrite:"," When the answer to every question is \"we need to rebuild this\", the ability to work within existing systems is missing.",[16,422,303],{"id":302},[12,424,425],{},"Technical due diligence is not only a task for investors. Founders who cannot evaluate their own technical foundation are dependent on the goodwill of their team. That is not a sustainable pattern for a leadership role.",[12,427,428,429,432],{},"External review provides an independent, structured perspective that is difficult to generate internally. The ",[311,430,431],{"href":313},"Architecture & AI Review"," is designed precisely for this: a neutral assessment of the technical state, understandable for non-technical leaders.",{"title":97,"searchDepth":112,"depth":112,"links":434},[435,436,437],{"id":351,"depth":112,"text":352},{"id":384,"depth":112,"text":385},{"id":302,"depth":112,"text":303},null,"2026-03-10","Non-technical founders need to assess technical decisions they didn't make. The right questions make this possible.",{},"\u002Fen\u002Fblog\u002Farchitekturentscheidungen-bewerten-ohne-entwickler-zu-sein",{"title":343,"description":440},"en\u002Fblog\u002Farchitekturentscheidungen-bewerten-ohne-entwickler-zu-sein",[446,338,447,448],"Software Architecture","Startup","Technical Debt","vbQYD32IVl4Tkj-CWfP8jFKN5hJ3o6nF9-nc7JzWcso",{"id":451,"title":452,"body":453,"cover":438,"date":544,"description":545,"draft":328,"extension":329,"meta":546,"navigation":331,"path":547,"seo":548,"stem":549,"tags":550,"__hash__":553},"blog_en\u002Fen\u002Fblog\u002Fersten-senior-entwickler-einstellen-was-gruender-falsch-machen.md","Hiring Your First Senior Developer: What Founders Get Wrong",{"type":9,"value":454,"toc":539},[455,458,462,494,498,501,527,529,532],[12,456,457],{},"The first senior developer hire is one of the most consequential decisions an early-stage company makes. This person sets the technical culture, the code standards, and often determines whether the next hires succeed or fail. Yet this decision is frequently made with the same recurring mistakes.",[16,459,461],{"id":460},"the-most-common-mistakes-in-a-senior-hire","The Most Common Mistakes in a Senior Hire",[24,463,464,470,476,482,488],{},[27,465,466,469],{},[30,467,468],{},"Optimizing for the most impressive CV:"," Recognizable companies on a resume do not mean someone will thrive in a three-person startup. Enterprise experience and startup context require fundamentally different skill sets.",[27,471,472,475],{},[30,473,474],{},"Conflating years with seniority:"," Someone with twelve years of experience in a narrow role is not automatically senior. Seniority means judgment under uncertainty, not tenure.",[27,477,478,481],{},[30,479,480],{},"Not involving the existing team:"," The hiring decision is made by founders alone, without technical perspective. The people who will work alongside this person should be part of the process.",[27,483,484,487],{},[30,485,486],{},"No technical assessment, or an irrelevant one:"," Textbook coding challenges test algorithmic knowledge, not the ability to make good technical decisions in a real context.",[27,489,490,493],{},[30,491,492],{},"No clear picture of the role:"," Should this person lead or deliver? Mentor or build? Without a clear answer, you hire for the wrong phase.",[16,495,497],{"id":496},"what-actually-matters","What Actually Matters",[12,499,500],{},"Four qualities matter more in early teams than technical depth in a single stack:",[24,502,503,509,515,521],{},[27,504,505,508],{},[30,506,507],{},"Communication and clarity:"," Can this person explain their decisions, including to non-technical stakeholders?",[27,510,511,514],{},[30,512,513],{},"Ownership mindset:"," Is the problem taken through to completion, or only the assigned part addressed?",[27,516,517,520],{},[30,518,519],{},"Breadth over depth:"," Someone effective in a small team works across product boundaries, not only within their own layer.",[27,522,523,526],{},[30,524,525],{},"Learning velocity:"," New domains, new requirements. Someone who learns quickly is more valuable long-term than someone who already knows a lot.",[16,528,303],{"id":302},[12,530,531],{},"A wrong senior hire is costly to undo: in time, money, and culture. A right one multiplies the entire team's effectiveness. The difference often lies less in the quality of candidates than in the quality of the selection process.",[12,533,534,535,538],{},"When no one internally is qualified to evaluate candidates technically, external support is the more effective investment. The ",[311,536,537],{"href":313},"Fractional Tech Lead"," can guide hiring processes, design technical assessments, and ensure the first senior hire fits the current phase of the company.",{"title":97,"searchDepth":112,"depth":112,"links":540},[541,542,543],{"id":460,"depth":112,"text":461},{"id":496,"depth":112,"text":497},{"id":302,"depth":112,"text":303},"2026-03-03","The first senior hire defines a company's technical culture. Common mistakes in the selection process and what actually matters.",{},"\u002Fen\u002Fblog\u002Fersten-senior-entwickler-einstellen-was-gruender-falsch-machen",{"title":452,"description":545},"en\u002Fblog\u002Fersten-senior-entwickler-einstellen-was-gruender-falsch-machen",[338,551,447,552],"Hiring","Technical Leadership","u4X1Mq04ZpGABguX-YctwcMPzjGNpfX9IQPI-n1GR6Y",{"id":555,"title":556,"body":557,"cover":438,"date":701,"description":702,"draft":328,"extension":329,"meta":703,"navigation":331,"path":704,"seo":705,"stem":706,"tags":707,"__hash__":710},"blog_en\u002Fen\u002Fblog\u002Fcode-reviews-die-wirklich-die-codequalitaet-verbessern.md","Code Reviews That Actually Improve Your Codebase",{"type":9,"value":558,"toc":696},[559,562,566,569,601,605,608,640,682,684,687,693],[12,560,561],{},"Code reviews are standard practice in most development teams. Yet the quality gap between effective and ineffective reviews is enormous. The difference lies not in the tooling, but in what is actually being evaluated during the review.",[16,563,565],{"id":564},"what-makes-code-reviews-ineffective","What Makes Code Reviews Ineffective",[12,567,568],{},"Poor reviews share a small set of recurring patterns:",[24,570,571,577,583,589,595],{},[27,572,573,576],{},[30,574,575],{},"Only syntax and formatting checked:"," That is what linters and formatters are for. A review that only addresses this level wastes time on both sides.",[27,578,579,582],{},[30,580,581],{},"Approval within minutes of a 500-line diff:"," A change of that size cannot be meaningfully assessed in five minutes. Fast approvals signal that nobody actually looked.",[27,584,585,588],{},[30,586,587],{},"No feedback on architecture or naming:"," Whether a function has the right name and whether the logic belongs in the right place are the critical questions. They go unasked in poor reviews.",[27,590,591,594],{},[30,592,593],{},"No questions about the purpose of the change:"," What is this code supposed to solve? A reviewer who does not ask this question only checks whether the code runs, not whether it does the right thing.",[27,596,597,600],{},[30,598,599],{},"Culture of not wanting to block colleagues:"," In many teams, rejecting a PR is considered impolite. The result is reviews without impact.",[16,602,604],{"id":603},"what-good-code-reviews-actually-accomplish","What Good Code Reviews Actually Accomplish",[12,606,607],{},"High-quality review feedback addresses different layers:",[24,609,610,616,622,628,634],{},[27,611,612,615],{},[30,613,614],{},"Intent:"," Does this change solve the right problem? Sometimes the error lies not in the code but in the underlying assumption.",[27,617,618,621],{},[30,619,620],{},"Architecture:"," Is this the right place for this logic? Does this responsibility belong in this service or this module?",[27,623,624,627],{},[30,625,626],{},"Abstraction level and naming:"," Does the name reveal what the function does? Is the abstraction introduced too early or too late?",[27,629,630,633],{},[30,631,632],{},"Test coverage for the real cases:"," Not code coverage as a metric, but whether the tests cover the scenarios that will actually occur in production.",[27,635,636,639],{},[30,637,638],{},"Small PRs as a prerequisite:"," Good reviews require small, focused pull requests. An 800-line diff cannot be reviewed meaningfully.",[92,641,645],{"className":642,"code":643,"language":644,"meta":97,"style":97},"language-diff shiki shiki-themes github-light github-dark","# Ineffective review comment:\n- \"Please add a space after the comma.\"\n\n# Effective review comment:\n+ \"This validation logic now lives in the controller. Should it not sit\n+  in the domain object so it can be reused? If we need this same rule\n+  elsewhere, we will end up copying it.\"\n","diff",[99,646,647,652,657,662,667,672,677],{"__ignoreMap":97},[102,648,649],{"class":104,"line":105},[102,650,651],{},"# Ineffective review comment:\n",[102,653,654],{"class":104,"line":112},[102,655,656],{},"- \"Please add a space after the comma.\"\n",[102,658,659],{"class":104,"line":123},[102,660,661],{"emptyLinePlaceholder":331},"\n",[102,663,664],{"class":104,"line":139},[102,665,666],{},"# Effective review comment:\n",[102,668,669],{"class":104,"line":151},[102,670,671],{},"+ \"This validation logic now lives in the controller. Should it not sit\n",[102,673,674],{"class":104,"line":163},[102,675,676],{},"+  in the domain object so it can be reused? If we need this same rule\n",[102,678,679],{"class":104,"line":171},[102,680,681],{},"+  elsewhere, we will end up copying it.\"\n",[16,683,303],{"id":302},[12,685,686],{},"The review process shapes the codebase over time more than any single architectural decision. Teams without effective reviews accumulate patterns they later regret: inconsistent abstractions, scattered responsibilities, code that is hard to test. That is not a technical problem; it is a leadership problem.",[12,688,689,690,692],{},"Teams looking to reset their review process benefit from an external perspective. The ",[311,691,537],{"href":313}," supports teams in systematically improving review culture and quality.",[317,694,695],{},"html .default .shiki span {color: var(--shiki-default);background: var(--shiki-default-bg);font-style: var(--shiki-default-font-style);font-weight: var(--shiki-default-font-weight);text-decoration: var(--shiki-default-text-decoration);}html .shiki span {color: var(--shiki-default);background: var(--shiki-default-bg);font-style: var(--shiki-default-font-style);font-weight: var(--shiki-default-font-weight);text-decoration: var(--shiki-default-text-decoration);}html .dark .shiki span {color: var(--shiki-dark);background: var(--shiki-dark-bg);font-style: var(--shiki-dark-font-style);font-weight: var(--shiki-dark-font-weight);text-decoration: var(--shiki-dark-text-decoration);}html.dark .shiki span {color: var(--shiki-dark);background: var(--shiki-dark-bg);font-style: var(--shiki-dark-font-style);font-weight: var(--shiki-dark-font-weight);text-decoration: var(--shiki-dark-text-decoration);}",{"title":97,"searchDepth":112,"depth":112,"links":697},[698,699,700],{"id":564,"depth":112,"text":565},{"id":603,"depth":112,"text":604},{"id":302,"depth":112,"text":303},"2026-02-24","Code reviews are a ritual without impact in many teams. What separates effective reviews from ineffective ones and how to reset the process.",{},"\u002Fen\u002Fblog\u002Fcode-reviews-die-wirklich-die-codequalitaet-verbessern",{"title":556,"description":702},"en\u002Fblog\u002Fcode-reviews-die-wirklich-die-codequalitaet-verbessern",[708,338,339,709],"Code Review","Backend Development","JlB-x34J5deU9CrVPQSIEdQB_vavAyzZsf6iuRgJKlU",{"id":712,"title":713,"body":714,"cover":438,"date":781,"description":782,"draft":328,"extension":329,"meta":783,"navigation":331,"path":784,"seo":785,"stem":786,"tags":787,"__hash__":788},"blog_en\u002Fen\u002Fblog\u002Fwas-ein-fractional-tech-lead-woche-fuer-woche-tut.md","What a Fractional Tech Lead Actually Does: A Typical Week",{"type":9,"value":715,"toc":776},[716,719,723,726,752,755,759,762,765,767,770],[12,717,718],{},"The concept of a fractional tech lead is still unfamiliar to many companies. The question that comes up most often is not \"do we need technical leadership?\" but rather \"what would that person actually do?\". The answer is less abstract than most expect.",[16,720,722],{"id":721},"typical-tasks-in-a-week","Typical Tasks in a Week",[12,724,725],{},"A typical week in a fractional engagement covers four core areas:",[24,727,728,734,740,746],{},[27,729,730,733],{},[30,731,732],{},"Architecture decision reviews:"," Technical proposals are reviewed and hard questions are asked, not to block progress but to ensure decisions are made deliberately with the right trade-offs considered.",[27,735,736,739],{},[30,737,738],{},"Pull requests and code reviews:"," The focus is on patterns, abstraction levels, and architecture rather than syntax. Selected reviews are commented in depth to generate knowledge transfer across the team.",[27,741,742,745],{},[30,743,744],{},"Weekly alignment with founders or the product team:"," Technical reality and product priorities are synchronized. Bottlenecks are named early, before they become emergencies.",[27,747,748,751],{},[30,749,750],{},"Identifying the next technical bottleneck:"," Based on current velocity and codebase signals, the next area for investment is identified and prioritized.",[12,753,754],{},"In practice, this often means one day for sprint review and architecture alignment, another for PR reviews and developer feedback, and a third block for founder sync, technical roadmap, and prioritisation. Availability is typically two to three days per week.",[16,756,758],{"id":757},"what-a-fractional-tech-lead-is-not","What a Fractional Tech Lead Is Not",[12,760,761],{},"Distinctions matter more than definitions here. A fractional tech lead is not a senior developer billing hours on feature work. The engagement is strategic, not operational. Nor is it a consultant who delivers a report and leaves: the collaboration is continuous, with a direct feedback channel to the team.",[12,763,764],{},"A fractional tech lead does not replace a full engineering team and is not a CTO in the traditional sense. No equity, no executive overhead, no five-year commitment. That is precisely what makes the model attractive for companies in a growth phase.",[16,766,303],{"id":302},[12,768,769],{},"For companies with 3 to 15 engineers, unguided technical decisions are the most common cause of scalability crises later on. Decisions made without structure accumulate. Technical debt does not come from bad code; it comes from good decisions that nobody coordinated.",[12,771,772,773,775],{},"A fractional engagement gives this stage structure without the cost of a senior executive hire. The ",[311,774,537],{"href":313}," is designed for exactly this phase: technical leadership when it is needed, without long-term commitment.",{"title":97,"searchDepth":112,"depth":112,"links":777},[778,779,780],{"id":721,"depth":112,"text":722},{"id":757,"depth":112,"text":758},{"id":302,"depth":112,"text":303},"2026-02-17","Fractional Tech Lead sounds abstract. In practice it means architecture decisions, code reviews, hiring support, and technical strategy, 2-3 days per week.",{},"\u002Fen\u002Fblog\u002Fwas-ein-fractional-tech-lead-woche-fuer-woche-tut",{"title":713,"description":782},"en\u002Fblog\u002Fwas-ein-fractional-tech-lead-woche-fuer-woche-tut",[537,552,338,708],"OtYt0lBJjtqh_IUCKR3Ra-N866hOicgJu_1oVm1KCyw",{"id":790,"title":791,"body":792,"cover":438,"date":875,"description":876,"draft":328,"extension":329,"meta":877,"navigation":331,"path":878,"seo":879,"stem":880,"tags":881,"__hash__":882},"blog_en\u002Fen\u002Fblog\u002Ffractional-tech-lead-wann-er-besser-ist-als-ein-vollzeit-cto.md","Fractional Tech Lead: When It Beats Hiring a Full-Time CTO",{"type":9,"value":793,"toc":870},[794,797,801,804,836,839,843,862,864],[12,795,796],{},"Hiring a full-time CTO too early is one of the most common and expensive mistakes early-stage teams make. The salary, the expectations, and the recruiting effort frequently exceed the actual need by a significant margin. The question is not whether technical leadership is needed, it is needed, but rather in what form and at what point in time.",[16,798,800],{"id":799},"what-a-fractional-tech-lead-can-deliver","What a Fractional Tech Lead Can Deliver",[12,802,803],{},"A Fractional Tech Lead brings technical seniority without the full-time overhead structure of an executive hire. In practice, this means:",[24,805,806,812,818,824,830],{},[27,807,808,811],{},[30,809,810],{},"Architecture decisions"," grounded in experience rather than trial and error within the team",[27,813,814,817],{},[30,815,816],{},"Code reviews"," and technical standards that keep quality at a sustainable level",[27,819,820,823],{},[30,821,822],{},"Hiring support:"," evaluating technical candidates, defining role requirements",[27,825,826,829],{},[30,827,828],{},"Stakeholder communication:"," translating technical complexity into business language",[27,831,832,835],{},[30,833,834],{},"2 to 3 days per week"," of engagement, without the fixed costs of a full-time employee",[12,837,838],{},"A Fractional Tech Lead is not an on-call interim CTO but a focused technical partner with a clearly defined scope.",[16,840,842],{"id":841},"typical-situations-where-a-fractional-tech-lead-makes-sense","Typical Situations Where a Fractional Tech Lead Makes Sense",[12,844,845,846,849,850,853,854,857,858,861],{},"The need arises in predictable constellations. ",[30,847,848],{},"Teams of 2 to 8 engineers with no technical leader:"," The developers are capable, but nobody carries responsibility for architecture decisions. Everyone decides locally; nobody decides globally. ",[30,851,852],{},"Non-technical founders who need a trusted technical partner:"," Without technical judgment in the leadership team, dependency on the development team is entirely uncontrolled. ",[30,855,856],{},"Teams growing faster than their architecture can support:"," New developers are hired, but the structural prerequisites for good onboarding and productive collaboration are absent. ",[30,859,860],{},"Companies that need senior technical judgment but cannot justify a full-time executive:"," The economic reality of many growth phases sits precisely in this in-between space.",[16,863,303],{"id":302},[12,865,866,867,869],{},"Technical leadership gaps compound quickly. A team without architectural authority makes dozens of small decisions every day that add up to an unmaintainable codebase. This is not a criticism of the developers; it is a structural consequence of absent leadership. The ",[311,868,537],{"href":313}," is a concrete offering for companies in exactly this situation: technical leadership on a defined engagement, with clear scope and no long-term executive commitment.",{"title":97,"searchDepth":112,"depth":112,"links":871},[872,873,874],{"id":799,"depth":112,"text":800},{"id":841,"depth":112,"text":842},{"id":302,"depth":112,"text":303},"2026-02-10","A full-time CTO is too early and too expensive for many teams. A Fractional Tech Lead delivers technical leadership without long-term commitment.",{},"\u002Fen\u002Fblog\u002Ffractional-tech-lead-wann-er-besser-ist-als-ein-vollzeit-cto",{"title":791,"description":876},"en\u002Fblog\u002Ffractional-tech-lead-wann-er-besser-ist-als-ein-vollzeit-cto",[537,552,447,338],"V3V--Sv2J89Zm8b2r8BRLEIidmCwEdJBbD8UsOiNtXs",46,1781596426568]