HackerLangs
TopNewTrendsCommentsPastAskShowJobs

JasonSage

978 karmajoined 14년 전

comments

JasonSage
·8시간 전·discuss
Yeah, I mostly mean for the TTS, which in my testing is flat and has no emotional register, or no nuanced variation. OpenAI speech in my experience is very good at things like communicating understanding or questions non-verbally using intonation, and I'm yet to see a local TTS model that will do contextual intonation well at all.
JasonSage
·그저께·discuss
I for one am greatly looking forward to the day these kind of voice models can be run locally. It seems like the gap between open-weight and frontier is way larger for voice models than coding/language models.
JasonSage
·9일 전·discuss
It's also a great way to not become the next "graphics programming legend" --I think a fast-moving field with lots of new developments is actually an exciting place to be a pro.
JasonSage
·11일 전·discuss
I think the situation with anti-cheat on Linux is changing. Studios are putting resources into anti-cheat that will work on Linux. If I'm being a bit cynical, I could say this is "just" because of Steam Deck and Steam Machine, but I think the number of potential players switching to Linux right now outside of the Steam ecosystem is starting to be worth considering.
JasonSage
·21일 전·discuss
I appreciate that a lot! The article has a deliberate and explicit scope, and covers it well.

I'm hoping that perhaps my personal perspective shades why "instances" comes up, or why the reaction on HN seems to include the wider scope than the article itself covers.
JasonSage
·21일 전·discuss
From my perspective, I care about the centralization/decentralization aspect a lot, and if I'm coming into the discussion with a much better understanding of the Mastodon side then _of course_ I'm going to ask about the instances--that's the vocabulary I'm going to use to try to probe for flaws and gaps. It's not necessarily that it's the instances specifically I care about, or that I'm somehow technically misguided.

What I hoped to read in the article is how we approach topics like centralization, censorship, moderation, data ownership--and with a technical lens. But I feel like all I got was "here's why instances are the wrong vocabulary" without substantively talking about the part I personally care about and want to marry the technical understanding with. Maybe I just read too shallowly and need to sit with it.
JasonSage
·지난달·discuss
I keep a bookmarks folder of websites that have non-cookie-cutter design.

If I have an aesthetic in mind I'll use some screenshots of those sites in the prompt and phrase their inclusion as: "Look at these slightly non-standard designs that work really well for me." So far I've only seen Claude look for through-lines and high-level takeaways--"user likes <design feature> based on the screenshots, so I'll include that"--and screenshots aren't currently a granularity level where it can lift specific details or produce something derivative.

Other than that I try to encourage specific consideration of: type scale, borders and rounding, padding/whitespace, elevation as shadow vs blur, colors. I don't think one needs to pull every customization lever on every project.
JasonSage
·지난달·discuss
I've had that experience and I've started testing different prompts and inputs.

I find it funny about meeting requirements when you give them, and making safe choices when you don't give direction. So if you're going to rate the output aesthetics and UX/content, but you don't prompt especially much around the aesthetics, you're only getting the safe assumed defaults. It's good at making bootstrap/tailwind clone designs unless you work that angle. For simple web pages, I've started making this the only focus for initial iteration.
JasonSage
·지난달·discuss
> content co-authored with AI that is carefully reviewed

The problem I see is that this is indistinguishable to a reader at a glance.

Distancing the writing from the "AI smell" not only improves the quality by dropping the unnecessary ocean of rhetorical devices, it forces the human to have real weight and agency on what's being said.

I think that act of distancing from raw LLM output through refinement is a huge quality leap. Even if you're only doing the refinement with an LLM, it forces the writing to have more voice and ideas from the author.

I can see the work that went into the analysis here but again, as a casual reader, it's impossible to tell that there were any original ideas here expressed by the author.
JasonSage
·지난달·discuss
When there's no discernable human filter on the text output, reading the text suggests it's what the LLM produced and not what a human considered.

This is low-quality--every single day I witness Codex and Claude misunderstand, mislead, and hallucinate responses based on "assumptions" and I have to fact-check them.

If I wanted a statistical analysis and to be the human in the loop, I would ask the LLM myself, and I would definitely NOT read an article that just dumps the LLM output as-is.
JasonSage
·2개월 전·discuss
I see it as having a blue component and a green component. If the mixture has more green than blue, then it's green.

The analogous version in black and white is "is this dark grey or light grey?" because that's the one asking you to guess which side of the 50/50 split the color is on.
JasonSage
·3개월 전·discuss
I enjoyed this, though my font preferences are pretty stable.

It would be nice if it showed you 1st, 2nd, semi-finalist, quarter-finalist...

It would also be nice to see progress of some kind, a few minutes in I was wondering if I was near completion or just getting started.
JasonSage
·4개월 전·discuss
THINKalpha | Senior Frontend Engineer | Remote | Full Time

We're building alphaLENS (https://alphalens.io), a suite of tools for professional market research and trading. Public registration opens in days. You can see our company at https://thinkalpha.io.

Stack: Svelte (migrating from React/Redux), MVVM architecture with signal primitives, class-based models with IoC for cross-platform targeting (web + Electron, mobile later). Heavy emphasis on testing and performance.

Looking for: Someone who thinks about problems in detail. You should be comfortable with OOP in JS, understand reactive primitives at a deeper level than hooks, and be able to operate autonomously on a small team.

If this is you, please reach out to me with your resume and a brief intro: jason [at] thinkalpha [dot] io
JasonSage
·5개월 전·discuss
Do you think nobody felt that way about cars?
JasonSage
·6개월 전·discuss
Yes, we're getting errors in the checkout action, and I haven't been able to git fetch for 5-10m.
JasonSage
·6개월 전·discuss
ChatGPT recommended this to me recently when I was trying to get some assistance with a usable Tailwind palette. I ended up not needing it right away but it's first in line next time I need to make one.
JasonSage
·6개월 전·discuss
You're right.

People want to pretend fundamentals of economics don't exist AND the company has moral obligations to fulfill to consumers. It's laughable.

It's not just nVidia, I've seen other expensive consumer brands getting the same sentiments.
JasonSage
·7개월 전·discuss
I suspect that the non-Rust improvements are vastly more important than you’re giving credit for. I think the go version would be 5x or 8x compared to the 10x, maybe closer. It’s not that the Rust parts are insignificant but the algorithmic changes eliminate huge bottlenecks.
JasonSage
·7개월 전·discuss
Yeah, that’s a huge over-generalization
JasonSage
·7개월 전·discuss
Local non-utility does not imply global non-value. Of course there's costs and benefits, but it's hard to have a conversation with good-faith comparison using "many see it as overly complex" -- this is an analysis that completely ignores problem-fit, which you then want to generalize onto all usage.