Think google maps purchasing and processing satellite imagery; if you want to compete, you also need to regularly update petabytes of data. That's table stakes, even if you have one user.
3,194 karma · joined April 28, 2014
Think google maps purchasing and processing satellite imagery; if you want to compete, you also need to regularly update petabytes of data. That's table stakes, even if you have one user.
> Global oil demand is forecast to rise by 2.5 mb/d from 2024 to 2030
Beyond that, culture has a huge role to play. Many complex lifeforms learn how to survive from their parents and peers. Those groups with less adaptive strategies will be wiped out. For many organisms, they are not "thinking" per se, they are processing sensory data in the way they've been taught. The "thinking" was done by multilevel selection, weeding out ineffective strategies.
IOW, no organism technically needs to think through a problem from first principles. There's always some cultural heuristic to fall back on.
Second paragraph is spot on. The search space is far too large for evolution to provide direct solutions for every challenge a multicellular lifeform could face. General solutions rule. But it's likely that cultural adaptation plays a larger role than individual cognition.
One could argue the prokaryotic life is 100% instinct though - adaptive responses seem to be pretty rare in bacteria.
It's no wonder inexperienced developers don't get as much out of it. They define a vague structure, full of problems, but the sycophantic AI will spew out conformant code anyways. Garbage in, garbage out. Bad ideas + fast code gen is just not very productive in the long term - LLMs have made the quality of ideas matter again!
https://upload.wikimedia.org/wikipedia/commons/5/53/Dymaxion...
If you have a system of a dozen components with well defined interfaces, you could imagine an LLM rewriting and redeploying each component one at a time, without changing the observable properties of the system.
We'd show up to a frat party with a survey and breathalyzers and got people to line up before things got ... weird. As soon as word caught on that we were measuring blood alcohol levels, the boys would start chugging alcohol at dangerous rates to see who could blow the highest BAC. So much for promoting safe drinking behavior! And this would obviously invalidate the research, so we had to go in like a strike team and collect as much data before word got out!
There is something special about this wavelength; it's not a coincidence! It would be very surprising if the evolution of ALL life honed in on this critical range of the EM spectrum but left human perceptions open to wide interpretation. IOW interpreting "blue" is probably hard wired trait into most evolved life because we share a sun and the earth's atmosphere.
In organizations that value innovation, people will spend time reading and writing. It's a positive feedback loop, almost a litmus test of quality of the work culture.
So it's possible to be both skeptical of how well these results generalize (and call for further research), but also heed the warning: AI usage does appear to change something fundamental about our congnitive processes, enough to give any reasonable person pause.
No so with CI tests. Input and output are 100% specified and no manual intervention is even possible.
There are some problems where "correct" can never be well defined. Think of any feature that has aesthetic values implied. You can't just unit test the code, brush off your hands and toss garbage over the wall for QA or your customers to pick up!
I use this technique mainly to avoid an over-reliance on automated testing. I've seen far too many painful situations where the unit tests pass but the core functionality is utterly broken. It's like people don't even bother to run the damn program they're writing! Unacceptable and embarrassing - if encouraging ad-hoc tests and QA-up-front helps solve this, it's a huge win IMO.
This is where I've landed as well. Unit tests are for locking down the interface, preventing regressions, and solidifying the contract - none of which are appropriate for early stages of feature development. Integration tests are almost always closer to the actual business requirements and can prove direct value - ie only once the integration works, then lock it down with unit tests.
I've also toyed with a more radical idea: don't check your tests into the git repo. Or at least keep the developer tests separate from the automated tests. Think about it: what rule says that the tests used in development should go directly into the CI test suite? One is designed to help you navigate the creative process, the other is designed to prevent regressions. I think we do a disservice by conflating the two scenarios into one "testing" umbrella. During TDD, I need far more flexibility to redefine the shape of the tests (maybe it requires manual setup or expert judgement or ...) and I don't want to be hampered by a (necessarily) rigid CI system. Dev tests vs CI serve two completely different purposes.
Many of us have seen images like this: https://www.asu.cas.cz/~bezdek/vyzkum/rotating_3d_globe/figu... which are effective at showing the shape and gravitational anomalies but is wildly exaggerated on the height axis. Visualizing to scale would look indistinguishable from sphere.