Recent submissions

Comment · 4 months ago
Comment · 10 months ago
I'm very interested in trying this out! I run Claude Code in sandbox with `--dangerously-skip-permissions`. Is that possible with Letta?
Comment · 11 months ago
Do we have Windows support yet?
Comment · 1 year ago
I also recommend listening to the drum history podcast which has episodes with Zildjian and Sabian family members.
Comment · 2 years ago
Clink + windows terminal + Git tools is the perfect setup IMO.
Comment · 2 years ago
First 10 minutes are quite interesting. Analog vs digital, longevity of music, “open” formats.
Comment · 2 years ago
Any recommendation for a provider with dedicated servers in the US?

I’m with a provider now who is phasing them out.

Comment · 2 years ago
Yeah, it won't work without a stable team. And that may be okay in a true agile environment but I've always had a manager who wants some type of estimate/high level schedule.

We do T-shirt sizes mapped to numbers, because recording effort in numbers lets you get an avg etc...

Comment · 2 years ago
Yeah, you are doing it wrong if scrum is deadlines. I've worked with people who had to pull all nighters to get all sprint content done before the sprint closes. I'm using it more as a window to do some cheap analysis on our progress.
Comment · 2 years ago
The things I've taken from scrum and use at every team:

- plan in 2 week chunks

- estimate in points (relative size to something you've already done), emphasis on consistent estimates for each dev.

- make sure you define what 'done' means, and make sure it relates to what exactly you are trying to measure (Eg just coding effort, work till feature can ship?, etc). This is probably the most tricky bit.

- capture total velocity every 2 weeks and eventually use the avg for future planning

- review the entire process and modify things that take a lot of time for devs.

Live from the official Hacker News API

A modern reader for Hacker News · SvelteKit + Skeleton