don't get the hate, cheap tix to Vegas were great, now it's less competition, if their plane config was not to your liking you can pay whatever you want for any other airline, don't get the schadenfreude.
I don't hate low cost carriers. I absolutely want competition.
I was flying Spirit quite frequently. I'm well prepped. I have a backpack that is the maximum size allowed as a personal item, I carry an empty water bottle and a meal from home. They have an option where you can bid on exit row and big seats in advance. I'd bid the lowest amount ($4-10) and almost always win the upgrade.
Not everyone is aware of this though. I dislike businesses that prey on customers' lack of knowledge to bombard them with fees.
The guy next to me on a flight last year got hit with a $80 fee at the gate because his bag was an inch or so too big. It was his first time flying Spirit. It was cheaper for him to discard that bag and purchase a smaller bag for the flight back.
How much more nickel and diming is there left to be done? Standing seats? [1]
Very anecdotal evidence, but I was on a trip last week and Spirit was more expensive than American which is what I chose. I'm not loyal to any airline.
No one was at the gate hounding at people for bag sizes. I had Wi-Fi on the plane and got a drink and a small snack. My knees also appreciated the slightly longer legroom.
This sounds like nightmare fuel compared to just getting a $100 - $150 annual fee credit card for your preferred airline for free checked bag and just buying your seat.
I am mostly loyal to Delta and by the end of the year, my wife and I will have flown over a dozen times on our dime - many of those shorter flights. I like free checked bags, priority check in, etc
Is this is a joke? Of course it's not going to kill ad-funded anything, ads will still be there 100% in some form, except now all the ad money will go to 1-2 companies instead of the whole world of web publishers. Very smart cheering that on!
> Handing your codebase to an AI company is not nothing.
it's a battle that's already lost a long time ago. Every crappy little service by now indexes everything. If you ever touch Github, Jira, Datadog, Glean (god forbid), Upwork, etc etc they each have their own shitty little "AI" thing which means what? Your project has been indexed, bagged and tagged. So unless you code from a cave without using any saas tools, you will be indexed no matter what.
> When it is worth the pain to load a large bundle in exchange for having really small network requests after the load
...and yet, i keep running into web (and even mobile apps) that load the bundle, and subsequent navigation is just as slow, or _even slower_. Many banking websites, checking T-Mobile balance... you wait for the bundle to load on their super-slow website, ok, React, Angular, hundreds of megs, whatever. Click then to check the balance, just one number pulled in as tiny JSON, right? No, the website starts flashing another skeleton forever, why? You could say, no true SPA that is properly built would do that, but I run into this daily, many websites and apps made by companies with thousands of developers each.
backend has many traps but no one totally dominating "load the slow bundle once, near-native subsequent page loads" narrative which is (for whatever the reason!!) a non-existent illusion on most average daily websites.
> I'm able to quickly stop it and fix any mistake it makes
I would think that's the process too, but according to the article the dude is almost completely hands off:
> You come back to ten thousand lines of code. You spend 5 minutes reading. One sentence of feedback. Another ten thousand lines appear while you're making lunch.
You can't humanly review 10 thousand lines of code in 5 minutes. This is either complete bullshit or it really writes flawless code for them and never makes any mistakes.
why is this so surprising? every place i worked at, going back probably 6 jobs, was using an ORM (django, hibernate, or even a self-built one), they went on to get acquired by Twitter, Microsoft, Uber etc, so not completely stupid or obscure. Even if you have a personal dislike of ORMs, if you ever work with/for another team with an exiting codebase and a DB, chances are you will have to work with one.
what do you mean remember? it didn't go anywhere. I try to understand how to make this useful for my daily programming, and every credible-looking advice begins with "tell LLM to program in style ABC and avoid antipatterns like XYZ", sometimes pages and pages long. It seems like without this prompt sourcery you cannot produce good code using an LLM it will make the same stupid mistakes over and over unless you try to pre-empt them with a carefully engineered upfront prompt. Aside from stupid "influencers" who bullshit that they produced a live commercial app with a one-liner English sentence, it seems that getting anything useful really requires a lot of prompt work, whatever you want to call it.
I've never seen someone put having a high number of junior engineers in a positive light. Maybe with LLMs it's different? I've worked at companies where you would have one senior manage 3-5 juniors and the code was completely unmaintainable. I've done plenty of mentoring myself and producing quality code through other people's inexperienced hands has always been incredibly hard. I wince when I think about having to manage juniors that have access to LLMs, not to mention just LLMs themselves.
Ah.. now you are asking the right questions. If you can't handle 3-5 junior engineers.. then yes, you likely can't get 10-20x speed from an LLM.
However if you can quickly read code, see and succintly communicate the more optimal solution, you can easily 10x-20x your ability to code.
I'm begining to believe it may primarily come down to having the vocabulary and linguistic ability to succintly and clearly state the gaps in the code.
> However if you can quickly read code, see and succintly communicate the more optimal solution, you can easily 10x-20x your ability to code.
Do you believe you've managed to solve the most common wisdom in the software engineering industry? That reading code is much harder than writing it? If you have, then you should write up a white paper for the rest of us to follow.
Because every time I've seen someone say this, it's from someone that doesn't actually read the code they're reviewing.
