HackerLangs
TopNewTrendsCommentsPastAskShowJobs

1024bits

14 karmajoined 2개월 전

comments

1024bits
·3일 전·discuss
I have mixed feelings on this (I have some relatives in the medical industry). On the one hand, having a professional scribe is absolutely a positive for the provider, provided they have been trained and are accustomed to that provider. They take away significant cognitive load from them, leaving them able to focus on the patient.

With the proliferation of AI note taking, this advantage purports to have been democratized, but I'm not quite convinced. Since AI summaries are far from infallible, a mistake is bound to sneak in here and there (note that these aren't mere transcripts, but summaries split into sections). The provider may or may not go in and clean up your AI notes afterwards, any mistakes made by AI are effectively disowned in terms of responsibility, and admin will still pressure providers using these note takers as leverage to be able to see more patients than otherwise possible (admins want to see both lower costs and higher patients seen per day).

When you refuse this type of service, you're demanding a higher bar for your notes, but it comes at the cost of a distracted provider (who has grown accustomed to AI note taking, and only has so many hands, so they have to go back to the keyboard every now and then after checking your body).

In summary I think it comes down to how much you care about note quality versus care quality, which is likely different per person. I don't have any allergies, am not on any medications, and generally only go in for routine checkups, so in my case the notes are more or less a bureaucratic requirement that I'm happy to do away with cheaply. For others this may not be the case, and having quality notes may be critical to their care, in which case they should definitely refuse AI scribes.

Of course, none of what I said goes into privacy, which is a significant matter. However, "iPad scribes" which are essentially third party contractors remotely taking care of the notes already exist, so those concerns which arise even without the use of AI are a bit of a different topic.
1024bits
·3일 전·discuss
Nice! I'm quite the beginner when it comes to music production and theory (took me a while to even figure out "Audition" means "Listen"), so I couldn't make full use of this site, but I like ideas presented in your about section. The website is quite functional, which is nice to see from a Rust base.

I'm interested in looking at more commercial products made in Rust, they tend to be far more polished than what I can stumble upon in Github (and are thus a nice showcase of what a bit of polish can do for these frameworks).
1024bits
·4일 전·discuss
I don't know about Yew but I've been using Iced 0.14 which is also a Rust crate inspired by the Elm architecture. It seems like Yew is specifically geared towards web applications, which I suppose is in some ways closer to the original Elm project.

What is your app? Is it intended for personal use, or commercial?
1024bits
·26일 전·discuss
Thanks for flagging that, you've likely saved me a few days of back-and-forth with Apple's reps for the iOS review process. Fixed now.
1024bits
·27일 전·discuss
I'm working on Totem (https://totemkb.com), a collaborative knowledge management system built entirely in Rust without any HTML or web-tech. Currently supporting Windows, MacOS, Ubuntu, and iOS (although the iOS build is currently in review).

Although the goal is to build an efficient all-in-one-workspace, I wouldn't run a company on it just yet. Right now I'm looking for early adopters who don't mind the rough edges and relatively minimal feature set.

You can grab an early build at https://alpha.totemkb.com.

New workspaces will be in a 14-day 'trial' mode, email [email protected] if you'd like me to upgrade your workspace free of charge.
1024bits
·2개월 전·discuss
Discussed a bit more here in 2017-2018: https://forums.nesdev.org/viewtopic.php?t=16414
1024bits
·2개월 전·discuss
Awesome! Thanks.
1024bits
·2개월 전·discuss
I found the Github repo much more informative and easier to read: https://github.com/xai-org/x-algorithm

Your title makes it seem like it's a direct link to the repo. What does your AI generated intermediary add?
1024bits
·2개월 전·discuss
It should be possible on MacOS. If I take a region screenshot with Cmd + Shift + 4 (and then click on the thumbnail in the corner), the preview window that opens stays on top no matter what, so the base functionality exists.
1024bits
·2개월 전·discuss
What're you using to render this blog? Any chance there could be an RSS feed?
1024bits
·2개월 전·discuss
Congrats on launch!

I'm a little bit confused by this. You say it supports 100+ languages, but on the landing page some languages are colored in and the rest are greyed out, and the total number doesn't seem to amount to 100+.

Also, presumably the local model doesn't cost you anything per token. So why isn't that one the free tier, with the cloud model being in the paid plan? Wouldn't that help you get a lot more users cost-efficiently?

Lastly, your landing page has a lot of "AI hallmarks". This may or may not be a bad thing, but at least on here I imagine many people are fatigued from this pattern.

I'm all for apps that don't use Electron. What did you use for this?
1024bits
·2개월 전·discuss
I'd also wager that hiring generalists with no prior experience in the language actually helped them, because they got to instill their culture and style from the ground up with their new hires. Pre vibe-coding, most of those people would'nt have wanted to just jump in and hack away with zero instruction.
1024bits
·2개월 전·discuss
Reminds me of this story from lego:

     I gave the ducks just two coats of varnish, not three as we usually do!
His dad made him redo the lot.

Source: https://www.lego.com/en-us/history/articles/b-the-beginning-...