msingh_5

It’s tedious but likely possible.

If you really want to engage an LLM to help point it towards Cherri (https://github.com/electrikmilk/cherri) to help with implementation

You don’t need to build an app. You can use the built in Shortcuts app.

create a shortcut that turns off all alarms. Can have it read your calendar or whatever as signal to determine if alarms should be on/off for a certain day/time and have it run at a regular schedule.

hey - great question i used whoops journalling feature for several montths.

what I found was that it often throws 5+ variables into one “correlation”, creating a lot of noise where it ends up suggesting X impacting your sleep, when it could have actually been Y.

Pulse is built for n=1 experiments: you isolate a habit (like less screen time, consistent wake up time, caffeine impact), test it, and see if it actually helps your sleep better or not. think self-controlled studies

Hey HN, I’m Mani - Co-Founder & CTO @ Pulse.

This started from my own burnout trying to optimize performance. I tracked everything, changed habits constantly, got a bunch of wearables, but could never figure out what was working vs wasn't.

Most devices just give you a score based on some generic/population model and leave you to figure it out. They treat everyone like an average.

With Pulse, we wanted to build something different -- a way to actually test what works for your body in real life.

Happy to answer questions about the tech, hardware, or what it took to get from idea to (almost) shipping

I do this. I leave my code in a state where it wont compile. So the next day just hitting build will highlight where i left off - which makes it easy to get started, which makes it easier to move to the next thing.

I love this. Particularly, I have terrible recall of things I wanted to do. I would like to install cameras in my home (at least in the kitchen and by the front door), so that I can do things like: - next time I'm making chicken remind me to use this new recipe - remind me to take shopping bags / umbrella etc as im leaving the house (based on weather lookup/my calendar lookup)

I prefer installing things from App Store on my parents' computers cause it will handle automatic updates and provides certain guarantees (i.e. can rely on Apple not letting malware onto their App Store).

KExt: Kernel EXTension.

AFAIK loading custom kexts has become harder since the launch of TouchID on macs, but for an average user its better to live inside the secure world of Apple's tight security controls & encryption - allowing Apple to claim security & privacy as core selling points.

Loading kexts require disabling SIP (System Integrity Protection).

Rosetta 2 makes x86_64 binaries run on Apple Silicon (arm64).

You can dive deep into Apple's platform security guide + arch: https://help.apple.com/pdf/security/en_US/apple-platform-sec...

I've previously had software engineers on my team who didn't know how to update DNS settings on their computer or what a MAC address was. Not everyone gets into a field out of curiosity.

It's the same as most people knowing how to drive but not being able to rebuild an engine or even replace their own windshield wipers.

But I believe school curriculums should include some exposure to general computing as a way to make everyday life easier.

Do you use a custom location? Or default to ~/Dropbox?

You can always symlink to whatever location Dropbox forces upon you…

It is built into Google calendar. But the gcal version has horrendous UX.

It’s called appointment schedule/slots.

https://support.google.com/calendar/answer/11608416

I love calendly because: 1) it checks my calendar for conflicts with a link or suggest times in gmail 2) adds zoom meeting details automatically 3) avoids having to do timezone math

I just send my calendly link and don’t have to discuss back and forth about who’s available when savings tonnes of time.

Coinbase is a hit & miss.

1) For a corporate account, try Gemini or Kraken.

2) Also you should consider paying in USDC (I see in your response that recipient requests BTC), but paying in stablecoin will make your accounting life much much easier. The recipient can convert to whatever crypto they prefer after.

3) There are multiple companies that can help with international payroll. If you don't need your own crypto account and don't want to manage it, consider a service like Bitwage (https://www.bitwage.com/) to handle payroll for you.

You enter a new country, in case Germany, you're automatically opted in to the emergency broadcast notifications, as any other local laws.

The EU legislation allows "opt out" from level 2/level 3 notifications, but is based on the notion that messages are received "without the need for the public to have to opt-in".

So for compliance sake, you're opted in. Maybe this should only happen the first time you enter EU or a member state, and then either your phone or cell service provider should remember your preference (which is probably not worth the resources to implement for the cell service provider, but maybe your phone already does?).

I'd be interested to see if this already exists, i.e. do you only need to opt out in Germany once? Does that opt-out at EU level?

When your wife disabled notifications, she merely opted out of notifications in whatever jurisdiction she was in (presumably US?), but opting out of something in US doesn't mean you opted out of every other similar law from every other nation state.

These are emergency broadcast alerts. Different countries have different laws on these - and in some countries you might not even be able to disable them.

Just because its listed under "Apps & notifications"/"Wireless emergency alerts", it doesn't mean they are "user settings". Its not necessarily the local "carrier" that turned the settings on, its more that connecting to a cell tower in a particular jurisdiction can enforce receiving emergency alerts.

More on the EU alerts systems: https://en.wikipedia.org/wiki/EU-Alert

So that atomic changes are consolidated in a single commit/PR.

Sometimes, the flow for a single feature A: - commit change AA - commit change AB - fix change in AA - extend AB

In this case, until merged into main/master and to reduce noise for the reviewer (especially if using a code review each commit type process), its best to squash all commits into a single "feature A".

I guess the sentiment is more like "Don't make students start programming in IDEs first"

I get it. It shields them from understanding what's happening underneath. But not everybody is interested or needs to know all the things happening underneath, and its okay. If they're going to learn the whole stack, they will.

Ah we built something similar at a hackathon a couple of years ago as a joke. Was briefly the owner of paybyselfie.com.