browningstreet (u/browningstreet)

browningstreet commented on New high-speed Amtrak trains are moving slower than the old ones wsj.com/us-news/amtraks-n... · Posted by u/SCEtoAux

rPlayer6554 · 4 days ago

New trains are very sexy, but what’s really needed is the very unsexy difficult track replacement and enforcing passenger train right of way. (Which may involve side pass extensions and/or freight train length restrictions) More people will travel if the times go down. Maybe the new trains will increase comfort which I could see being a draw.

browningstreet · 4 days ago

I read the article but it doesn’t actually clarify why new trains would run slower than old trains on same track. The tracks may be in need of replacement but the current performance still exceeds the replacement performance.

browningstreet commented on Areal, Are.na's new typeface are.na/editorial/introduc... · Posted by u/g0xA52A2A

rmonvfer · 5 days ago

I don’t get it, this is just a font, right? I mean, don’t get me wrong, I understand the need for these announcements but it feels… cringe? Like, it certainly cannot be THAT deep

browningstreet · 5 days ago

Release notes are good.

browningstreet commented on Show HN: A zoomable, searchable archive of BYTE magazine byte.tsundoku.io... · Posted by u/chromy

browningstreet · 6 days ago

So much of my childhood in one zoomable image. This is incredible.

browningstreet commented on Will Smith's concert crowds are real, but AI is blurring the lines waxy.org/2025/08/will-smi... · Posted by u/jay_kyburz

ares623 · 7 days ago

Some PM in Youtube: “ yes let’s make it harder to tell real videos from AI to make people who don’t know better more susceptible and accepting of it”

browningstreet · 6 days ago

Except: https://support.google.com/youtube/answer/14328491?hl=en&co=...

browningstreet commented on Omarchy Is Out world.hey.com/dhh/omarchy... · Posted by u/kristianp

siliconc0w · 7 days ago

I might be in the minority but I actually like overlapping windows - often the entire window is not necessary to get the data I am interested in. Right now I'm running tests in another window and I have a sliver of that window visible while the majority of the screen real-estate gets used for the browser in primary window.

browningstreet · 7 days ago

I have all my windows centered but pyramid stacked. I can see a bit of everything but my main browser is in the center. Slack is in the upper right, and the browser leaves a bit of the Slack screen open. I keep Obsidian in the lower left such that I can see the organization panel.. it helps me keep a mental map of the notes I'm working with.

In the center are two Chrome browsers representing two separate profiles.. a personal profile for some flows, and a work profile for others. Again, stacked so that I can see most of the tabs.

I've never dared to dream that I could combine this habit with some Hyprland-style "spontaneous windows launched by keybinds". I'd love that. A prime stack of core windows and an omega stack of ephemeral windows.

When I have multiple screens I also tend to stack one above the other, as opposed to left and right.

Corner case all the way.

browningstreet commented on Palantir CEO Alex Karp's Letter to Shareholders palantir.com/q2-2025-lett... · Posted by u/nalinidash

dismalaf · 9 days ago

> MS and Apple PEs are based on stability.

Definitely not how equities are priced.

browningstreet · 9 days ago

I wasn't proposing a rational technical analysis view...

browningstreet commented on Palantir CEO Alex Karp's Letter to Shareholders palantir.com/q2-2025-lett... · Posted by u/nalinidash

dismalaf · 9 days ago

Nvidia and Palantir PE values are at least based on future expectations...

MS and Apple's are based on what? Their margins don't have much room to get better so to increase income by 3-4x they need to increase revenue by a similar factor. Which is hard to imagine.

Or we're just in an asset price bubble, which I think we are.

browningstreet · 9 days ago

MS and Apple PEs are based on stability. They’ll manage better than most to preserve their stability in all of the randomness ahead.

Palantir’s is based on the probability things get worse and they get more government contracts. In fact, it’s a bet on how much worse things can get.

browningstreet commented on AWS in 2025: Stuff you think you know that's now wrong lastweekinaws.com/blog/aw... · Posted by u/keithly

jp57 · 12 days ago

> Glacier restores are also no longer painfully slow.

I had a theory (based on no evidence I'm aware of except knowing how Amazon operates) that the original Glacier service operated out of an Amazon fulfillment center somewhere. When you put it a request for your data, a picker would go to a shelf, pick up some removable media, take it back, and slot it into a drive in a rack.

This, BTW, is how tape backups on timesharing machines used to work once upon a time. You'd put in a request for a tape and the operator in the machine room would have to go get it from a shelf and mount it on the tape drive.

browningstreet · 12 days ago

Yeah, but they've been robotic for decades since.

browningstreet commented on Vibe coding tips and tricks github.com/awslabs/mcp/bl... · Posted by u/mooreds

nzach · 14 days ago

>Provide detailed specifications for the work to be done

I've been playing around with vibe coding for a few months and my experience doesn't really match this advice.

I used to think this was the correct way and based on that was creating some huge prompts for every feature. It took the form of markdown files with hundred of lines, specifying every single detail about the implementation. It seems to be an effective technique at the start, but when things get more complex it starts to break down.

After some time I started cutting down on prompt size and things seem to have improved. But I don't really have any hard data on this.

If you want to explore this topic one thing you can do is to ask you LLM to "create a ticket" for some feature you already have, and try to play around with the format it gives you.

browningstreet · 14 days ago

I have found it better to have stronger scope for 2nd and 3rd iteration feature sets in mind.. refactoring because you didn't think you'd be adding a certain kind of feature or filter or database scope is worse than knowing ahead of time that's where you were going.

A little different than "spec", but one-shotting things works great if that's going to get you as far as you want to go. If you're adding neat-o features after that, it can get a little messy because the initial design doesn't bend to the new idea.

Even something like adding anti-DDOS libraries towards the end, and then having to scope those down from admin features. Much better to spec that stuff at the outset.