[meetingthrower]

Vibecoder here. I don't think so. I am a PE investor, and we are using it in our small portfolio companies to great effect. We can make small little mini-apps that do one thing right and help automate away extra work.

It's a miracle. Simply wouldn't have been done before. I think we'll see an explosion of software in small and midsize companies.

I admit it may be crappy software, but as long as the scope is small - who cares? It certainly is better than the janky manual paper processes, excel sheets, or just stuff in someone's head!

[svieira]

> excel sheets

Funnily enough, Excel is the quintessential example of a fourth generation language, IDE, and database and it's the only one aside from SQL which actually succeeded from its time period. It's software, just like what you're building now, and just like what you're building now there are good points and bad points about it. The tradeoffs are different between the JS / Python code you're likely spinning up now vs. the Excel code that was being spun up before, but they rhyme.

[meetingthrower]

100% correct. Wonderful and we will still use it for most use cases. But for stuff where it is just not needed or should be automated, we can now make some amazing tools. (Just like the VBA coders of old.)

[puilp0502]

I think the parent is talking about the people who post to LinkedIn that "SWE as a profession is dead" non-stop. I fully agree with you that it massively lowered the cost to create, but I'd argue that the people who's saying that SWE is dead wouldn't be able to go past the complexity barrier that most of us are accustomed to handling. I think the real winners would be the ones with domain expertise but didn't have the capacity to code (just like OP and you).

[meetingthrower]

Correct. I think "real" software requires real development and architecture.

And to be honest, even the tiny apps I'm doing I wouldn't have been able to do without some background in how frontend / backend should work, what a relational database is, etc. (I was an unskilled technical PM in the dotcom boom in the 2000s so at least know my way around a database a little. I know what these parts of tech CAN do, but I didn't have the skills to make them do it myself.)

[elzbardico]

Don't care about the critics. What you're doing is what people were doing in the 80s with their new PCs and tools that democratized this kind of development, like Basic and DBase.

Most developers are too full of themselves, in fact, most of us are a bunch of pretentious pricks. It is no wonder people are happy to be able to get what they want without our smugness and pretentiousness. Too bad some us are not like that and will end up getting unemployed anyway in the next few years.

[bookofjoe]

See also: the fate of Stack Overflow. R.I.P.

[hexbin010]

A miracle! Tell us more! What kind of apps? How has it helped revenue?

[meetingthrower]

Two examples:

1. Invoice billing review. Automated 80% of what was a manual process by providing AI suggestions in an automated way. Saved 3 hours per day of managers time. Increased topline by 10%. Dev time: 1 day

2. Data dashboards. We use janky saas that does not have APIs. Automated a scraper to login, download the reports daily, parse and upload to a database, and build a dashboard. Used to take my associate 3 hours per week to do this in a crappy spreadsheet. Now I have it in a perfect database much more frequently. Dev time: 4 hours.

We are attacking little problems all across the business now.

A MIRACLE!!!!

[SPICLK2]

>an explosion of software in small and midsize companies

For me, that is nightmare fuel. We already have too much software! And it's all one framework or host app version update away from failure.

[meetingthrower]

But this nightmare is ALREADY true, except that software is a spreadsheet. Or a piece of paper on someone's desk. Or an email that someone is supposed to send every day.... Yes it's an absolute nightmare to maintain if you built a fortune 500 off of it. But for a 100 person company that is 95% blue collar workers, this is fine. And better.

[HPsquared]

It's a nice demonstration of the Jevons Paradox in action.

[sdf4j]

Curious about why the janky manual paper processes, excel sheets, or stuff not documented, was fixed only when vibe code was available. Was it just cost?

[matwood]

Time and thus cost. Early in my career I would look across a fairly large company at processes being ran on spreadsheets and see if it would be worth the time to create software to address and if those processes should be standardized. We barely scratched the surface with all the possible custom software opportunities for this company.

[meetingthrower]

Cost and managerial overhead. We don't have a dev on staff. Even if we did, there is lots of managerial overhead to explain "the problem" and then iterate to a solution with a dev. Now you can just build the damn solution yourself!