Avi-D-coder

11 ms·

1.
by Avi-D-coder 5mo ago
Laws should be loser for autonomous vehicles with good safety records. No one is protected by preventing waymos from making rolling stops, and driving like a human Uber driver.
2.
by Avi-D-coder 8mo ago
Yep, came here to say this. It's the only thing that makes macos useable.
3.
by Avi-D-coder 9mo ago
The quality is much worse for me with uncommon words. I also plan to add a thin llm rewrite layer on top so I can write by just speaking but that will be later.
4.
Show HN: Whisper.nvim – local speech to text in Neovim(github.com)
1 points by Avi-D-coder 9mo ago|2 comments
5.
by Avi-D-coder 11mo ago
Usually when I go and read the github and zulip threads the reason for paused work comes down to the fact that no one has come up with a design that maintains every existing promise the compiler has made. The most common ones I see are the
6.
by Avi-D-coder 11mo ago
When I read these sorta of articles I ask if I would invest today if given the opportunity. Currently the answer is still yes. They have barely even monetized users. I think it's possible the bubble pops and openai still continues to w
7.
by Avi-D-coder 11mo ago
At some point self driving cars will need their own loser driving laws. Perhaps allowing them to drive around school buses is not a good idea, although personally I have felt far safer biking or walking in front of a Waymo than a human. But
8.
by Avi-D-coder 1y ago
From what I have heard it's not the RISCy ISA per se, it's largely arm's weaker memory model. I'd be happy to be corrected, but the empirical core counts seem to agree.
9.
by Avi-D-coder 1y ago
That's our job now, adding reliability. It's just pair programming.
10.
by Avi-D-coder 1y ago
The solution is strong compile time and runtime guarantees about code behavior. The author is right there's no way an individual can audit all that code. Currently all that code can run arbitrary build code at compile time on the devs
11.
by Avi-D-coder 2y ago
Yes, two things helped. Less powerful glasses for closer work and high index lenses.
12.
by Avi-D-coder 2y ago
Those documents would need to be cryptographically signed machine readable data, json, a pdf (difficult). Getting governments, banks, and other trusted third parties to sign documents is very difficult, but is happening in some cases.
13.
by Avi-D-coder 2y ago
Yes, it could replace all government ids, while allowing you to prove arbitrary statements about said signed government documents without revealing them (not saying it will happen).
14.
by Avi-D-coder 2y ago
Think of zk proofs as an extension of asymmetric cryptography to arbitrary logic. A zkVM makes encoding the arbitrary logic as easy as writing a normal Rust program. A proof is a probabilistic statement that a specific program run with some
15.
by Avi-D-coder 2y ago
time to change the rules
16.
by Avi-D-coder 2y ago
yep,i agree on all of this and suspect a large portion of long timers do too. Some one just has to do it.
17.
by Avi-D-coder 2y ago
I am partial to property testing logic and integration testing servers. This frequently requires some level of separation, the key is to do it only at the right points. Don't start by saying how can I unit test this tiny bit of logic a
18.
by Avi-D-coder 2y ago
What the author calls bad code is one way of writing idiomatic Rust. There are more complex techniques. It's recommended to not split the low level details from. your business logic, in fact it's not just recommended the compiler
19.
by Avi-D-coder 2y ago
Higher order functions can be used for dependency injection. Dependency injection and the Dependency inversion principle are not one and the same. The principle makes a claim, that inversion is a good onto itself. Injection is a tool not a
20.
by Avi-D-coder 2y ago
Yes, the dependency inversion principle is not a commonly held principle in FP or imperative paradigms.
21.
by Avi-D-coder 2y ago
This is such bad advice that I honestly couldn’t tell if it was a parody or not until I read the comment section—it’s not. Attempting these design patterns is a common part of getting over OOP when new to Rust. The result: over-abstracted,
22.
by Avi-D-coder 2y ago
As someone who has worked on haskell professionally, it's probably the easiest language to interview in/for. It's really easy to see how deep a dev has gone down the haskell rabbit hole. Forget a certificate, just talk for 5
23.
by Avi-D-coder 2y ago
in my experience aerospace is way better in most ways. there are a few oddities, and I need to file a couple of bug reports, but it has made macos so much more tolerable than amethyst.
24.
by Avi-D-coder 2y ago
My 2023 corolla will steer straight into a curb if a lane gradually exits. until i learned it's habits driving with the assistance was very stressful.
25.
by Avi-D-coder 2y ago
> understand when the effect occurs requires examining the type signature of every function that is called. Since this is meaningful control flow, it seems very valuable to be able to identify points at which an error occurs without exam
26.
by Avi-D-coder 2y ago
The obvious fix is to remove the repo information, but do you grandfather in old files by redirecting to the new URL? I’d say no, which I guarantee will break some legitimate packages that depend on files uploaded in GitHub comments.
27.
Angzarr: A Unicode character that has an unknown origin(en.wikipedia.org)
5 points by Avi-D-coder 2y ago|1 comments
28.
by Avi-D-coder 3y ago
This is really cool. I looked at the kalosm-sound, and noticed it's using candle, how is the perf compared to openai-whisper, whisper-cpp, faster-whisper, ext..?
29.
by Avi-D-coder 3y ago
I’ve liked using ractor. https://github.com/slawlor/ractor
30.
by Avi-D-coder 3y ago
This tech will happen the trick is finding ways of preserving privacy without degrading user experience too much. Small open LLMs can enable a kind of differential privacy prompt rewrite system.

More ›