jpnc

One thing I'm missing when modeling FSM like this is different states having different set of constraints, even if only being concerned with nullity. It's a shame having to make the field optional just because you do not have the appropriate value in the initial state of the entity.

One thing I'm missing is pkcs11 API in browsers. This seems to not make sense to US devs from what I could see but if you're in EU you can probably commiserate.

Was just thinking the same. It's also nicely ironic. Also, given the replication crisis I wonder how many of these LLM research papers are actually worth a damn and how many are research paper equivalent of AI software grift.

Hammer makes no attempt to appear human

The title could probably be extended to 'You'll regret using natural keys as primary keys' and it would be right in some ways. Personally, I've come to the conclusion that it's probably best to use both surrogate and natural keys. Surrogates (IDENTITYs, UUIDs what-have-you) as PK from a technical perspective and natural key as 'PK' from a business/data modeling perspective.

Somewhere along the way the wires in my brain have crossed and started associating the word 'content' with 'litter'. So a 'content creator' became 'litterer'. It made it make sense to me why the internet feels more and more awful. It's like a park being more and more covered with litter.

I wonder what the point of that sentence is - to get picked up by HN? Kinda like how any product or service even tangentially related to data suddenly has 'by the way also AI and stuff' added somewhere on their landing page. You don't see 'Developed using intellisense' used in READMEs.

I thought OP meant to imply that the readability could use some tweaking. You have 'disable', 'enabled' and 'False' used in the same expression so it requires some (more) thinking while reading it and trying to decipher what it's trying to do.

>JSS is not currently used to make determinations about artistry, and it still isn’t considered ready to use on certain complex routine components, like beam connections and dance elements on floor; the tech just isn’t there yet

So at what point does a sensor of some kind that does some computation become 'AI'? Is this just marketing buzzword bandwagoning?

We clearly can, but not with gusto. LLM can't feel gusto about anything. If the point is that it doesn't matter as long as a person reading it is convinced there is gusto, then my point is that the 'opinion' of such a thing is irrelevant.

Giving a description of a song is not the same as saying what you think about it.

Performance improvement plan

Unless I'm misreading something the author does not mention breaking anything.

No, there's also the bazzite-nvidia variant if that's the GPU you got. It's fairly easy to setup. Once you start bazizte ISO you're given a choice of the variant you want/need.

I myself run the nvidia variant on my new desktop and the OOB experience has been amazing.

I remember reading Mike Portnoy doing that for Dream Theater while he was in the band (not sure if they still do it). Not just mixing up the set list for the venue repeats but also taking into account that some fans like to go to neighboring venues and wanted to keep it fresh for them too.

Those are called dynamic tests and junit has them.

OT: anyone know what they're using for diagramming? I like how it looks.

We're in the middle of an AI hype. Much like with previous hypes (crypto etc), time will tell whether it was worth it. Unless you're chasing gold or selling shovels the only thing to do is just to wait it out.

Who reviews tests then? Empty tests and assertEquals(1, 1) always show green.

Is this literate programming?

> soon breakpoint will be gone

First I've heard of it. Any links? My search-fu seems to be lacking.

There's https://github.com/tcdi/pgx for writing extensions in rust.

Copilot is basically copying-from-stack-overflow on steroids. Maybe it should be called Copy-a-lot.

Whatever. Regardless of copying mechanisms I expect my fellow developers to understand every suggestion made by such tools.

Location: Croatia

Remote: Yes

Willing to relocate: No

Technologies: Primarily the JVM ecosystem (Java, Spring) and usual enterprise suspects

Résumé/CV: https://www.jpranjic.com/

Email: josip.pranjic88@gmail.com

I've worked in the fullstack enteprise Java ecosystem for about 9 years now. I have helped develop and deliver systems from initial requirements gathering, software architecture setup and testing all the way to production and beyond. Ocasionally have led small teams but would say I work best in the individual contributor (or similar) roles.

Genuine question: what keeps you coming back to this site?

I thought so too. Encrypt the hash with private key -> decrypt with public key and check the hash.

They say it's slower but are trying to close the gap [1]

[1] - https://docs.dolthub.com/sql-reference/benchmarks/latency

My guess is it went the way of Clojure. Small language that's generally loved but does not have a massive mind-share. Every once in a while you'll see some people gush about it, but then it's right back to regularly scheduled language wars.