1import"../chunks/DsnmJJEf.js";import"../chunks/DIHxWcDZ.js";import{f as i,b as r,n as l}from"../chunks/hPEmA7oG.js";import{l as p,s as d}from"../chunks/7zTA4vzK.js";import{A as h}from"../chunks/DuJsthP_.js";const e={title:"What will be the Gen AI equillibrium?",description:null,slug:null,image:null,published:!1,published_at:null,tags:["ai","git","productivity","claude-code"]},{title:y,description:$,slug:_,image:v,published:k,published_at:A,tags:I}=e;var c=i('<p>In a matter of weeks (or even days), the pendulum of the opinion on the place of where AI will finally settle swung completely the other way. After a new set of layoffs, several weird pieces of information came out that supported the weird turnaround in the opinion â weâre seeing companies clamp down on gen AI usage by developers and even discourage its (over) use.</p> <p>We went from AI leaderboards to âuse it when necessaryâ. This was a shock to a lot of developers including me. The corporate world that had been quietly (and loudly) chanting âBurn more tokensâ is now scaling back and wanting to be more cautious. Unfortunately, this turnaround seem to be focused more on the cost of tokens and less on the impact of those tokens.</p> <h2 id="the"><a class="heading-anchor" aria-label="Link to this section" href="#the"><span class="heading-anchor-icon">#</span></a>The</h2>',1);function T(t,o){const a=p(o,["children","$$slots","$$events","$$legacy"]);h(t,d(()=>a,()=>e,{children:(s,u)=>{var n=c();l(4),r(s,n)},$$slots:{default:!0}}))}export{T as component};
Line numbers count LF bytes from the start of the resource, as the search results do. Vendor segments are library code the classifier recognised; they are stored but not indexed. Bytes are shown as Latin1 characters, one per byte.