Hacker Newsnew | past | comments | ask | show | jobs | submit | dflock's commentslogin

I've been using this skill with Claude on a new project and it's nice, but it's quite expensive, token wise. It's ~$5 per use, on my codebase, which seems fairly high to me. This is according to the crappy stats in the claude usage thing, so not sure how accurate that is.

Good at research, terrible at product?


From https://en.wikipedia.org/wiki/The_Garin_Death_Ray if anyone else was wondering.


You need example product pages.


I like you blog and tried to add it to my feed, but it doesn't appear to have an RSS or Atom feed. I know beehiiv supports feeds - any chance you could switch it on?



That's an interesting - and maybe correct - point. Looking at the examples, it seems very long winded and not something I would want to write myself - but maybe I don't need to care about that anymore, as you say!


This time around in the pre-covid days, F# had a surge of popularity, there was Fable and Giraffe and an elm-style set of frontends (the generic pattern is called MVU - Model View Update), it didn't take off because A) we are still a trend/fad-driven industry and B) there was no AI to help hold your hand in refactoring all of your apps.

These days? Doing this FE SPA framework for Effect/typescript familiarity or Fable for F# familiarity and a model-view update pattern can help one do CQRS better, force you to think about stronger Hexagonal Architecture patterns, and overall help your application care about long term correctness more without you having to hand code every discriminated union as such.

The LLM can't replace you, but it can be an enzyme that lowers the activation energy required to switch from bad old MVC mutable tag soup to MVU frontends with strong data interface designs held in sqlite-dbs-per-aggregate (if you are of a DDD or event sourcing taste, which this pattern does not require!)


This looks interesting, and I've been keeping an eye on this for a while - but does anyone have experience from actually using this for real?


I see people are doing scripts or other things to remove shorts from their feeds, but there is a simpler solution. Take your RSS URL of a channel, e.g.:

https://www.youtube.com/feeds/videos.xml?channel_id=UCxSGC9B...

Replace the `channel_id` with `playlist_id` and replace `UC` with `UULF`. This prefix will only list normal videos:

https://www.youtube.com/feeds/videos.xml?playlist_id=UULFxSG...

----

From this comment: https://news.ycombinator.com/item?id=48032508


I'll give this a try!


No one knows how many vulnerabilities there are in closed source medical record software - because we can't check. There are _probably_ loads though, because that medical software is super terrible in every way that we _can_ check.


Well the closed-source EHR applications that use NoSQL databases such as MUMPS (InterSystems Caché) probably don't have many SQL injection vulnerabilities.


Or voting machines.


I wasn't aware that there were any public, commonly-used voting machines that we could check.


Isn't anything closed-source by definition this? Why speak of the subset of closed-source medical record software when it's just the entire class of software?


SQL injection and XSS come up in dynamic analysis too.


I've tried to use state charts for frontend development a couple of times, but bounced off. IIRC, I was using xstate with vue, and I found that they were hard to retrofit to existing systems, and where I tried, I found that the boundary between the part of the system controlled by xstate and the rest of the system problematic. It felt like it would work better with everything "inside" the statechart, but that's a big lift for an existing codebase.


Out of curiosity, was that before or after LLM agents?


Before. I could, probably, now get an LLM to refactor everything to be inside the statechart - but I'm not sure if I actually want that.


Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: