CodeWriter23

Well this is ironic, GPL advocate(s) declaring a clean implementation based on specifications infringing due to someone/something reading specs provided under license. Didn't Oracle lose that argument in court as pertains to Android implementation of Java libraries?

I was able to get all the balls stuck on the 'ceiling'. Bug or feature?

Our Constitution accounts for government agents gone awry so there is back and forth. The FDA can go as far as mandating a recall but they need evidence, which they obviously lack at this point or they would just mandate the recall.

This is some FDA operatives using the rules and a PR campaign to wage war on raw dairy, something that is not new in this country at all.

I don't know what their QA looks like but I don't think it's too big a stretch to think they retain samples of every batch and culture for such pathogens. Just to have the ammo to fight back.

It is entirely possible mishandling could cause this. Like the many times I've gotten home from Trader Joe's to find the 'associate' unpacking the box sliced the product package open with their box cutter.

Current state of my workflow: (your feedback is welcome, I'm an autodidact and have been self-teaching myself thus far) I also think my workflow addresses some of the pain points the OP mentioned.

If a problem is a continuation of the current or other chat, switch to it. If it is a new problem or sub-problem requiring something more extensive than a tiny refactor, a new chat is started.

From there,

Start in Ask mode. Ask about existing code I'm trying to modify. If I am interfacing with someone else's code, that is put in reach of the project and ask questions about how it produces certain results or what a function does. Ask the foundational 'bottom-up' questions, how does this work? what routine produces x? Call out specific external sources from the web if it contains relevant information, like an API. Iterate until I feel I have a grasp of what I can build with. Not only does this help me comprehend the boundaries in terms of existing capability and/or shortcomings, it seeds the context.

Move to Plan mode. Provide a robust problem statement and incorporate findings from the Ask into the problem statement, and what the desired output is. Throw in some guard rails to narrow the search path used by the LLM as it seeks the solution. Disqualify certain approaches if necessary. If the LLMs plan isn't aligned with my goals, or I remember that thing I skipped, I amend the plan. The plan prompt I typed is saved to a blank file in the text editor.

Implement.

Validate. If it works, great. Read the code and approve each change, usually I speed read this.

If it doesn't work, I tell the LLM the difference between the expected and actual result and instruct it to instrument the code to produce trace output. Then feed the trace output back into it with explanations of where the output doesn't match my expectations (often times revealing weaknesses in my problem statement). Sometimes when it is a corner case that is problematic, several iterations are required then screen for regressions. If I reach the point where I know I screwed up the planning prompt, I trash the changeds, then I revise the copypasta saved earlier and start a new Planning session.

Read the wording, they aren't complying with US warrants, they are complying with Swiss-issued warrants. US LE/Intel agencies figured out this loophole some 20 years ago.

This should surprise exactly nobody after it was disclosed back in [checks notes] 2021 that ProtonMail gave up user data to law enforcement and also changed their TOS.

Disarming the masses is Communism 101.

Really been wanting something like this. Thanks!

Let's be clear about this, barging into a church to "set them straight" while physically obstructing parents from their children is clearly terrorism. I don't see anyone being charged with terrorism though. ¯\_(ツ)_/¯ just some more commie pretending and hallucinating.

My high school computer lab instructor would tell me when I was frustrated that my code was misbehaving, "It's doing exactly what you're telling it to do".

Once I mastered the finite number of operations and behaviors, I knew how to tell "it" what to do and it would work. The only thing different about vibe coding is the scale of operations and behaviors. It is doing exactly what you're telling it to do. And also expectations need to be aligned. Don't think you can hand over architecture and design to the LLM; that's still your job. The gain is, the LLM will deal with the proper syntax, api calls, etc. and work as a reserach tool on steroids if you also (from another mentor later in life) ask good questions.

I was unaware, thanks for the update.

> customers of a depreciating SaaS product surely churn after a 1-3 years, so they wouldn't make enough of a return

You might think that. Then there's Earthlink and AOL still collecting $5 or $6/mo per mailbox as their cash cow.

PA, Intrinsity wasn't front of mind for me. My point is, Apple has proven they can buy their way into vertical integration, let's look at the history.

68K -> PowerPC, practically seamless

Mac OS 9 -> BSD / OS X with excellent backward compatibility

PowerPC -> x86

x86 -> ARM

Each major transition, biting off orders of magnitude more complexity of integration. Looking at this continuum, the next logical vertical integration step for Apple is fabrication. The only question in my mind, does Tim have the guts to take that risk.

Apple is the company that just over 10 years ago made a strategic move to remove Intel from their supply chain by purchasing a semiconductor firm and licensing ARM. Managing 'painful' transitions is a core competency of theirs.

/whoosh

Ah missed that.

You could buy a house and a 69 Charger for $25K in the 60's with a tidy sum left over.

The Jobs I and Jobs II eras at Apple prove it is constructive.

The Bozo Explosion is in full force at Apple now. They should bring Forstall back. Engineers need to be be humiliated for making stupid decisions.

Why would one want to do that instead of using claude-zai -c from the start? All this is pretty new to me, kick a n00b a clue please.

LDIR? We used DMA for that.

I was referring to LODSB/W (x86) which is quite useful for processing arrays.

"Oddball string instructions", as an assembler coder bitd, they were a welcome feature as opposed to running out of registers and/or crashing the stack with a Z-80.

I seem to recall Musk saying something about OpenAI being over-valued/under-funded earlier this year. Of course he was summarily booed off the stage by the startup crowd.

Costco. Go to a supervisor in a red vest and ask what other Costco has the item that has stocked out and you'll see. No idea what the backend is but the app they use is a terminal emulator that looks straight out of the late 80's.

It was probably pretty loud

> The fact that they didn't do enough research doesn't mean it's okay to scam them, though.

True, if one does not mind risking the Orange Jumpsuit scenario

First OpenAI, then WordPress and now this. I think we are learning there is a point where VCs using open source become allergic to it. My only suggested solution at this point is to be honest about it. Because only then can solutions emerge.

The author does not dispute devices were found. Author expresses a belief it was controlled by a criminal enterprise. Author then claims to understand the intent of said enterprise.

The pattern: 1. Corroborate fact. 2. Pose plausible cause of fact. 3. Present unsubstantiated claim as fact.

Sounds like propaganda to me.

If there's a known vulnerability (which is the case to the best of my knowledge) that can be exploited by an enemy to bring harm to American forces, that would be the very nature of protected National Security Information.