Readit NewsSomeone should dig into who this is coming from and why. The answers are usually either (a) they got paid to do it by a company selling the tech, which appears not to be the case here, or (b) they went insane on social media.
(can't confirm this personally, but it seems from other comments that it's perfectly feasible to just drive out of New York State and buy a gun somewhere else in the gun-owning US? And this is quite likely where all the guns used in existing NY crime come from?)
I would also note that the Shinzo Abe doohickey wasn't 3D-printed.
Preemptive regulation is absurd.
You might as well just write instructions in English in any old format, as long as it's comprehensible. Exactly as you'd do for human readers! Nothing has really changed about what constitutes good documentation. (Edit to add: my parochialism is showing there, it doesn't have to be English)
Is any of this standardization really needed? Who does it benefit, except the people who enjoy writing specs and establishing standards like this? If it really is a productivity win, it ought to be possible to run a comparison study and prove it. Even then, it might not be worthwhile in the longer run.
Having a super repo of everyone else's slop is backwards thinking; you are now in the era where creating written content and verifying it's effectiveness is easier than ever.
Not a fanboy, but this seems like it went exactly according to plan.
Instead they chose a completely different name with unrecognizable resonance.
Pro audio system design and install, commercial interior design and fabrication, event production.
These pulled from skills I learned from hobbies I did to get away from programming.
I kept myself relevant by making programming the hobby I did to get away from physical work. After a couple years I got the professional programming bug back.
You definitely have other interests that can cross over into an alternate profession. And if you don't, picking up creative hobbies definitely contributes to work life balance and might prevent you from going to an extreme in the first place.
Could have just used a prepend to preserve behavior instead pf going down the rabbit hole of re-interpreting the RFC (which is a cop out IMO; it worked before, a change broke it).
Rules are just context, too, and all elaborate AI control systems boil down to these contexts and tool calls.
In other words, you can rig it up anyway you like. Only the context in the actual thread (or "continuation," as it used to be called) is sent to the model, which has no memory or context outside that prompt.
There may be a day when we retroactively edit context, but the system in it's current state is not very supportive of that.