HN user

whalesalad

27,778 karma

Hacker. Autodidact. Psychonaut. Linux. Elixir. Clojure. Python.

Detroit, MI

github.com/whalesalad • michael@whalesalad.com

YC '12 - FarmLogs

Posts557
Comments5,387
View on HN
twitter.com 6d ago

DoorDash CLI

whalesalad
4pts0
www.theverge.com 7d ago

OpenAI Launches Hardware for Codex

whalesalad
6pts1
www.youtube.com 3mo ago

Building Pi in a World of Slop – Mario Zechner [video]

whalesalad
3pts0
github.com 3mo ago

Rsloop – an event loop for asyncio written in Rust

whalesalad
2pts0
status.canonical.com 3mo ago

Security.ubuntu.com Is Down

whalesalad
4pts0
dux.now 3mo ago

Dux – Distributed DuckDB-Native DataFrames for Elixir

whalesalad
1pts0
github.com 3mo ago

Pgfmt – a PostgreSQL specific SQL formatter

whalesalad
21pts0
github.com 3mo ago

Sky – an Elm-inspired language that compiles to Go

whalesalad
183pts89
www.nytimes.com 3mo ago

An Inside Look at the Subway's Archaic Signal System

whalesalad
3pts0
www.chinatalk.media 4mo ago

Claude Opened the Straight of Hormuz

whalesalad
3pts0
fedoramagazine.org 4mo ago

Fedora Asahi Remix 43 is now available

whalesalad
3pts0
github.com 4mo ago

The Palantir Impact: Ontology Strategy Connecting Data and AI

whalesalad
6pts0
www.cloudflarestatus.com 7mo ago

Cloudflare pages builds are down

whalesalad
4pts1
fictionalbrandsarchive.com 8mo ago

Fictional Brands Archive

whalesalad
1pts0
www.dotcom.press 8mo ago

A Brief History of Domains

whalesalad
2pts0
www.kohlerhealth.com 9mo ago

Kohler Dekoda – an IoT camera for your toilet

whalesalad
2pts1
bcachefs.org 9mo ago

Bcachefs

whalesalad
2pts0
vala.dev 9mo ago

Vala Programming Language

whalesalad
5pts0
samueloph.dev 10mo ago

Debian 13: My list of new features

whalesalad
9pts0
lists.debian.org 11mo ago

Debian ships 3rd and final release candidate for Debian 13 Trixie

whalesalad
2pts0
omarchy.org 1y ago

Omarchy – an opinionated Arch/Hyprland setup

whalesalad
1pts0
www.nextgov.com 1y ago

VA-based DOGE associate gets 'the boot' after publicly discussing his work

whalesalad
23pts7
www.thetimes.com 1y ago

I was alone on shift when Newark air traffic control went dark

whalesalad
4pts0
www.propublica.org 1y ago

Trump Decimates NOAA Lab Protecting Great Lakes from Toxic Algae Blooms

whalesalad
10pts0
krebsonsecurity.com 1y ago

Whistleblower: DOGE Siphoned NLRB Case Data

whalesalad
818pts452
nathanmarz.com 1y ago

Suffering-Oriented Programming (2012)

whalesalad
82pts23
boringsql.com 1y ago

Time to Better Know the Time in PostgreSQL

whalesalad
2pts0
www.theregister.com 1y ago

Critical PostgreSQL bug tied to zero-day attack on US Treasury

whalesalad
6pts1
www.telegraph.co.uk 1y ago

Chinese AI threat triggers $1T market panic

whalesalad
7pts2
m0n0.ch 1y ago

M0n0wall Gallery

whalesalad
1pts0

Geothermal heating/cooling exists because deep down in the soil temperatures are fairly constant. And the earth is a fantastic insulator both in temperature and sound. Aside from the cost of digging a giant hole, there really is no reason not to be doing this.

I would flip my bitch switch if a datacenter was stood up near me, where I could hear it. I am on 5 acres in rural Michigan surrounded by peace and quiet. I specifically came here for this reason. At the same time, I understand that we need datacenters. And tbh, Michigan is under-served in this space (ex, most of my queries thru the Cloudflare network have to go to Chicago first), and I wish we had more. But not close to residential areas. Not on top of valuable farmland.

My wacky idea was that datacenters should be built on EPA superfund sites. It becomes a win-win. Datacenter gets land that humans cannot occupy, helps/funds partial cleanup, slaps a big ass concrete building down on top of the rest of the mess and kills two birds with one stone. https://en.wikipedia.org/wiki/List_of_Superfund_sites

Also thoughts of mine recently: why are we not doing subterranean datacenters, why are we not doing tall/skinny skyscraper like datacenters (versus enormous sprawling warehouse-style).

LG TV’s are really really good. If you never connect them to the internet. And that rule should be applied to all TV’s. Use an external device like an Apple TV or a self-crafted solution (Roku, Amzn stick, etc all garbage phoning home and listening with Alexa crap)

Treat your TV like a computer monitor (ironic here in this context lol)

I used to have the same problem I would buy fancy moleskins or really nice Japanese grid notebooks, and I always felt like I had to model what I was trying to get out of my head to the medium rather than just focusing on getting it out of my head.

Not too long ago I accidentally bought a huge package of wide ruled spiral notebooks. I hate wide ruled and prefer college ruled. So they sat collecting dust for a long time before I finally looked at the pile and figured I'm just gonna start using these and treating them exactly like you do - a drainage ditch. So far so good, the pile is half gone. Definitely helps to go with the no fucks given approach.

[dead] 12 days ago

I hope that at some point in the future there are 'hotels' all over the land where you can go and trip for half the day in a safe and supportive environment. There is so much healing potential in psilocybin.

I think it is pretty obvious why they often get conflated. There is substantial overlap between the two. "Who you are" and "what can you access" are tightly related. Of course they do not need to be, but it's not a surprise that in the majority of situations they are.

You are building your app with a single user in mind. They can create <thing> (blog posts, photo albums, code repositories, you name it). Eventually you realize, sometimes people are working in teams or groups. Multiple people need to have access to <thing>. So instead of architecting from the get-go that a <thing> is owned by a user (usually with some kind of FK, like an owner_id, or user_id) you want to start by having an abstraction there right out the gate. Things are owned by a team or org, and a user belongs to an org.

This is why a lot of SaaS you use these days will come with a "default project" or "default team" that might just be 1:1 with your own person. But injecting that abstraction layer makes it super easy down to the road to allow other individuals to join or participate in the management of those entities.

This is kinda like the ORM vs no-ORM argument. I think that off-the-shelf auth will accelerate your development for sure (like an ORM) but eventually, you are going to feel constrained by the framework/tool you are using. You will need to work around it. You will find that using it 'correctly' results in poor performance, and so you deviate here and there. Pretty soon you tell yourself, "man I should have just used SQL" or "man, I should have just rolled my own auth". At least ~20 years of software dev has taught me this.

For an MVP or a prototype, I think it's okay to use an off-the-shelf tool. For something serious that will have long-term legs, I would do it myself. I hear all of your concerns and arguments and agree there are a lot of footguns. But again, having spent the better part of my adult life using and interfacing with these tools, I have an innate understanding of how to model auth correctly (separate it from the user, separate users from an 'org' or 'team' entity, etc).

You said it though, 'it depends' is really the right answer here.

Eventually capable of producing more than 200 million screwworm flies a week, the Mission factory was a grotesque marvel of insect-producing efficiency. Operating 24 hours a day, 365 days a year, it was, in essence, a 76,000-square-foot artificial wound. Trays full of meat, blood, and water, each one heated to the exact right temperature to stimulate screwworm growth, moved through the facility on a monorail system timed to the lifecycle of the screwworm.

Imagine working at the screwworm factory.