HN user

sirtimbly

60 karma
Posts1
Comments38
View on HN
NASA Force 3 months ago

ohhh... right, clearly, they only expected Mac users to open the web page or to apply.

Your design is very friendly and approachable. I appreciate the attempt to take another swing at this problem. I've been using Teams for a year now, and they are trying to do some of this same stuff, but what they missed was the key of the composing experience, being too high-stakes. Like you point out:

they’ve often overlooked the fact that writing a post has more friction than writing a chat message, which is why people often revert back to doing everything over chat

Anyway, you have a really good idea with the LLM generated title and TLDR. I worry about not having trust in an algorithmically ranked timeline, so you might want to make that feature optional, or do a top-level tab like they did on twitter. Or give users ability to influence the rankings.

Fascinating. At first I just thought this title was ridiculous, but basically the authors are saying that the magnetic properties of the core affect cosmic radiation detection, so therefore any massive anomaly deep in the earth's core would

1. have an effect on cosmic radiation detection, and 2. is also likely to precede widespread global seismic activity.

They adjusted the radiation detection data for global sunspot numbers and saw a correlation of the specific event of the 2010 Chile earthquake.

If this holds true for more events, a sort of "geophysical weather forecast" could be possible!

The sort of collectible one of his characters would purchase after a successful exit from a crypto startup. But it is beautiful. Also what is this new snowcrash story he was working on!?!

This tool addresses one aspect of my job really well, looking at how a dev implemented my figma design, and showing them exactly which little tweaks need to be made to fix it up. Of course inspector works too, but it's just like buying [Cleanshot](https://cleanshot.com/) instead of using the built in macOS screenshot tools. Providing a more refined experience for something I need as part of my regular job.

It's expensive for what it is, yes. But as a self-employed consultant, these (non-subscription) business expenses for software are my favorite.

I hate the way the health-care system works and how it's affected me and those close to me. I spent much of my adult life paying off medical debt exactly like they describe. Defrayed by parents somewhat, but still a significant burden for many years. On one hand, we have debt and bankruptcy as a tool to help individuals deal with costs that would be impossible to save up for. On the other hand, this quote from the article rings true:

“We have a health care system almost perfectly designed to create debt.”

This was true before the ACA – and is still true.

Ahhh! Now I know what this style of interview is called! Thanks for explaining what the heck was going on in some of the interviews I went through in the last few years. Since 2005 spent a long time at 2 companies and then went self-employed 6 years ago. When getting back into full-time employment around 2019, I had a couple really weird interviews where they gave me some intense timed puzzle solving "games", and then brushed me off. I was so confused because it had no relevance to any of the web development work I had done, ever, in my years of career experience, and it was super stressful.

I thought these hiring managers were insane. I get it now. I think code tests are fine, but timed puzzles just don't tell anyone much about any dev's ability to assemble features out of higher-level tools.

Conceptually, yes. But type definitions are exported by declarative lines in the same code that runs. Basically the schema is imperative code that runs actual validations, the tRPC methodology simply looks at the inferred types from that code to enforce consistency between client and server rather than parsing an actual static schema artifact (e.g. a .gql file).

I've used both. firefly-iii is a fairly good, easy to maintain and host, web app. It's not as good design or UX as Actual - especially since firefly-iii has no mobile experience to speak of. Acutal had great mobile apps. firefly's budgeting interface is a bit of a UX mess.

It's in an established and competitive market. There's money flowing into companies doing this same thing. An investor throwing (some) capital at marketing and growth for this totally functional (and beautiful) product could have made sense.

Sad that this app didn't achieve the scale of subscriptions it deserved. A good reminder that awesome tech isn't usually enough. Do you regret not taking capital to fund marketing and support full time? Or put another way, any other ideas of where you could have spent someone else's money to give you a boost into higher subscription numbers?

The line between configuration and code is always a little blurry. There are some projects where using a .js file for the "configuration" of another operation is incredibly useful. TS makes even more sense in many of those situations. Lots of configuration files require pre-processing already, like merging shell env vars in with textutil or something like that. So, I wouldn't dismiss this opinion outright.

A 225K gzipped .wasm file download for a client-side state management and persisistence layer is not great. It is competitive with some similar solutions, but still a lot for any web app's performance budget

Optimizing for distance from a national forest seemed like a good idea when purchasing a home 5 years ago. Still seems like a solid plan. Home price rises are great, but sorta irrelevant when you're happy with where you live already, and it's likely that you can keep working remotely as long as you like.