It's a catch-22 because juniors need AI to be competitive, but you need to do the grunt work yourself for a few years before you really build the skills necessary to advance. I can't imagine learning how to do math by simply reading a solution book.
I don't like the UX but the extra controls on ebook rendering was worth the pain for me, since almost all of my time is just reading the ebook anyways.
When I lived in Chicago I'd see rats and cats eating cat food left out alongside each other. I'm not against helping wild animals as long as it doesn't come with a rat infestation issue.
It doesn't. You already have a rat infestation issue. This doesn't cause it or further it. You think that little handful of kibble compares to the free calories available in an entire dumpster full of chicago deep dish pizza scrap that sits out in the open air day in day out?
Thankfully as of now it appears they're very explicit about what content they share that is sponsored. They might be worried about the legislative backlash if they don't.
Regressions is a meaningless metric to me. Every app has bugs, and most are either rarely encountered or aren't breaking the app. All I care about is interruption of service.
Perhaps new devs should write all their code by hand until they feel comfortable doing that. Then, they can start using LLMs gradually, just a little bit at first, all the way to fully AI generated code.
However, that would just make the difference in productivity between junior and senior developers even more pronounced! It’s really difficult to see how things will play out in the future without junior developers disappearing, causing a slow death of the profession. LLMs will probably never be good enough to do everything a developer needs to do: understand and improve or clean up requirements, consider future needs, test outside the box, evaluate performance and decide where and when to improve it…
Yeah it's a real catch-22. I think you're right though, LLM tech will keep up just enough to replace that lost workforce, till some day development as we know it will no longer exist, perhaps when the code becomes too abstract and complex for normal humans to ever hope to maintain without automation, similar to what happened to most assembly developers when the compiler came along.
And the amount of logic needed to understand code, including how to fix it or modify it further depends on how complicated the code-structure is.
I wonder about this: Does LLM write better code in a better language?
Humans often have more difficulty fixing existing code than reqriting it from scratch, and un-structured un-constrained code would be a big reason for that.
But maybe it doesn't apply to an LLM if it always rewrites all code from scratch?
You do get a public IPv6 IP, which is fine for most people (and with a simple script on a cron can keep a AAAA up to date, not that it changes often). And like someone else said, if you insist, you can use something like tailscale to punch a hole in Starlink's global NAT.
Starlink is a problem that solves itself. If enough fiber rolls out that there's no more customers, they'll scale back satellites (since they only last 3-5 years).
Kind of refreshing though that the "throw more processing at it" scaling we saw in the 90s has returned in a different way. For a while we were really bottlenecked in our advances by relatively low levels of parallelism (most software used by your average user doesn't scale cleanly with more than a few threads).