snide

Joined 17 years ago

Karma
2,332
Submissions
316
Member since
May 22
A chaotic good web designer trying to not piss off the Internet. I'm currently building Table Slayer, tooling for tabletop map displays. Previously I was an early designer at Elastic and led their UX team for 6 years. Before that I was a founder of Whiskey Media.

You can find more info about me on my website https://davesnider.com

Can contact me dave.snider [at] gmail.com

View on Hacker News

Recent submissions

Comment · 18 days ago
First, this is cool! Well done.

I live next to a State Park. It sounded really cool when I bought the house. No neighbors! Privacy! There is a trail accessible from my properly that goes into some woods, which you only want to be in during the Fall / Spring because the ticks and chiggers are intense.

The biggest issue with sharing a border with the state is the fence line. Technically it's on them to maintain. The woods are filled with mostly 200 foot trees. They exist right up to my property and fall every year during big storms. There goes the fence line. I have dogs so the fence is important. Otherwise they run out into the woods that have licensed bow-hunting during the Winter.

In practice its impossible to get the fence fixed. You are working through layers of bureaucracy and mismanagement. There is no vested interest from a parks service to work well with hundreds of neighbors individually. I'd build fence lines myself, and could easily pay for it, but it's the upkeep of those fences that would be difficult because so many trees (really, it's every year) fall down from their side.

My main point is that sharing a properly line with the government is more like sharing a properly line with nobody. You may as well own that land. Don't expect any upkeep and go in with eyes open.

Comment · 2 months ago
As a fellow filtered well-water maintainer... just give it time. Even the best filtration systems break down. There are lots of moving parts to keep that water clean. Odds are you'll see or smell that brown water soon enough!
Comment · 4 months ago
Thanks duder! It's a fun project.
Comment · 4 months ago
I've been working on a fairly complicated real-time app [0] for playing dungeons and dragons on a TV. It has to do a lot of complicated "Figma-like" things to keep the real-time nature and multi-editor possibilities in check. Oh, and the battlemap is a Three JS canvas with lots of effects and clipping going on.

I'm VERY impressed with Claude 5. I had long ago given up hope that my real-time systems would work without a lot of hacky time-windows and throttle checks. On a lark to try things out, I decided to try out the new model and talk in the output I wanted for a rewrite [1], not the solution. I just listed my problems and places I've had keeping track of my code. It went off and rewrote everything in a much more elegant solution where the state followed a very clear pipeline. It had to navigate YJS, Partykit, Svelte, Three JS, R2 hosting, and a Turso DB I was running in an embedded state for speed.

I watched it hit the wall a few times, and then sudden say... fuck it, i'm making something easier to reproduce over in /tmp to try and solve this (with a more minimal setup). I'm utterly bewildered with how well it did and how much better my app runs. The /usage would have cost me $230 bucks based on how many tokens it consumed if I wasn't already on a max plan. I'm going to miss not having it when the time-window runs out later this month, and will likely occasionally dip in for big projects and just pay my way out of some problems.

I'll also say I like it's MOOD much better now. It's a lot less congratulatory, and talks through it's reasoning in a much better way. Look, it's not a real coder, and I'm sure there is some flaws, but it took my crappy ideas and said... hey, i understand what you want to do, here's a way to do it better. Also, I removed 2x the amount of code that it added. Really impressive.

[0]: https://tableslayer.com

[1]: https://github.com/Siege-Perilous/tableslayer/pull/448

Comment · 5 months ago
I mostly share Josh's opinion, but I think a lot of these posts that talk about Senior vs. Junior experience when working with AIs is kind of rubbish. Sure, you get better results as a Senior working with AI tooling and struggle more as a Junior. Nothing has changed in that equation except the amplification.

What folks seem to avoid is that a Junior (in ANY subject) has the ability to LEARN so much faster with an AI research assistant, and that becoming an expert has accelerated for those with the personal stamina to dig deep (this as a requirement hasn't changed). I spend just as much time with my AI tooling asking questions as I do asking it to "build" or "fix" things. "How does this work?". "Can you suggest other tools?".

I think some people always think about AI as an input / output relationship, when a lot of the time, the fiddling in between, with or without AI was always the important part. Yes people will suck in the beginning, against they always did. I think the good folks though will suck for a MUCH shorter time than I did getting into things.

A lot of people will drop out and get discouraged. That happened before too. Learning things requires persistence. I think the only real case to be made is that AI's sense of immediate pleasure can neuter people away from running into friction. AI natives likely won't understand friction and question it.

Comment · 5 months ago
> Guitars are not about aesthetics

My wife used to work at Acoustic Guitar magazine. She said the most common sales line to sell a guitar at Guitar Center was "it looks good on you". The sound of guitars might not be aesthetics, but in regards to sales, it most certainly is. Everyone plays the same guitars because they grew up seeing their idols play those guitars.

Comment · 5 months ago
Comment · 5 months ago
Comment · 6 months ago
This is why I'm so thankful I went with Lucia early. They sort of sunset their library and replaced it with documentation (and some small utilities) for how to manage and host authentication for yourself. It's always presented as some big, scary thing you can't manage yourself, but I found that taking the week to learn how security and basic salting works, I was able to feel more confident about how everything worked.
Comment · 6 months ago
Comment · 6 months ago
Stores are now putting QR codes for pricing, not listing the prices out on stickers/paper. You check on your phone, and often times walk through "scan and go" making direct payment on your phone.

This is often done in stores where they say that prices can change daily, and that these tools help them keep prices up to date. The darker pattern is what this law prevents, and that even with this sort of labeling, they can't charge you different from what they charge me in the same store.

Live from the official Hacker News API

A modern reader for Hacker News · SvelteKit + Skeleton