tta

https://console.cloud.google.com/marketplace/details/y-combi...

I feel this too, and I've learned to accept that this is just the way my brain works. Once I've lost my motivation for a certain project there's really no point trying to force it back, and besides, this isn't such a bad thing. The whole point of a side project is that I can work on what I want, even if that means doing something new every 4-6 weeks.

I create a "project" in my to-do list app for each side project, and dump every little idea I have in there while I'm excited and switched on about the idea. When my motivation ebbs and eventually returns (months or years later), I have a low-friction starting point to jump back in, which makes all the difference.

Jumping into a months-old codebase _and_ having to figure out what to build next usually means I feel a bit discouraged and never really get back to that project.

Related: https://news.ycombinator.com/item?id=30696451

This is absolutely amazing. I'm working on a small side project exploring programmability in a smaller design space, and this really takes those ideas to the next level – I'm definitely going to be spending days going over this with a fine-tooth comb.

Thanks for sharing!

Relatedly, Tailwind[1] has fixed my analysis paralysis with CSS colors for good.

[1] https://tailwindcss.com/docs/customizing-colors

I have two sons – 5 and 1 – and this is exactly the kind of relationship I want to build with them. Do you have any advice?

Thanks, and I'm terribly sorry for your loss.

Ha, that's a wild coincidence! What was your app called, by the way?

I considered this, but I'm trying to be extra careful about my email/phone providers disabling my account over spam/etc. Perhaps a CAPTCHA would help?

Thanks for the feedback ... I'm still not convinced because of spam concerns, but I'm definitely going to give this more thought!

I responded to this in a comment below[0], but essentially, this tool:

  - Can call you with a reminder, which can be more powerful than notifications
  - Works across platforms
  - Will eventually support more integrations, such as calendars, webhooks, and telegram/whatsapp/etc.

I'm not able to reproduce this, unfortunately. Can I trouble you to send a screenshot to tim@nudges.fyi so I can investigate?

Thanks, this is useful feedback. The pricing isn't set in stone, and I haven't given it much thought so far, to be honest. Do you have any thoughts around what a more reasonable price point might be?

In addition, I'd encourage you to give the app a shot using the NUDGESHN promo code (3 months free on the pro plan); I'd love feedback on more than just the pricing page!

The temptation to make it perfect and build out a large feature set first is real and paralyzing; I doubt I would've gotten anything out the door if I didn't cut scope.

This took a bit longer than your project (initial commit on Oct 16, I just checked), but I still cut a ton of stuff I'm excited about building. How are you managing scope for your project?

Regarding pricing, I haven't really given it too much thought yet, and the current numbers are essentially just placeholders. Thanks for the feedback, and good luck with your project!

Thanks to everyone who has checked this out! This is the first real app I've launched on HN, and it's a great feeling to know people are using something I've made. :)

To anyone who wants to give the phone call/text messaging features a shot asap, you can use the code NUDGESHN for 3 months free on a Pro plan.

For the record, the free plan doesn't include any call/text credits at the moment because I'm worried about my phone provider disabling my account over spam if I allow this for free accounts.

Apologies, this should be fixed now.

Great question! The closest thing I've found to this app is simply adding reminders as events to Google Calendar and setting up email notifications for each one. I'd say nudges is better in these ways right now:

  - Phone call notifications have been quite powerful in practice. I miss push notifications all the time, but a phone call is harder to ignore.
  - More powerful scheduling: some filters aren't possible to create (like "last day of month") in the Google Calendar UI

I'm working on an app that focuses on the "rituals" you mentioned, so I've been thinking a lot along these lines too.

Things and other similar apps are great for one-off tasks that possibly need to be done in the future ... the power to say "I want to do this in 3 weeks" but not have to think about it until then is hard to beat, and hard to properly articulate until you've experienced it. At the same time they aren't as good for routines where you want to tick off the same set of tasks every time, especially when the routine doesn't happen very often.

The app is in _very_ early alpha at the moment, but I'd love feedback if you're willing to give it a shot: https://checklists.fyi

Relatedly, iTerm's tmux integration[1] pairs very well with this setup.

[1] https://iterm2.com/documentation-tmux-integration.html

https://en.m.wikipedia.org/wiki/Jugaad

HN discussion on the original release blog post: https://news.ycombinator.com/item?id=28140732

I have a couple of comments here.

You should never be going off and work on huge changes without keeping in sync with the base branch.

I agree, but the stacked PR approach doesn't preclude this. If you periodically `autorebase` the stack against `origin/master` right after a `git fetch origin`, your stack stays in sync with `master`.

ate a longer lived branch and make small PRs to that. Then merge longer lived branch into master

Large features don't necessarily imply long-running feature branches, though. I personally prefer feature flags (or some other mechanism for conditional execution) on the base branch for features that are "open" for more than a week or so, say.

"Large" is also subjective. You could have changes that are large in terms of lines of code added, the number of services that are being touched, or the number of different+unrelated concerns involved.

As an example, this week I worked on a semi-greenfield Kafka service. Stacking PRs helped me keep track of the review process a lot more easily than "one big PR" would allow, and the stack was merged in 4-ish days. I structured the stack like this:

  - Add a `proto` file covering messages that this Kafka consumer reads off the incoming topic
  - Pull in a gradle library for protobuf code generation
  - Add in a simple Kafka consumer and producer
  - Add a `Processor` that works on incoming messages
  - Hook everything up; the sevice consumes off Kafka, "processes" the data, and produces back to Kafka

Stacked PRs make all this more difficult.

I'm in agreement. Stacked PRs involve more overhead, but there are times when this is a reasonable tradeoff.

This is good feedback, thank you! I intend "top" to mean "the PR furthest from `master`" and "bottom" to mean "the PR closest to `master`". I'll add a section clarifying this nomenclature.

This is exactly right! The quoted section assumes stacked PRs aren't an option, as a way to introduce the problems that the stacking workflow addresses.

This sounds pretty great, I wish I'd seen this a few months ago! One quick question: does this support adding commits to open PRs, or are you effectively locked in to one-commit-per-PR?

I put “Read Later” things in a pg database via Retool[1], fetch RSS/Atom a few times a day into the same database, and serve it to Fiery Feeds[2] via the Fever API spec[3].

[1] https://retool.com/ [2]: http://cocoacake.net/apps/fiery/ [3]: https://feedafever.com/api

This is doable via a shell script (+ pandoc):

  # 1. Put markdown on clipboard
  
  # 2. Convert to hex
  out=$(pbpaste | pandoc -f markdown -t html -s | hexdump -ve '1/1 "%.2x"')
  
  # 3. Convert to an applescript data class
  osascript -e "set the clipboard to «data HTML${out}»"

  # 4. Paste rich HTML

I started doing this a couple of months ago[1], and the fact that my notes are public acts as something of a forcing function; I’ve found that I engage with technical content a lot better this way. I consider myself the primary consumer of these notes (I’m not looking to provide learnings/advice in particular), but making them public has been a step in the right direction for me.

[1] https://timothyandrew.net/learning

Thanks for the recommendation! I use ddcctl + an Alfred workflow[1], but Lunar looks much nicer!

[1] https://storage.googleapis.com/ta-share/2020-07-10.11.01.02....

Slides 12 and 13 here should help: https://aphyr.com/media/talk.pdf

https://developer.mozilla.org/en-US/docs/WebAssembly#Browser...

Vuepress → Github actions → static site deployed to GCP/Storage. Writing Markdown in VSCode is _significantly_ better than all the online editors I've tried.