> probably have to read 200+ LLM generated messages a day and reply back in great detail about 5 times a day (think of an email instead of chat message).
I can think of nothing more tiresome than having to read 200 emails a day, or LLM chat messages. And then respond in detail 5 of those times. It wouldn't lead to "3x to 4x" performance gain after tallying up all the time reading messages and replying. I'm not sure people that use LLMs this way are really tracking their time enough to say with any confidence that "3x to 4x" is anywhere close to reality.
A lot of the messages are revisions so it is not as tedious as it may seem. As for the "3x to 4x", this is my own experience. It is possible that I am an outlier, but 80% of the generated AI code that I have are one-shot. I spend an hour or two (usually spread over days thinking about the problem) to accomplish something that would have taken a week or more for me to do.
I'm going to start producing metrics regarding how much code is AI generated along with some complexity metrics.
I am obviously bias, but this definitely feels like a paradigm shift and if people do not fully learn to adapt to it, it might be too late. I am not sure if you have ever watched Gattaca, but this sort of feels like it...the astronaut part, that is.
The profession that I have known for decades is starting to feel very different, in the same way that while watching Gattaca, my perception of astronauts changed. It was strange, but plausible and that is what I see for the software industry. Those that can articulate the problem I believe will become more valuable than the silent genius.
The same noise was made about pair programming and it hasn't really caught on. Using LLMs to write code is one way of getting code written, but it isn't necessarily the best, and it seems kind of fad-ish honestly. Yes, I use "AI" in my coding workflow, but it's overall more annoying than it is helpful. If you're naturally 3x-4x times slower than I am, then congratulations, you're now getting up to speed. It's all pretty subjective I think.
This is very measurable, as you are not measuring against others, but yourself. The baseline is you, so it is very easy to determine if you become more productive or not. What you are saying is, you do not believe "you" can leverage AI to be more efficient than you currently are, which may well be true due to your domain and expertise.
No matter what "AI" can or can't do for me, it's being forced on us all anyway, which kind of sucks. Every time I select something the AI wrote it's collecting a statistic and I'm sure someone is probably monitoring how much we use the "AI" and that could become a metric for job performance, even if it doesn't really raise quality or amplify my output very much.
> being forced on us all anyway, which kind of sucks
Business is business, and if you can demonstrate that you are needed they will keep you, for the most part, but business also has politics.
> probably monitoring how much we use the "AI" and that could become a metric for job performance
I will bet on this and take it one step further. They (employer) are going to want to start tracking LLM conversations. If everybody is using AI, they (employer) will need differentiators to justify pay raises, promotions and so forth.
>Do you produce good results every time, first try?
Almost always, yes, because I know what I'm doing and I have a brain that can think. I actually think before I do anything, which leads to good results. Don't assume everyone is a junior.
>The complete package includes things like highly curated training data, specialized tokenizers, pre and post training regimens, guardrails, optimized system prompts etc, all tuned to coding.
And even with all that, they still produce garbage way too often. If we continue the "car" analogy, the car would crash randomly sometimes when you leave the driveway, and sometimes it would just drive into the house. So you add all kinds of fancy bumpers to the car and guard rails to the roads, and the car still runs off the road way too often.
>"challenge me when I'm wrong, and tell me I'm right if I am"
As if an LLM could ever know right from wrong about anything.
>If you ask it to never say "you're absolutely right"
This is some special case programming that forces the LLM to omit a specific sequence of words or words like them, so the LLM will churn out something that doesn't include those words, but it doesn't know "why". It doesn't really know anything.
If you need alcohol to get laid or make friends then I feel very sorry for you. Most people I know got laid in high school (sometimes actually inside the school), without any alcohol involved at all. We also made plenty of friends. YMMV, I guess. I suppose some people are only likable if other people are drunk? I generally avoid those kinds of people no matter how inebriated I am.
I'm happy that people you know got laid in high school but loneliness has become society destroying epidemic and your friends that are getting laid are not doing enough to save the fertility rates.
The strange tone in your writing reminds me of Dinesh from the Silicon Valley series :) I'm sure you are one of the cool ones with the good hairstyle who doesn't need alcohol unlike the lesser people haha.
Alcohol is not about being so drunk that you do degenerate stuff and fuck people you don't like. It's about easing the social anxieties and improving the mood together with a good company and some music.
Since you are assuming things about me, I'll assume that your social skills suck if you need to be intoxicated to be social or get laid. It seems like your parents failed you.
But you don't know me and no, I don't have "a good hairstyle", and no, I'm not "one of the cool ones". I'm just as average as anyone.
"fertility rates" and people getting laid are two very different things. People don't have sex only to produce offspring.
And the world could use a lot less people anyway, so I don't see it as a bad thing if fertility rates drop, no matter the cause, even if the drop is significant. The world will be fine with a billion or two less people, in fact it may just improve some situations.
I, like many developers was handed a Macbook Pro upon starting my first day at the company. I gave MacOS a shot (again, I used to be a mac sysadmin at a design company), but was happier when I could install Windows on it. Finder is a joke, and so many other things about MacOS are just stupid. Sure, Windows has some crap too, but it lacks the pretentiousness and ridiculous things I dislike about Apple products. I also covered the white lit-up Apple logo on the laptop screen with red-circle-strikeout sticker, because I really disliked Apple after being a sysadmin getting all too familiar with their products and OS.
Now I am what you would consider a "Full Stallman" free software guy, but you can imagine my mixed feelings when I ended up being interviewed by Business Insider on why Microsoft shouldn't be giving up with web engine for a Chromium based browser. Yes, things like Safari are proprietary junk but they still keep things like Chrome dominance at bay. Alas I feel we are better having a few proprietary systems than a singular monolithic one. Once Apple lets that one go, it is only a matter of time until Google almost single handled controls the framework of the internet.
"Chrome dominance" isn't my concern, and it isn't the problem with Apple.
The problem is Apple is intentionally hobbling their web browser and forcing every other browser maker to use it, which prevents web applications that use any kind of hardware API from functioning on iOS - the only alternative being making a native app for iOS where Apple can charge a significant amount for any purchases made through the native app. Web applications threaten Apple's greed, so they forbid any other browser maker from using anything but Safari on their platform.
Microsoft got sued in an antitrust and lost just because they bundled IE with Windows - not for forbidding any other browser on the platform like Apple has been doing, which is way worse IMHO. And that's one of many reasons the DOJ is suing Apple for abusive business practices.
Eh, this is annoying because I agree with you in principle except there's a handful of things you're simply wrong about.
I'll start with the most eggregious one to save time so you can just click away but: Microsoft wasn't sued for bundling a browser, it was sued because it used one monopoly position to aid another. Apple mobile devices are 57% of the market in the US (which is the highest percentage globally from what I can tell at a glance) and a far cry from 1997 Windows which was a staggering 96%+ of all desktop operating systems in the US. That is a monopoly which is not explicitly forbidden in the US unless you use it to further domination in some other field: Web browsers were considered another field.
That said, while I agree with you in principle, in practice I really don't like the idea of a browser monoculture. We already see the effects of it with WebUSB (for real) and Manifestv3 which nobody really wants but is essentially foisted on us.
There are two types of people: those who think the web is an application delivery platform, and those who think it's a window into information.
The more leaky the sandbox the worse security will get over time (even if we put a lot of eggs into the basket) and the more bloated things will get. But the people in the first camp cannot see passed their next meal for want of a "better" application delivery system. Anything that keeps them at bay is welcome to me, even if it's something I also don't agree with.
"The central issue was whether Microsoft was allowed to bundle its IE web browser software with its Windows operating system. Bundling the two products was allegedly a key factor in Microsoft's victory in the browser wars of the late 1990s, as every Windows user had a copy of IE. It was further alleged that this restricted the market for competing web browsers (such as Netscape Navigator or Opera), since it typically took extra time to buy and install the competing browsers."
Yeah, Windows has a larger market share than Apple ever will, but that doesn't change the abusive business tactics Apple is using to satiate their greed.
When someone installs Chrome on iOS, they aren't getting Chrome, they are getting Safari with a wrapper. It's way worse than what Microsoft did with IE by simply bundling a browser with Windows - was it really so inconvenient to download and install a different browser when downloading and installing software is the de facto means of obtaining and running any software? I think the case against Microsoft was a bit absurd, honestly. And I don't care if Apple's market share is smaller, that isn't the point. They are preventing competition so that they can pocket even more money from developers.
>There are two types of people: those who think the web is an application delivery platform, and those who think it's a window into information.
And yet the web is both of those things. I think it's both, so am I a third type of person? What else are you getting wrong about this?
I’m don’t seem to be getting anything wrong as you haven’t disproved anything I said; in fact it reinforces it.
you don’t mention what a third type of person would look like, i only can see that you’re the first type from your comments. They’re fundamentally incompatible with each other (or, will cause major issues for each other) so being a blend of both is to be a walking contradiction.
That’s more complicated because the alleged harms are quite limited (it’s not like Android or desktop users are using PWAs much) and the biggest direct impact is the unalloyed good of “the web” not being synonymous with the Google Chrome roadmap. Everyone has benefited from proposed specs with significant negative privacy and security impacts not being adopted, so we have to ask how much the negatives outweigh the positives here.
Remember when Microsoft got sued in a class action because they simply bundled IE with Windows? Well Apple is doing far worse than that. The DOJ finally noticed and was suing Apple for it as well now, and rightfully so.
No, they are making it impossible to implement some kinds of web applications on the entire iOS platform so they can push developers to make a native app, where they can collect a significant percentage of any money made through the app.
The DOJ noticed and is suing Apple for doing this.
That comparison is somewhat more complicated because it was much more broadly tied into Microsoft's control of the by-far dominant PC operating system and was in the era where browsers were commercial products which cost money and significantly predated the rise of open source software.
That's likely why the DOJ is _not_ “suing Apple for doing this”. Browsers are conspicuously not on the list of charges and I think it's because in the subsequent 3 decades, we've had some key changes: all of the major browser engines are open source, very few people question the demand for standard libraries for rendering web content even in desktop apps, statistically nobody pays for web browsers. A large part of the Microsoft trial was discussing how they colluded to prevent PC vendors from bundling other companies' software but in this case Apple isn't trying to restrict another vendor's decision about what software they ship on their hardware and users don't show much sign of being bothered by the lack of PWAs, which have negligible usage on any platform. If someone was making a lot of money with a PWA on Android but having to pay Apple's in-app fees on iOS, that'd be a much stronger argument for market distortion.
The actual lawsuits are focused where Apple's behavior is more clearly like 90s Microsofts: restricting access to the NFC APIs, restricting game streaming platforms, and restricting the ability of WearOS watches to work with iOS phones or Apple Watches working with Android phones. Unlike PWAs, there are other mobile payment companies who'd love to ship tighter integration, customers who want more gaming options, or who want to have something like a Garmin device as tightly integrated as an Apple Watch. I don't know how likely the DOJ's case is to succeed but at least in those cases it's easy to show that there's a real market being affected whereas it's much harder to argue that a PWA market would suddenly spring into being or that Google is somehow being deprived of Chrome revenue by having to use WebKit on iOS. I'm aware of the technical arguments but it seems fairly challenging as a legal argument to make the case that the DOJ should respond to Apple abusing a monopoly position with a fifth of the market by allowing Google to push their share over 90%. The only way the web is better off out of this is if there's some coordinated simultaneous action.
>Browsers are conspicuously not on the list of charges
Wrong.
"60. For years, Apple denied its users access to super apps because it viewed them as
“fundamentally disruptive” to “existing app distribution and development paradigms” and
ultimately Apple’s monopoly power. Apple feared super apps because it recognized that as they
become popular, “demand for iPhone is reduced.” So, Apple used its control over app
distribution and app creation to effectively prohibit developers from offering super apps instead of competing on the merits.
61. A super app is an app that can serve as a platform for smaller “mini” programs
developed using programming languages such as HTML5 and JavaScript. By using
programming languages standard in most web pages, mini programs are cross platform, meaning
they work the same on any web browser and on any device. Developers can therefore write a
single mini program that works whether users have an iPhone or another smartphone."
A browser engine made by a company other than Apple is considered a "super app". It's the same thing Apple got sued for in Europe and lost, and now iOS in Europe has to allow other browser engines.
>A large part of the Microsoft trial was discussing how they colluded to prevent PC vendors from bundling other companies' software
That is pretty much what Apple is doing.
You can try to deny it all you want but Apple is being sued by the DOJ for many things, and one of this things is them forcing Safari on every web browser running on iOS.
I really don't care what Apple does to hobble Safari, so long as they let other more modern and capable browser engines on the platform.
You say that, but consider that they might not have used the word “browser” because super apps are not the same (your attempted redefinition is not how that term is normally used). That's going back to the App Store control of code distribution, there's certainly no technical reason why someone can't use HTML5 or JavaScript in an iOS app given how many do that every day.
Again, I'm not saying that what Apple is doing is blameless but it's important to read the actual DOJ cases so you can understand why these aren't the same. For example, you baldly assert “That is pretty much what Apple is doing” completely missing that Apple is only controlling what you can do with their hardware and is making no effort to prevent, say, Google or Samsung from doing something different on their own hardware. That's significantly different from Microsoft preventing Dell, IBM, Gateway, etc. from shipping alternate operating systems and those kind of legal distinctions matter a lot in court.
Apple already lost this exact fight in the EU where they are now forced to let Chrome use its own browser engine. The US lawsuit is definitely about this, as well as many other abusive practices. It's one of many reasons the DOJ is rightly suing them.
You're trying to weasel around the fact that "Super App" is definitely what a native browser app not using Safari is considered to be. The DOJ is explicitly mentioning HTML and Javascript, and you're just handwaving that away.
Good luck to you sir or madame, I don't care to continue this pointless back and forth.
No, it isn't. It's forcing developers to write native apps instead of web applications, which then lets Apple collect a significant percentage of any sales made through the app. This is why Apple is being sued for this by the DOJ, among many other abusive business practices.
I do not want to pay Apple for the privilege to develop a native app, as well as being forced to buy not just their mobile devices, but a full computer just to develop that native app on, when it could just be done as a web application. It's hurting me, a non-Apple user.
My web app works great on Android, but will never work on iOS because they refuse to implement APIs I need, and they won't let anyone else implement a browser with the APIs either.
I refuse to pay Apple and buy their hardware to be able to develop a native app for their walled-garden platform, where they can then further extort me for any money my users spend through the app I create.
And the DOJ agrees with me, which is why they are suing Apple for abusive business practices.
Your web app is statistically irrelevant. If PWAs were so much better on Android, then why do companies still make Android apps and web apps?
Well, one reason is that most Android phones being sold are so underpowered that you have to make a native app to get decent performance. Facebook for one found out early on that it couldn’t get away with just having an app that was a web wrapper because of low end Android devices.
So where are all of the great groundbreaking popular web apps?
And saying the current US government is in agreement with you about anything isn’t the positive thing you seem to be implying it is…
The vast majority of what people use a phone for works perfectly fine as a PWA on cheap hardware.
Apple is essentially responsible for the shit show that is react native, flutter and all the other cross platform crap. Just let us build for the web with basic support for a native like experience. Works fine on every platform but iOS and iPadOS.
I as a small business don't want to write three separate fucking apps. I don't want to charge customers more to cover that. It's a waste of everyone's time and money.
You get it. It's expensive to develop for iOS (or multiple native apps), and on top of that, once you do get into their app store, you pay Apple a significant percentage of any purchases made through the app, as well as the possibility that Apple will steal your idea and add it to their OS as they have done in the past. Fuck all that noise, when web apps are perfectly capable, secure, and the only thing stopping them is Apple's greed.
You really don't need to reply. I'm just going to give you canned response from here on out because I'm not wasting any more of my time with an Apple shill.
If it’s just Apple, then why are most companies still releasing Android apps.
So Apple is now responsible for the shit show of current web development and at the same time isn’t keeping up or doesn’t care about the web? Which is it?
I could swear that the two most popular web frameworks over the years either came from Google or Facebook.
How praytell is Apple responsible for Google’s Flutter - that they also have basically abandoned.
And run once run anywhere has never worked in the history of the industry.
> So Apple is now responsible for the shit show of current web development and at the same time isn’t keeping up or doesn’t care about the web? Which is it?
Yes. Apple, who once promoted the web as a distribution model, changed course once they realized that doing so would lead to less revenue. They have been actively hostile to open web standards and PWAs as a distribution model.
So you think I'm the only person who ever had this problem? The DOJ apparently disagrees with you.
>Well, one reason is that most Android phones being sold are so underpowered that you have to make a native app to get decent performance.
Bullshit. It has nothing to do with performance, it has everything to do with Apple's abusive business practices not allowing any other web view on their platform, and purposely hobbling their browser for anti-competitive greedy business reasons.
>So where are all of the great groundbreaking popular web apps?
So where are your goalposts moving next?
>And saying the current US government is in agreement with you about anything isn’t the positive thing you seem to be implying it is…
I didn't say the current US government, the DOJ under the previous administration is the one that filed the charges against Apple. But I know you aren't arguing in good faith, so maybe we should just agree to disagree.
Those were always my goalposts - web apps sucked when Microsoft tried to do it with Windows CE, RIM tried to do it, Palm and even Apple. They suck on mobile, electron apps sucked, etc
If the only reason web apps aren’t on iPhones is because of Safari and if there are other browser engines available for Android and Chrome is so much better, wouldn’t you expect to see great PWAs on Android? Especially with it being 70% of the world wide market?
> Bullshit. It has nothing to do with performance, it has everything to do with Apple's abusive business practices not allowing any other web view on their platform, and purposely hobbling their browser for anti-competitive greedy business reasons.
It doesn’t have anything to do with performance of iOS devices that’s true - because Apple doesn’t make any devices with substandard hardware with bad browser performance. But there are plenty of crappy Android device (most of them by sales volume) that do have subpar hardware performance.
But native apps are more performant than web based apps and web wrappers. Are you denying that?
> I didn't say the current US government, the DOJ under the previous administration is the one that filed the charges against Apple. But I know you aren't arguing in good faith, so maybe we should just agree to disagree.
One of us haven’t checked to see what the DOJ’s complaints are about - none of which are alternate browser engines…
>web apps sucked when Microsoft tried to do it with Windows CE, RIM tried to do it, Palm
Wow, that's quite the reach. Again, bad faith.
>wouldn’t you expect to see great PWAs on Android?
I do, YMMV. I even created one myself. But again, bad faith from you.
>because Apple doesn’t make any devices with substandard hardware
"You're holding it wrong" proves you wrong.
>that do have subpar hardware performance.
None of this is about a hardware dick-measuring contest, but you sure are trying to move the goalposts that way. Again, bad faith from you.
>But native apps are more performant than web based apps and web wrappers. Are you denying that?
This is another logical fallacy. I'm done with you, you're comments are not grounded in anything except your hatred of anything not Apple.
>One of us haven’t checked to see what the DOJ’s complaints are about - none of which are alternate browser engines…
Again, just more bullshit from you.
"The complaint also alleges that Apple’s conduct extends beyond these examples, affecting web browsers, video communication, news subscriptions, entertainment, automotive services, advertising, location services, and more. Apple has every incentive to extend and expand its course of conduct to acquire and maintain power over next-frontier devices and technologies."
The "affecting web browsers" part is exactly the thing I described.
Apple already lost that exact thing in Europe, because Europe sued them for it too, and now you can use alternative browser engines on iOS in Europe. Apple's going to lose that one in the US too.
You really don't need to reply. I'm just going to give you canned response from here on out because I'm not wasting any more of my time with an Apple shill.
So you have magically become the first person in history who has created a web app that is just as performant as a native app with local assets, written in a language that is compiled down to assembly and delivered as such (iOS) or even close enough in the case of Android native apps these days (yes I know Java has come a long way, that’s just the point)?
You should be working for Facebook or Google, they both came to the conclusion that their apps should use native frameworks for
performance reasons…
It very much is about hardware. Most Android phones suck statistically (yes I know there are some performant ones. But that’s not what most of the world is buying) and your web app is not going to perform well on them.
By the way, what’s the ARR on your web app? Monthly active users? Have you tested it on one of the low end free phones?
And it’s not me being an Apple shill, your web app probably sucks like every other web app that has ever existed on mobile. I wouldn’t say the same about a native Android app.
You really don't need to reply. I'm just going to give you canned response from here on out because I'm not wasting any more of my time with an Apple shill.
>I'm baffled as to why new iPhones and iPads have a settings toggle to only ever charge to max 80%, but Apple hasn't brought the same setting to new Macs
Because that would affect their battery life ratings, making them close to most other laptops.
I don't follow. It wouldn't change ratings at all. It's an optional toggle that defaults to off. For this reason it doesn't affect battery life ratings on phones or tablets either.
>I was working on some code where I didn't really understand the typescript types and fed it the crazy error messages I was getting and it made a try to understand them and didn't really, I used it as a "rubber duck" over the course of a day or two and working with it I eventually came to understand what was wrong and how to fix and I got into a place that I like and when there is an error I can understand it and it can understand it too.
I have to wonder if you tried a simple google search and read through some docs if you couldn't have figured this out quicker than trying to coax a result out of the LLM.
My (not GP) intuitive answer would be hell no. Typescript messages are pretty hard to google and even parse manually and the LLM suggesting multiple approaches and ways to think about the problem does seem useful. It sometimes uncovers unknown unknowns you might never find otherwise.
I have had cases in which a web search and some good old fashioned thinking have yielded better results than using an LLM, but on average I’m pretty sure the LLM has the edge.
Personally I think Stack Overflow and Google are 95% trash for that kind of problem.
The answers are in (i) the Typescript documentation and (ii) the documentation of libraries that I'm using. I could get lucky with a Google search and it could be worth trying, but I wouldn't expect it to work. Personally my preference is to have a language and libraries with great documentation (Python, Java, Typescript isn't too bad [1]) and really know that documentation like the back of my hand.
If I hadn't had the LLM I would have probably figured it out the same way doing experiments, I might have asked my other "rubber duck"
A tactic I didn't use, which helps in "legacy" systems where I am stuck, is start a fresh project in the IDE and try either reproducing the problem or building a tiny system which is problem free.
I'm hesitant to say what speedup I got out of the "figuring out the types together with the LLM" but emotionally I felt supported and in the process I wrote a whole lot, like I was keeping track of the process in a notebook. I feel a lot times when I have good LLM conversations I wind up writing better code than I would otherwise, not necessarily write it faster -- it's like pair programming.
[1] The typescript docs are great for the typescript stuff, MDN is good for Javascript and Javascript's stdlib
I can think of nothing more tiresome than having to read 200 emails a day, or LLM chat messages. And then respond in detail 5 of those times. It wouldn't lead to "3x to 4x" performance gain after tallying up all the time reading messages and replying. I'm not sure people that use LLMs this way are really tracking their time enough to say with any confidence that "3x to 4x" is anywhere close to reality.
reply