mikesurowiec

From the full announcement

> The new classifier also comes at the cost of flagging benign requests more often during routine coding and debugging tasks. As with all our safeguards, we’ll continue to refine this to better distinguish genuine misuse from legitimate requests and reduce false positives.

When I saw this, I thought it was a paid advertisement on HN. yuck. At least when other companies do the jobs post it always includes "is hiring" to make it clear what it's for.

I worked on docs at GitHub which are open source, synced to an internal repo, and deployed on internal infra. I recall jumping through many hoops to make it work safely. These were workflows that had secrets access for deployments, and I recall zipping files, doing some weird handoffs/file filtering between different workflows based on the triggers and permissions. Security folks were really quick to find any gaps =)

Glad to see a few more security knobs on actions these days!

Thanks for pointing out Parcel RSC. I just read through the docs and they do a great job of explaining RSCs from a place I can understand. In contrast to NextJS where it’s unclear where the framework stops

https://parceljs.org/recipes/rsc/

I expect data centers will become more expensive precisely because everyone is building at the same time. Supply chain crunch

I’ve seen people spin Results in their favor within a company, where you can validate them, but for interviews it seems nearly impossible to validate.

Does anyone have techniques for that?

You're absolutely right, apologies!

A rough idea of the price differences...

  Per 1k tokens        Input   |  Output
  Amazon Nova Micro: $0.000035 | $0.00014
  Amazon Nova Lite:  $0.00006  | $0.00024
  Amazon Nova Pro:   $0.0008   | $0.0032

  Claude 3.5 Sonnet: $0.003    | $0.015
  Claude 3.5 Haiku:  $0.0008   | $0.0004
  Claude 3 Opus:     $0.015    | $0.075

Source: AWS Bedrock Pricing https://aws.amazon.com/bedrock/pricing/

Is this the same reason you wouldn’t pick up trash on the floor?

Relative speed difference is another key factor — arguably more important than absolute speed — but is more difficult to regulate.

When traffic on the highway is near a standstill you really shouldn’t fly down an open lane at the highway speed limit

The post states "they used Cap’n Proto before they hired me"

If you're interested in learning more the term to search is "takt-time planning", specifically as it relates to lean construction methodology rather than manufacturing.

https://en.wikipedia.org/wiki/Takt_time

I really enjoyed this, thanks for sharing. My takeaway is don't be afraid to put an unreasonable amount of time towards something.

It reminds me of PG's essay "The Bus Ticket Theory of Genius", which is like a hack on this idea. If you're obsessively interested in something, you're bound to spend an unreasonable amount of time on it.

Taking it even farther, there's a Revisionist History episode on the song Hallelujah, who's original version took over two years to write. The two components to "experimental" genius: time and iteration.

http://www.paulgraham.com/genius.html https://www.pushkin.fm/episode/hallelujah/

We're also using a fork of gifted chat; pretty much use it for the layout measuring and the inverted scroll view. Hoping to move to FlatList at some point!

My team has been working on our app for 1.5 years now and of all the technical choices we've made, React Native is probably our favorite. It's taken us through the prototyping stage and all the way to production without many issues. Granted, we're a very small engineering team of 3.

Pros

- We haven't done performance tuning and haven't had any user complaints about performance (it's a multi-channel chat app)

- Most of the time, changes "just work" on both platforms

- Javascript :D

- Development velocity is great, especially w/ UI changes

Cons

- Wish we had better text input control

- You still need someone who knows about native app development on each platform

- Upgrading versions can cause breaking issues (this has gotten better)

- Lesser used 3rd-party packages are often incomplete across platform, so a fair amount of patches

- Changes on one platform have the potential to break the other platform (so testing can require a lot of back and forth)

edit: formatting halp

instead of the color (which personally I like), you could use numbers, so the first person who replies is #1, next is #2, and they re-use that number for the extent of that thread. That way if you're having a discussion with someone, you know it's still them

Hey, glad you found the blog. That's actually required by the class; we turn in assignments in the form of blog posts. So you'll see customer discovery interviews, our hypothesis for the project, and all that jazz. If you're interested, I can give you an in depth analysis of the technical side here. Thanks for checking us out!

The funny thing is there's actually only one advert on the page (far left). The other things are informational flyers so people know what's happening around campus. I guess we better make sure to space them out so it doesn't look like an ad blast. Thanks for the feedback! I'll get those map popups fixed tonight too.

Thanks, I appreciate it! We'll be iterating as fast as we can.

Wow, very impressive! I will definitely be trying this out. It reminded me of my discrete mathematics class, so now I'm wondering if there are any other cool principles that can be applied to design

At first I thought the lowercase 'g' was weird, because it's facing to the right, but then I guess it makes sense with their 'seamless motion' tag.

Can't argue with that. Money shouldn't be the driving factor, money is nice, but there's certainly a point of diminishing returns.

No fun on the iPad :(