HN Simulatornew | past | comments | lists | submit | ManBeardPc's commentslogin

Steam created a platform that works for developers, gamers and the platform itself. It is managed well. They pushed Linux gaming. They are not perfect and monopolies are dangerous but currently they are beneficial for the gaming community as a whole. They have not won capitalism they just have a consistent product that they didn’t enshitify to squeeze out ever short term earnings they can. I only fear that at some point someone greedy takes over and ruins it. Epic failed to create a proper alternative even with a good example and many many years of time to iterate on it.


>Epic failed to create a proper alternative even with a good example and many many years of time to iterate on it.

not to mention the money (hundreds of millions) spent on securing exclusive launches.


Does for us (data science, specialty chemistry, finding/optimizing formulas). We can get from idea to prototype in a day compared to 1-2 weeks. All that boilerplate to process data took a long time to code by hand, especially for the data science/math guys who are not programmers. Now we can actually try all ideas instead of guessing the most promising and only try that.


And what revenue and/or profit increases can you cite publicly as a result of the use of AI in this work?

I don’t think anyone is disputing that it makes many kinds of work easier and/or faster, just the degree of those improvements and how much of those improvements actually translate to dollars earned or saved.

Seeing hard data on that would help settle the issue.


Unfortunately not everything will cleanly show up in PnL, which is a function of the entire company’s processes.

If developers are shipping more code (and most of the enablement is in software right now) does that show up in top line? Maybe… if sales and marketing are also selling more, and product people are building the right thing, and…

It’s not a straight line from AI -> $$$


btw, shipping more code isn't necessary a good thing. If quality isn't controlled properly, it eventually shows up as negative in the top line.

With AI, keeping good quality gets even harder because it normally only produces tricky defects.


It’s not just code quality, it’s all the other business fundamentals like the product itself having value.

I see this in a very non-AI way working at a company that’s a hodgepodge of acquisitions. Some of our products just don’t make a lot of money, don’t resonate, or are behind the competition in various ways.

The amount of code or general engineering complexity of the application seems completely detached from profitability a lot of times.

Now the bar is going to be higher for software to actually be worth buying when it’s so easy to make your own for yourself, so that also means that our ability to pump out code loses value.


> It’s not just code quality, it’s all xxx

> I see this in a very non-AI way

That's very non-AI of you


I did not use AI to write any of my comment. Please don’t make that accusation.

I don’t use AI to write prose at all in any form, not even drafts.


> The amount of code or general engineering complexity of the application seems completely detached from profitability a lot of times.

Of course, they're almost entirely unrelated. It's just programmers believe solving difficult problems with specifically code is valuable in of itself. The goal is to get as much value as possible from as little code & complexity as possible.


Maybe?

But I also think:

- there are a lot of companies that don’t need to be 5 9s[1]

- I have a feeling it’s possible to ship fast without drastic quality drops

[1] Claude code is 99.85% available and is one of the world’s most important products


> world’s most important products

Really? If we delete CC today, will humanity stop functioning? Nope. It's so far from one of the world's most important products.

About 5 9s, reliability is just one of the axes which suffers from fast generation.

There are a lot more: architecture, accuracy, etc...

> I have a feeling it’s possible to ship fast without drastic quality drops

at what scale and for how long?


This is laughable.

To call Claude Code not a world defining product is so absurd it’s genuinely laughable.

I guess that’s why they’re a $2T company within like 5 years of founding with or without your support.

Now you’re just being obstinate.


> btw, shipping more code isn't necessary a good thing.

This is FUD. It isn't necessarily a good or bad thing.

At the very least, using AI to audit your code is responsible use. The testing is the same as it ever was. If there was a chronic problem with shipped AI assisted code, it would be a popular talking point.

> If quality isn't controlled properly, it eventually shows up as negative in the top line.

This an idealistic pillar of capitalism that has been falsified across time. Depending on what someone means by "controlled properly", I don't think this wasn't been true before AI and I don't think it's demonstrated post-AI. Momentum (notably capture) keeps the software markets resistant to quality defects.


> It’s not a straight line from AI -> $$$

That seems like it might be a bit of a problem for those frontier model CEOs who have been making exactly the opposite claims.


Is it?

Most of the claims I’ve seen are around productivity (bottom line).

And while it’s hard to say “we would’ve had to hire more devs to be this productive without Claude” it kind of feels like the case, doesn’t it?


I don't think 2 trillion USD was invested into AI for "more productivity", without any financial gains.

Or maybe it was! And investors were actually great humanitarians!


That is such a malicious mischaracterization of my statement.

Come on, you know better.


It should be especially when new features are used to hook new customers (or renew contracts) and lower the amount of time wasted on bugs…


It can also be the case that it has zero impact on PnL, but is now necessary to operate a competitive business and keep up with competition.


Usually, things that aren’t clearly correlated with profit tend to get ignored and canned by businesses.

Think security, optimization work, refactoring, etc. Today everybody is drunk with AI, but what happens when the hype is over and you can’t justify to the finance dept. why the company is spending X on tokens?


An agent found a SQL optimization that at least a month of eng effort hadn't found.

Agents accelerated rollout of a data model change by at least 2 months of eng effort.

Those unblocked a $100k/month infra downsizing. That 2 months pays for my team's AI spend for the year.


This post is rage bait. Your experience is the modal outcome


This comment is rage bait. You have absolutely no way of knowing this


I know a very specific use case in management consulting where hours spent by a consultant for a repetitive task (mainly report writing and source data gathering) went from on average of 40 hours to 12 hours per project. It costs the firm roughly ~$150 in token spend to save those 28 hours. They used to be roughly $200/hr (so $5k~$6k).

That's about as hard of data as you can get.


You haven’t shared enough data to tell whether there was a financial payoff for the firm or not. The consultant is a fixed cost to the firm, so saving consultant time doesn’t necessarily translate directly to higher margins nor revenue per worker.

Are the consultants delivering more billable hours per person now?

All sorts of reasons why the answer to that may be: no.


The firm charges a fixed fee to the client. The client doesn't see anything different from what they got before, the firm increased their gross margin overnight.


Yes, assuming the consultants are salaried like most, you can increase gross margin while operating margin stays flat. The question still stands — did revenue per consultant increase for this firm?


The consultants are contractors. Even if they were FTEs, it would mean the consultants could do ~3x the work.

You seem hellbent on disproving me. Why?


> You seem hellbent on disproving me. Why?

Uhm, no. The OP makes specific claims wrt to AI and financial payoff; you offered up a case study, with incomplete data, as possible evidence that AI is generating these financial payoffs. I'm asking questions to uncover the data necessary to reconcile your case study against the actual claims from OP.

> Even if they were FTEs, it would mean the consultants could do ~3x the work.

Could. But again, are they? That's the whole point of Apollo's claims: people keep saying AI can or could increase capital efficiency, but it's not showing up in any actual financial results.

You're extrapolating a 3x increase in throughput from the optimization of a single process that exists in a whole business system. Given your background, I don't think I have to explain to you why that doesn't make sense.

Also, do we think the S&P 493 is so incompetent that they'd miss these optimizations? Or is it more likely that this firm you're referencing is a small inefficient player, and the S&P 493 already realized these efficiencies decades prior without AI?


> you offered up a case study, with incomplete data, as possible evidence that AI is generating these financial payoffs.

You're confusing the original article and the parent comment I replied to. I think the Apollo article is way off, BUT I have very intimate knowledge with very concrete numbers of a use case where AI has a very clear and definable ROI.

> Could. But again, are they?

YES. That's what I'm telling you. They just implemented the system. The contractors spend less time on each project which means they have more time to do another project. How is that so hard to understand?

> You're extrapolating a 3x increase in throughput from the optimization of a single process that exists in a whole business system.

Are you deliberately being obtuse? The company very clearly drives ~$5k additional profit per project. They do hundreds of similar projects.

> Also, do we think the S&P 493 is so incompetent that they'd miss these optimizations? Or is it more likely that this firm you're referencing is a small inefficient player, and the S&P 493 already realized these efficiencies decades prior without AI?

I never made any of these claims, why are you saying I did?


> it's not showing up in any actual financial results.

Really? Not any results?


This assumes the client is oblivious to the fact that they are paying the same for 12 hours of work as they used to pay for 40 hours of work.

For non-technical clients that may well be the case for a while, but I suspect even the most non-technical clients will eventually realize they can claw back a good portion of the efficiency as discounts.

I'm negotiating some contracts where I could do the work in-house for about 1/20th of the previously-reasonable vendor cost. I'd rather not do it, so I'm happy to pay 1/20th plus a reasonable percentage above that, but that's the limit. The vendor can accept that, or goodbye.

Interesting times on vendor contract negotiations these days.


> I suspect even the most non-technical clients will eventually realize they can claw back a good portion of the efficiency as discounts.

If the outcome is the same then the fees shouldn't matter to the client in the long run. Said differently, if the client who pays the management consulting fee gets the same return out of the service, why do they care?

Now, what may end up happening is that some other management consultant vendor in the market comes in an says "ya know what we're willing to do the same work for less" (which means their margin goes down). This could indeed drag their pricing down.

> Interesting times on vendor contract negotiations these days.

For sure.


> Said differently, if the client who pays the management consulting fee gets the same return out of the service, why do they care?

At least at every company where I've been in charge of my vendor contracts, I am always grilled by management on how we can lower the cost of the contract and whether we are getting maximum efficiency from each vendor. There is huge pressure every year to find ways to lower the cost.


I actually feel like it’s really premature for a relatively new technology to be showing profit improvements. We are talking on the order of a few years of investment and “figuring out” how to use it productively in business. Most new technologies take a decade or longer to really yield tangible value.

This is the first cycle in my (relatively) long career where the demand for return felt instant. The tools and techniques are almost comically immature and the average person interfacing with the tools is largely bewildered.

For word processing for instance people spent years upon years coming up to speed on wordstar, word perfect, word. Decades later they’re a common part of life and the tangible benefit over secretarial pools is obvious - there is no such thing as a secretarial pool.

AI it feels like almost a blink of an eye and the demand is “well, it’s been a few years, where’a the post scarcity society I was promised?”


The difference is that other new technologies didn't have a literal trillion dollars invested into them within the first few years, nor were the industry leaders warning that the tech could destroy humanity. Given those conditions I think "Has it made any money?" is a reasonable question to ask.


I think part of the issue is-if AI makes you twice as productive at X, that doesn’t necessarily result in any increased revenue, because now your customer expects twice as much for the same price, and if you don’t deliver that one of your competitors will.

A new technology can deliver significant increases in real economic value in terms of utility per $ expended without significantly increasing revenue for the average firm.


I agree. Being twice as fast as X might not help depending on how X impacts Y and Z.

As an example, my X is that boilerplate and general speed/effort of modifying my code is lower, but I’m noticing that this doesn’t necessarily make my team any more effective overall.

It seems like it’s been a code review burden and it’s led to some team members being too ambitious with picking up more projects that don’t make sense.

I have seen some managers in particular toss prototype work that they shouldn’t be doing at underlings, and one of those projects in particular really ended up taking me longer than if I had done it from scratch without AI. The fastest result would probably been if I did it from scratch with AI, but because I took it over from someone who didn’t understand the fundamentals and farmed out decisions to AI I had to spend a lot of time correcting mistakes.

Obviously, good management beats bad management all day long, but I bet you most companies don’t have stellar management.


Can’t share more than that publicly. Just that the time saved on this one thing alone is saving us way more money than the subscription per employee that is needed (~100$). I don’t doubt there are companies where this is not the case. Would like to share more details, but the rough math of doing something in a day vs several days + engineering salary have to do here.


> subscription

Well yes when your tokens are nearly free, then getting literally any business value is a good outcome.


Speaking annecdotally because im an engineer, not in sales:

Our company has secured projects and executed them to a standard which we would not have otherwise were it not for AI or hiring more people. Now, these are at least 3 year projects, so we are only seeing ~3 being AI accelerated.

For us, yes, it's a multiplier, directly translated to more $$.


With the advent of the internet and email, many people surely made similar observations. I wonder what the fate is of the companies who refused to accept these productivity enhancements.


The fate of companies who rushed into it before those technologies were ready was "a lot of wasted money".


Unfortunately we're at the mercy of Goodhart's law and in an interesting twist, AI is really good with things that have an immediate feedback mechanism, eg writing code that doesn't compile or pass tests, but you're trying to grade AI o something that doesn't have an immediate feedback mechanism. AI can slop out a PowerPoint deck in a fraction of the time it used to take a human by hand. The competent human then goes in and unslopifies it, but overall, still time is saved. Unfortunately, that employee is salaried and not hourly, so they can't click out early and even if they were, what's their incentive to clock out early if it means less money in their pocket? Or they can use the hours now free on something else. My gut, as an Internet random who's used AI is that it helps. I don't know how to measure it, just like how do you measure how much better it is to live in a clean house vs a cluttered one? How would you put that in a metric? If you can't put that into a metric, why bother cleaning your house? We clean it anyway, because of a certain je ne sais quoi.


> If you can't put that into a metric, why bother cleaning your house? We clean it anyway, because of a certain je ne sais quoi.

That "je ne sais quoi" is called hygiene and it's hard to measure but when you stop cleaning, generally bad things happen.


> And what revenue and/or profit increases can you cite publicly as a result of the use of AI in this work?

Nobody even tries to measure this. Their CEOs and board members have AI shares, and potential investors need to see your AI story to justify your valuation. It's a prison of lies.


It's probably just another Red Queen's Race. The benefits of LLMs won't show up in higher profits for most companies because their competitors are also using the same tools to move faster. You can't opt out of the race or else you'll be left behind.


Sounds like involution

Next step is 9to9/7days for the American worker to compete, or else you'll be left behind


Internally the hard data is there. On a budget of $2000 of API-priced tokens (Claude models + GPT models) we were able to migrate ~6 teams of infrastructure in 1 month, done by 1-2 people. Without AI it would've taken 10x longer wall clock time to do, and involved far more folks, and probably would have been much bumpier of a rollout. The big lift was mostly using AI for massive information gathering, digging through huge volumes of discussions, documents, commits, PRs, alerts, dashboards, etc pretty exhaustively for the past 5 years of history, to discover all the "chestertons fences" far more thoroughly than even the folks on the team who built it were able to. Then the 1-2 folks could go to each team with a super comprehensive "here is every need, every interaction, every discussion, everything you've ever done w/r/t this infeastructure, and here's how we're going to handle each of those with the migration we're going to do. We will do all the work for you, is that acceptable, yes or no?"

The teams throughly reviewed and brought up 2 overlooked cases, but mostly we all reminisced about things forgotten that AI discovery had turned up which would have been totally overlooked otherwise. Forgotten discussions, designs, outages, odd decisions, weird edge cases prepared for but never encountered, etc. Then they were migrated, it went smoothly, all to save a low seven-figures per year dollar amount.

The fundamental approach of exhaustively researching to that degree would never have been possible without AI. It's just not feasible to analyze 5 years of even one of those discussions sources (e.g. slack) to figure that out, let alone ALL of them. Now a team of ~1.5 engineers has tackled all that by leveraging AI.

The hard data is piling up in companies, but it'll take a while to get out there.

(Numbers and details lightly greeked in the above account)


It can take a long time for the economic gain of new technology to be visible in GDP because people have to learn how to use it effectively and processes have to change to integrate it. It took about 40 years for factory floors to be fully reconfigured around distributed electric motors rather than central steam shafts.


I always wonder why systems are designed so poorly that it takes weeks of boilerplate to use them for their intended purpose.

At what stage did the engineering fail?


Tons of unstructured data that needs to be cleaned up in so many different ways that are hard to predict. Knowledge distributed in the heads of greybeards, handwritten papers und excel, sharepoint and dozens other locations like ancient proprietary software. Which you have to repeatedly ask for and discover more piece by piece. Then clean up, discover issues, make the customer gather more data/correct it, etc.


This knowledge locked in people's heads isn't going to magically show up when you throw AI at it, though.


No, but if we go from data to experiment faster we see earlier if something is wrong. Once we get data we quickly can fix the data pipeline and get results. If there are issues we can quickly show what/why and discuss it with them in detail and make changes based on their response faster.


??

But the problem identified that is talking to people and having them record data.


Yes, but they tell things and maybe forget to mention certain things or contradict other data they have given you. Now we may not notice it initially until we make an experiment and get the results. Something is wrong and we have to find out what. Talk to the customer again. Fix experiment. Repeat. Faster experiments means the latency from new data to results is less and we finish the project faster. Errors become less expensive and cause less delays. People make errors and data quality is often horrible so the shorter iterations are nice.


But the experiments aren't two weeks of boilerplate. Or if they are, something else is really fucked up in the stack.


It's not all boilerplate of course. But iteration cycle is shorter and the latency matters. We are trying find a formulation, so a lot of experimenting, fine-tuning, checking errors (first via simulations, then real-world with measurements). Then we see what needs to be changed, repeat until error is in desired bounds. But the real-world is messy so we see a problem (lets say adding some certain color does not change the final properties of paint the way predicted) and we go back to the customer, some expert remembers temperature/moisture of the air was different on this day and that affects printing results. Now we need to measure this too and add it to the simulation and add it to the data pipeline. But we may have to wait until the real world has implemented that too (create a process, buy hardware, whatever) and then a while later we finally get real data and can start doing our part. Reducing our latency makes things faster, as you may do something else in between and need to load everything in you head again. The LLM gives results in sometimes minutes: frontend, backend and database. We now have the feature branch where you can upload the data like the customer would do, start the calculation, see the predicted formula. From idea to working prototype. We can focus on making assumptions and checking them quickly. Previously they can make the changes in their Python scripts but getting it in a presentable form took much more work. Now we can go to the customer and present a pretty custom made UI like an end-user would see same day they give us new data or report issues.

The stack certainly could need improvement, but much of the overhead comes from the process being pretty serial because each step depends on the previous. If someone we needs to talk to goes on vacation, sick or has a full calendar this delays it much further. Iteration speed is not linear in such cases. We do a lot of custom solutions and have to implement custom parsers or interface with undocumented ancient software or simply no existing software. Everything is custom, because previously they have no processes, no IT infrastructure or simply only data intended for humans (roughly structured, informally written, ever changing naming schema, typos).


And relying on AI to clean up unstructured data makes me nervous. Good luck spotting the hallucinations.


Oh yes. Verification needs to be done. Some statistics and validation is absolutely required. Also most customers don’t want their private data uploaded anywhere, so ai gets only test data and writes the script to transform it. As long as it is just XML, CSV or similar it’s pretty reliable. Handwritten notes and bad scans however…


A friend of mine runs a business similar to this for systems migration, which is a fairly tough and tedious "short-put" job (you have to know both old and new system fairly well, and if all goes well, you get the same job done on the new system, while if something goes wrong, you're in a world of pain...):

The AI analyses sample data from old and new system, and then builds a prototype deterministic mapping pipeline. The experts can then inspect said pipeline and with their domain expertise catch edge cases/exceptions/uncovered cases, fix them and improve things, and then you use the vetted deterministic pipeline for migration. Yet, the initial AI draft saves enormous time.


That's definitely how I use AI in general: build the tools instead of process the data. I rather like deterministic behavior.


> handwritten papers und excel, sharepoint and dozens other locations like ancient proprietary software

This area is one which AI has shown to be pretty good (as long as some error rate is acceptable). Character recognition, voice transcribing, converting documents from one standard to an other. I can see an argument that if people spent most time doing those things, AI will speed it up (with a bit of added errors).

I am reminded however that in translations and AI generated subtitles, there is still a lot to be desired compared to the human touch. Handwritten papers in a different language, using local short hand and assumptions, may result in some odd and error prone AI transcription.


I think a lot of “boilerplate” is just to align with a company’s way of doing things/ecosystem.

In a webpage the UI design, authentication, etc. are all “boilerplate” if one just wants to do “X” instead of worry about infrastructure.


Boilerplate becomes burdensome as complexity increases. Perhaps sometimes we don’t give ourselves enough credit for how much applications and their infrastructure are actually taking care of as part of boilerplate.

I look at stuff like terraform code or AWS infrastructure and it’s annoying and repetitive as hell sometimes but at the same time it’s incredibly impressive that you can just describe something as complex as your own private company’s network existing on global data centers and on a relative level you can just bake in pretty complex stuff like a spiderweb of IAM rules, disaster recovery/backup/databases you barely have to think about, horizontal scaling, security policy and all kinds of other stuff I’m forgetting off the top of my head.

It’s heavy boilerplate because like you said you can basically design an infinitely complex corporation as code and once you’re done with that deploy it instantly which used to be pretty much unheard of.


And yet, many companies today are spinning up full stack teams, asking them to be experts from user interviewing to database design, architecture, hosting, devops, API management, data product, and also keep an eye on GDPR compliance.

I see dozens of teams that are doing cloud to the wazoo when really they need to just be told “we’ll load your routes from main.py, build your assets in /static, you need a DB click the button to provision it”.

It boggles the mind that so many teams are reinventing the wheel a million times over to publish their APIs, register AWS accounts, setup CI, decide on ECS vs Lamda, etc.


This sort of activity has been the source of income for a very large number of people. You can't really fault them for trying to extend that gravy train's run.


Your middle paragraph sounds amazing but it works great until it doesn’t.

That’s pretty much the answer. The simple stuff has already been tried and there’s already some reason why we can’t just make XYZ simpler.


Who is productizing this type of boilerplate?


Probably a controversial take - but in the pursuit of elegance. 'Uhh, so I need to hook this connector up to that receiver using this adapter and then uh, I pass it to the connector manager which sends it to the scheduler that... @#%! FML.' And then it's all so polymorphicized that going through the debugger you spend an eternity just trying to figure out what the types even mean and why/where they came from.

When you look at old-school code that just hacked things together, it was ugly, but also very easy to in turn further hack. There was no elegance or grand base types with 80 levels of inheritance to enable clean extension at every possible juncture of types. And no spending forever to find out the exact function you want to be able to override, only to discover that it's outside your modifiable codebase and wasn't marked virtual. Everything just worked.


Yeah, so nobody did engineering.


This reminds me of a nice quote about engineering: 'Any idiot can build a bridge that stands, but it takes an engineer to build a bridge that barely stands.' Another is that 'If people knew how many assumptions went into designing a bridge, they’d never dare cross one.'

Engineering isn't about creating some perfect thing that is prepared for any conceivable scenario, but about solving a problem as efficiently as possible.


Well, that's a funny thing. The "well engineered" code can actually be harder to work on. And maintainability is one aspect of "well engineered".

What I've seen (at least at one place I worked) is that the code may be very well engineered for further modification - but only by people who have worked quite a bit on that code. For someone coming from outside, it's almost impossible. It takes forever to find your way around, and figure out where the magic place is that you need to modify in order to work within the existing design.

Well, you say, that's what the design documents are for! But they didn't have enough detail. They described the major objects, but not all the ancillary helper objects. They didn't describe the flow of data through the system in enough detail to know what to modify. The knowledge was there, in peoples' heads, but it was hard to get those peoples' time.

So, yeah. "Well engineered", but not engineered for maintenance by people who are not those already in the group.


You're describing something not fit for purpose. It's not well engineered.

That's like saying "that's the irony of it, a well engineered bridge sometimes drops chunks of concrete onto cars that pass underneath".


You’re not meant to ask that question.


The question is: how does any of that translate into more revenue? If you try more ideas and they mostly go nowhere that's not necessarily helpful to the bottom line.


https://en.wikipedia.org/wiki/OODA_loop

speed of iteration is more important than quality of iteration; high iteration speed lowers the cost of failure and compounds improvements


If that were universally true in all domains then all the best and most reliable software in the world would be written in interpreted languages, because they have the fastest iteration speed. Sometimes rapid low-quality iteration is just spinning your wheels.


I'm not sure that is strictly true. Speed of iteration is increased by interpreted languages in the small, but when working on larger systems or on teams where collaboration is required they can have the opposite effect.

I also find that thinking through a design first helps me achieve a result faster. So I prefer languages that encourage you to think first, type later. Interpreted languages encourage you to type first, think later.


> If that were universally true in all domains

Moving the goalpost is not compelling.


No goalpost is being moved here. Don't assume that an aphorism coined in one domain generalizes to other domains, especially when we have evidence to the contrary.


Not all experiments work out. If we find the right approach faster we can finish the project faster. Some projects are mostly fixed price or offer bonuses for reaching milestones in a certain time. Meaning we more often get a bonus and can take more projects. Also we can take projects with tighter deadlines that we would need to decline otherwise.


But if everyone's taking on more projects... where do all the new projects come from? And wouldn't it just lower the value of each project?


A lot in this world is not optimized by software yet. For our customers they have employees with decades of experience guessing things, maybe some software that kind of helps but still not good enough (slow, not finding really good formulas). They often have difficult problems and many failed projects. We try to find such customers and offer our service. If we are cheaper (+ show portfolio of successful projects) more are willing to give it another try with us.


Right, and while that might be working out for you right now, there is a finite budget that companies have for projects like that. The "zero financial payoff" framing sounds about right to me.


Yep. Hard to see why this increases revenue or profitability


You can have a better solution, but customers don't normally pay for that and CEOs don't care or understand. AI improves what businesses don't care about.

AI is going to effectively let random people compete and displace big tech companies with free software they simply release. This is why google wants to lock android down, they see it coming. CEO led companies with layers of management and lots of investors are obsolete. We are going to go back to teams of 1-6 people doing all the work on their own like in the 90s.


It makes things viable that previously would just sit in a backlog for months or years because something else is always more important. On the other hand it can create messes that cause a growing backlogs. Can confirm that smaller teams are much more viable now. We are 5 people only.


You don’t get it, what’s the actual profit gained to the company from that?

That’s the whole distinction


Now we can throw things at the wall, faster.

I understand there's some benefit of this. But is it worth putting the global economy into a death spiral? So ManBeardPc can save 4-9 business days to go and say "yeah, that doesn't work".


The two needn't go hand in hand. But here we are.


This gets downvoted? Why?


There's a difference between the cost of coding and the cost of delivering and maintaining software? AI has demonstrated that these two things are almost entirely unrelated.


Almost everywhere I've worked, the "designing and writing code" part was about 5% to at most 10% of the calendar time that it takes to make and release a software product. The remaining 90-95% of the time is: aligning stakeholders, meeting with all contributing teams to prioritize, gaining approval from various executives to commence the project, obtaining security reviews, privacy reviews, legal reviews, and so on, soaking in dev, staging, and beta environments to find bugs, manual QA testing, aligning with marketing--potentially waiting on key external marketing events, waiting for various people to come back from vacation, waiting for Mike to answer his E-mail... These things take the vast majority of a software project's time and can't be automated by AI.

So, AI is making 5-10% of your project much faster. Whoopdie doo.


It’s interesting to me that you don’t understand how 90% of the things you listed can either benefit from automation or be made irrelevant because of automation.

The firms of 2031 won’t be doing business like the firms of 2021 but just using AI for coding or in a few places to accelerate the same workflows.


Has AI demonstrated that or have people using AI demonstrated their lack of ability to properly use it, as they are fumbling in the infancy of an new age?


I'd argue that it's shown something slightly different, it's related but maybe not in the way some people hoped.

I think it sums up to something along the lines of "you get what you pay for".


The Record struct contains rtype and data where RecordData is a tagged union. Aren’t those two always in sync? Not a DNS expert, just wondering if this is redundant or there is a reason both are there. Doesn’t matter anymore if they store it already serialized but I would be interested why it was this way.


Guidelines | FAQ | Lists | API | Security | DMCA | Apply to YC | Contact

Search: