- > Dr. Jason Wingard is a globally recognized executive with deep experience across corporate, nonprofit, and academic sectors, specializing in the future of learning and work.He currently serves as Senior Advisor at Harvard University, where he advises trustees, senior administrators, and faculty leaders, and leads a research agenda on workforce transformation and innovation. He is also Executive Chairman of The Education Board, Inc. and Senior Advisor at Social Finance, Inc., providing strategic and visionary consulting while advancing a national research agenda on leadership and workforce development.He most recently served as the 12th President of Temple University, where he held dual tenured faculty appointments as Professor of Management and Professor of Policy, Organizational, and Leadership Studies.Previously, Dr. Wingard was Dean of the School of Professional Studies at Columbia University and Managing Director and Chief Learning Officer at Goldman Sachs. Earlier, he served as Vice Dean of the Wharton School, University of Pennsylvania; President & CEO of the ePals Foundation and Senior Vice President at ePals, Inc.; and held leadership roles with the Aspen Institute, Vanguard Group, Silicon Graphics, Inc. (SGI), and Stanford University.An award-winning author, Dr. Wingard has published widely on leadership, learning, and workforce strategy.
Not sure exactly what this guy does or what his expertise is, but I am fairly certain it’s not software development.
by Incipient
6 subcomments
- I'm sure a vibe coded internal or external application WILL break a company. The thought process is however, out of 10 companies:
- 2 won't use AI at all and simply be left behind and stagnate (or go bust)
- 2 will partly use AI, and maybe keep up, maybe not
- 1 will go nuts vibe an entire app and explode (see Tea app or whatever)
- 4 will have an inefficient app, suffer reputational damage, lose some money, or similar, but probably survive
- 1 will hit the jackpot and get a 100M ARR company with 4 people.
Stats are of course completely made up, but you get the point.
- I read it in a report:
AI amplifies. It amplifies the success of the good professionals and amplifies the failures of the bad ones.
In all cases, whole enterprise solution can't be made with pure vibecoding. Specification is needed, a basis of predefined rules, coding styles, security considerations.
- So the article isn't very good but the vibe coding debate is pretty interesting.
This is how I'm thinking about it: in a scenario with increased opportunity and risk... You've gotta know where you stand.
First question is how much is more software actually worth to you."
This is one with a lot of self deception. Software development is expensive. The companies have to do lists and wishlist and road maps. They have an A/B testing system and a productivity mindset.
But... If Linkedin, Salesforce or any whatnot really did have ways of producing software to make money... they would have done it already. Remaining opportunities follow a diminishing marginal value curve/cliff.
Imo, software development isn't necessarily a bottleneck. So... opportunity is limited and risk is the bigger deal.
The opportunity is at the upstart trying to bootstrap feature parity with Salesforce.
If you have no customers yet... you can unfettter the vibe and see if it works.
Imo companies need to revisit google's early days. Let a thousand flowers bloom. 20% time. If you unleash capable people and give them tokens .. That's a good way of searching for opportunities.
The thousand flowers died at Google because they had reached a point where opportunities are not everywhere. The best ideas had been discovered and also... the markets big enough to move Google's dial are few. There aren't many $100bn markets.
There's no way to do vibe coding safely, at scale, currently.
by chromacity
4 subcomments
- Third evidently AI-generated "AI is bad" story in a day. I'm gonna lose it...
by 2001zhaozhao
2 subcomments
- > Speed without judgement is a liability
So, what's the alternative?
Speed without judgement? (Maybe you'll be fine. Or maybe your business gets run to the ground by spaghetti code piling up beyond any hope for human review and quality controls breaking)
Judgement without speed? (That startup next door led by a 4-people visionary team and a bunch of AIs stomps over your 100-person company in ability to ship)
Judgement + speed at the same time? (layoff most of your employees and keep only the visionaries? how do you even filter for people who can make good decisions?)
by bluesaddoll
0 subcomment
- These articles are such doomsaying, yesterday's clickbait. Again, the worst-case scenario is being introduced as the one that will surely happen to your company.
- Is anyone really vibe coding like this?
I mean if someone without any coding skills vibe codes a whole app, cannot expect that this is production ready..
i think anybody with common sense should know this right?
- > The bottleneck in the AI era is not production. It is discernment.
> The right question to ask after a vibe-coded prototype fails is not what did the AI do wrong. It is what did our process miss.
> That is a governance story, not a software story.
> The Question Is Not Adoption. It Is Readiness.
> The right question is diagnostic, not strategic.
I don't know if AI will fully replace programmers, but it has already replaced writers of this type of bullshit puff piece.
- The question is, when it screws up, who gets blamed, and who pays. If it's the customer, and you can afford to lose a small fraction of customers, it may be worth it. It's just another form of crappy customer service. If it's internal, and it's all output, no input, and the internal organization doesn't really need that info that badly, that might work out.
But give it the authority to do something and there's real trouble.
by aussieguy1234
1 subcomments
- The faster you go with vibe coding, the more of a mess you'll get yourself into
by wewewedxfgdf
0 subcomment
- More hysterical over reaction to AI.
by blurbleblurble
1 subcomments
- "This is what vibe coding is about to expose across businesses. The companies that think the story is about software are going to lose to the companies that understand the story is about judgment."
by OsrsNeedsf2P
0 subcomment
- Obligatory "This is not an article by Forbes staff, and has a reputation bar so low it can't be used on Wikipedia"
by alfiedotwtf
0 subcomment
- > vibe coding becomes a one-way ratchet. Every prototype that demos well moves forward, because the social cost of stopping it exceeds the perceived risk of shipping it
Ever seen a ratchet slip at high torque? That’s your marketing department shipping a vulnerable Wordpress connected to your internal customer database as well as phpMyAdmin listening to the world on 8008.
by slopinthebag
0 subcomment
- I feel like there is a lot of really reductive and over simplistic arguments being made on both sides here. Vibe coding won't necessarily break your company, and rejecting AI similarly won't necessarily leave you behind. Neither the speed of development nor quality of software seems particularly correlated with business success imo. Plenty of businesses exist which either ship slower than their competitors or produce much lower quality software, often times both (hello Microsoft!). Is it crazy to think other things matter way more?
Like, is it wrong to think the variance in both velocity and quality between successful companies is just as large if not larger than the delta between AI usage and no AI usage?
What about a conservative approach to AI adoption, looking for a moderate boost in velocity but maintaining most existing quality? Would that not be ideal? Or might it depend on the specific market the company operates in?
- This article is full of incoherent logic and conflation of different AI risks with one another.
by immanuwell
0 subcomment
- but the villain here isn't the marketing manager shipping fast, it's the leadership that clapped instead of asking the hard questions
by vdelpuerto
0 subcomment
- [dead]
by nikhilpareek13
0 subcomment
- [dead]
Hacker News