Alacart
"The data showed that the age-adjusted incidence rate fell from 55.2 per 100,000 in 2000 to 36.7 in 2022, then rose to 38.3 in 2023."
Were more people fat back in 2000? Was the food worse? Though I don’t really doubt that the food industry and trends like you mentioned do contribute, that stat also seems to directly contradict the hypothesis.
Do you really think LLMs will only belong to 2 or three companies in the future, when we already have fairly competitive open weights usable from home (or rented servers)? How would this be anything but the opposite of centralization amongst 2 or 3 companies, which is already the case now? Software has always been displacing things, especially itself.
Your second point makes a lot of sense to me too. I’m not sure how this could handle that facet of human nature, except possibly to indirectly contribute to speeding up the cycle of spec creation.
At that point it’s about optimizing and deciding trade offs, both of which might mean heavily directing the generation in some way. Over time, maybe LLMs or whatever succeeds them won’t go down so many bad architectural paths. We’ve certainly seen that already in the last year or two.
I also don’t think folks like you ever lose your value in these efforts, even if all of it came true tomorrow. At worst it would be you plus the AI, which would always be a more potent combination than say, me with an AI trying to make a browser engine.
Edit: replies are making good points about AI capabilities and where the effort really goes. Let’s just say that I meant this in an aspirational sense, rather than where the rubber actually meets the road today.
Perhaps (sarcastically) this is the new approach, because this is now the point where they’re forced to struggle and therefore actually learn. An exam every other day, let them ask the questions.
Your (I’m assuming well intentioned) arguments are those that people abusing power trot out whenever it suits them, because it works so well to get them off the hook when the people they’re abusing are decent human beings. “Now that we’ve tried our best to destroy things, don’t you think it’s important we all forgive and forget?”
I also think you’re taking my point to mean punishing republican voters, which I’m not. I’m talking about upholding and enforcing laws against the politicians and their accomplices in the party, as they’re intended to be. Rather than taking the less confrontational path of letting it all slide after they lose power. That’s how this mess started in the first place.
He literally said “if you vote for me, you won’t need to vote again”. It’s not an ambiguous statement and doesn’t require extra context. Everything else you said didn’t really have anything to do with it.
Being open to being wrong and course correcting when enough people tell you so is the loosely held part.
If you’re doing that honestly, where they really have that problem and you actually have a good solution, you’d be a jerk not to lightly pitch it at that point.
You could probably do that up to 100 or so customers reasonably easily.
It’s easy to get carried away building every request, especially with early adopters who likely aren’t actually invested yet but may be excited about their own vision for it.
My personal experience is that too much of it leads to the product becoming a sort of shapeless, unwieldy ooze. Or perfect for one customer and few others. Some things can be tough to undo later too, so you might end up supporting them a lot longer than you’d like.
It makes connecting user domains to your app easy and reliable at any scale. Each Approximated user gets the own globally distributed, managed cluster of servers with its own dedicated IPv4 address. Includes (unlimited) edge rule features, DDoS protection, webhooks, and more. Make a simple API call, tell the user to point an A record at the IP, and it’s connected to your app with its own SSL certificates.
Built/building with elixir and phoenix, which has been fantastic.
I would argue that the answer to questions is no. It depends on how you define “smarter”, though. You would likely gain knowledge writing the essay yourself, but is gaining knowledge equivalent to getting smarter?
If so, you could also just read the essay afterwards and gain the same knowledge. Is _that_ smarter? You’ve now reached the same benefit for much less work.
I think fundamentally I at least partially agree with your stance. That we should think carefully before taking a seemingly easier path. Weighing what we gain and lose. Sometimes the juice is, in fact, the squeeze. But it’s far from cut and dry.
I still think it's the best way to live, but the saying "do what you love and you'll never work a day in your life" really is double edged.
Currently working on:
- Further improving the embeddable DNS widget (to help/automate users updating their DNS records) that launched last month
- Rolling out the new hybrid self hosted version that allows traffic and certs to only go through your servers, while getting the full benefit of the cloud version
- Tinkering with some AI ideas for improving the existing WAF features (tricky, but potentially powerful)
- Making Edge Sequences (pattern matching and rules applied at the edge) more flexible and powerful with more composable options and ways to match requests
Recently hit a milestone of over a million domains served!
I already automate apps, machines, etc with the machines API and GraphQL, so my big worries in this area are:
- Woops, some bad logic deployed too many machines (sounds like this policy helps) - Some kind of mistake or attack that just explodes bandwidth usage suddenly
Coming up on a million domains served, it's been a fun ride!
Concurrency? Trivial.
Reliability? Unbelievable. (YouTube Sasa Juric's "Soul of Elixir" talk)
Clustering/horizontal scaling? Built in, even across networks.
Web framework? Competitive with the best (I'd argue better, with liveview but YMMV).
AI/ML? Amazing support and tooling.
Embedded/IoT? Incredible support with the nerves project.
There's only 2 places where I feel it falls down a bit:
1) brittle dev tooling in ElixirLS that trips up new and experienced devs alike. Soon to get better though as competing LSPs are in the works.
2) no official release-as-binary tooling yet. Things are way better in the last few years for releases, and you're probably containerizing anyways, but I am jealous of e.g. Go's single file binaries.
Most of the world is more urban than not: https://ourworldindata.org/grapher/urban-vs-rural-majority
My pixel 5 just stopped turning on one day about 2 years in, and my pixel 7 pro had the volume and power buttons fall out about 3 weeks in (not due to a drop, after googling it's apparently a very widely seen issue).
The service with iFixit was unhelpful, they told me "We keep seeing this and Google says this is wear and tear. We can't submit it for a warranty repair, and if we try we end up eating the cost". After finally complaining on twitter I was contacted by some support person who said to give iFixit this email and they would fix it. They still refused, and after a few more rounds of interactions like that I eventually bought some replacement buttons on Amazon, popped them in, and put a case that covers them on it. I'm fully expecting this to randomly die some time before 2 years is up.
Combine that with Google's extremely strong tendency to abandon everything, promises like these seem well, worthless.
Meanwhile my daughter is using my wife's old iPhone from 8 years ago. My Samsung note 3 and my s8 still boot up and work just fine (though I cracked the screen on one about 5 years ago). It's just so obvious that these phones are very low priority to Google, while other companies base their business around their phones.
Jokes aside, and coming from a place of ignorance, it's interesting to me that a file count that size is still a real performance issue for git. I'd have expected something that's so ubiquitous and core to most of the software world hasn't seen improvements there.
Genuine, non snarky question: Are there some fundamental aspects of git that would make it either very difficult to improve that, or that would sacrifice some important benefits if they were made? Or is this a case of it being a large effort and no one has particularly cared enough yet to take it on?