There should be a tool recommender, which tells you the tool you'd want to use, depending on your preferences and use case.

"I built"

There's levels to prompting cluely. notcluely.in has a built in prompt engineering tool to save people's time. It also has a discount on cluely pro+ subscription.

Sadly, it always completely messes up flowcharts for me that are more than 2 next to eachother. It starts placing blocks in "random" places like putting a 3rd level if the flow chart by the first level and having crazy arrows going around.

I prefer excalidraw or the diagrams.net plugin because of this.

You should have committed with an actual emdash: —

Wow. That's incredible and a bit scary.

Now, internal legal scholars are pointing out the exact mechanical pitfalls from within the system’s own academic backyard.

Yeah no fucking way a human wrote that lmao

I have convinced teams to switch to just after rewriting their makefiles in a fraction of the time and size. There have been some make die hards but they gave in to the team once they saw the justfiles.

Luckily we didn't have to write C or C++. I think the reason why that has so many build systems is because of the lack of a package manager. That entire world needs a cargo equivalent.

LLMs right now massively overuse "it doesn't just X, it Y". Just like how they overuse "you are right to push back".

So I guess the excerpt raises suspicions even though it could just be the author writing that.

This is merely one instance/example of a deeper principle: avoid mixing layers of abstraction

Yeah it should have a clever name like most opensource projects, preferably with a clever recursive acrynomyn. Maybe call it something like the "InfoBay Manipulation Analytical Computational Universal Network Technology."

I think the headline doesn’t convey the substance of the article

I see two reasons this could be: a) either it is by design, so people click and read it, or b) he couldn't figure out a good and short title that conveys the article. So in other words either clickbait or skill issue. :D (I'm just joking here!)

How do you recognize that from these sentences?

Yes. Except without attribution or record of provenance, and we get to charge you and everyone else arbitrarily for access! Are you excited now?

This is saying if you have a module with public functions A and B, they shouldn't call each other, right? But it's not saying that module A shouldn't call module B's public functions. That's what I thought it meant at first, but that seems crazy.

it is, but the question stays - is growing their training dataset by 10% going to make such significant difference that they are willing to actually pay money for it instead of stealing it?

I was that sysadmin at one job. Always catching praise, I'd say,

"Well, uh, if I had thought of that case, I would have fixed it in the first place."

The moment Musk said that my jaw dropped. I didn't follow the guy, knew he wasn't the genius he said he was, but that drove the final nail in my opinion. Fuck me, I can carely "code" PowerShell, but I know the goal is short, easy to read, elegant code. We're I working at Twitter at the time,

# This code creates the log file

# We're not going to check if it exists

# because we want to start with a fresh log each time this runs

# so we'll overwrite the old log, if there was one

# because we don't care in this case

$LOG_FILE = "C:\Scripts\Logs\Archive-Documents.log"

# Now we have a log file.

BAM! 9 lines from 1! I'm awesome!

Our findings suggest structural deficiencies in the ParticleDB QA process. Perhaps tests were not run prior to release. Perhaps the test suite was run, but failed to exercise basic functionality. Perhaps engineers entrusted Large Language Models with the work of testing.

God I miss the days when websites like this had completely free educational materials. I miss Webmonkey from 25 years ago.

You can tell it to be concise or terse.

Is "InfoBay" actually any better? Zero imagination

Ironically in this case the bug was in the MVC controller and fixed as part of a ports-and-adapters AOP audit implementation. MVC isn't immune to it. It was a controller endpoint calling another controller endpoint, because someone was doing a bit of business logic there rather than in the service.

Yes, had they implemented MVC properly they wouldn't have done that. Anyway your point is well taken but as it happens in this case, the deities of irony conspired against you today.

I think the headline doesn't convey the substance of the article, but this is spot on. I just ran into a small, fixable problem my developers had created by doing that just this week.

It was easily fixed, but it shouldn't have been done that way in the first place.