GolDDranks

Joined 11 years ago

Karma
3,912
Submissions
916
Member since
Apr 13
[ my public key: https://keybase.io/golddranks; my proof: https://keybase.io/golddranks/sigs/_muJdrzbFuPzV0PR4d_Vl6gZe03xTPAGwnPRaUJuFkA ]

GitLab: https://gitlab.com/golddranks/ GitHub: https://github.com/golddranks/ Twitter: https://twitter.com/golddranks

meet.hn/city/jp-Tokyo

Socials: - github.com/golddranks

Interests: Programming, AI/ML, Data Science, DevOps, Education, Hacking, Hardware, Open Source, Networking, Philosophy, Science, Web Development, Japanese Language

---

E-mail: [email protected]

View on Hacker News

Recent submissions

Comment · 9 days ago
(I'm interested in Homebrew, and I'd love to port my self made game dev framework on Switch 2, but I'm afraid of losing everything)
Comment · 9 days ago
If one follows this and jailbreaks their Switch 2, are they in danger of getting their account banned by Nintendo, and their games unaccessible?
Comment · 14 days ago
You are supposed to renounce your other citizenship by the age of 20. Not everyone does that, though, because it isn't checked.
Comment · 14 days ago
Pretty good job, meaning that you get 96% there (if I recall correctly the results for MeCab which uses CRF). But 4% of kanji words is still multiple wrong furigana per page.

Still, very cool demo!

Comment · 18 days ago
Where did you get that the BB sequence would have finitely many entries? You can choose any integer n for BB(n), and there are infinitely many integers.
Comment · 18 days ago
Comment · 28 days ago
I find it odd that more people don't realize that we are talking about risk of elevated *general intellectual-domain capabilities* as a resource. To be clear, I'm not claiming that LLM + RF is necessarily THE technology that poses the risk, the risk is in recursive self-improvement and whatever technologies will result.

It's very clear to that any specifics couldn't capture the risks, because the capabilities, including the risks, are one level higher than any specific techonolgy. It is the process of advancing technology itself, in accelerating speed, that poses the risk.

Comment · 2 months ago
I've heard that the so-called "yellowish" skin color that non-tanned East Asians tend to have, is due to relative abundance of subcutaneous fat. If that's true, is that captured by the haemoglobin dimension or is it a yet another degree of freedom?
Comment · 4 months ago
I love the idea, and I developed something similar of myself in the past (https://github.com/golddranks/kobuta), but... this reeks of slop. With Rust code, edition="2021" is a dead giveaway.
Comment · 4 months ago
It's very hard when you are overworked to a near-burnout state. I needed to quit to save myself.
Comment · 4 months ago
I'm am not willing to wager my mental health for staying if I feel the current work environment would be detrimental for that.
Comment · 4 months ago
Why aren't the role tags preprocessed algorithmically/deterministically and then fed in as one-hot-encoded vectors alongside the semantic word embeddings? I'd imagine that it would be easier to train to _stay_ in the role an not confuse it, if the current role marker is explicitly set as a part of each input token, and not just implied by some past token. Plus a input separate from the word embedding would be unforgeable.
Comment · 4 months ago
Thank you!
Comment · 4 months ago
I am currently quitting a company of 10 years of employment. And I keep hearing how everything's shit. Btw. I'm located in Tokyo where it isn't as bad, apparently, but...

Let's see. My plan:

- Have my own company and start looking for customers. (Rust consulting)

- Keep looking for job opportunities, but don't succumb for shit jobs.

It might be that I'm too hopeful, but you can't know unless you try.

Anyway, I may join the "everything is shit" crowd in half a year if nothing pans out, but until then, I'm hopeful.

Comment · 4 months ago
Indeed, I realized I had my timeline a bit off after posting that. Of course, we have Lisp ca. 1960. (Pascal appeared 1970, but I don't think that's widely considered memory-safe. ML 1973, and that never got a widespread industry use.)

What I mean is: we had memory safe system-implementation languages in wide spread production use only after/around the times of the publication of that memo; importantly, Java.

We had memory-safe experimental programming languages, and scripting languages before that. And of course, around those times, hardware was fast enough that you could start implementing systems with scripting languages (Perl, Python, Ruby, JavaScript)

And the bit I want to correct is, of course, the point is if they are actually used. In that sense, I'd correct the introduction of Rust around 2023-2026 in actual, wide-spread use.

Live from the official Hacker News API

A modern reader for Hacker News · SvelteKit + Skeleton