HN user

ibash

872 karma

islam.sharabash@gmail.com

Posts1
Comments239
View on HN

That’s one framing, here’s another:

The next CEO of Apple is someone that cares about quality. (As evidenced by how good the hardware is)

Feel free to keep trying shoe models until you find the right one. It took me 25 pairs of shoes from amazon to find one that fit right (mizuno wave rider in wide).

Running shoes are converging on two designs: maximalist shoes with a long foam and a narrow foot, or “barefoot” shoes. Which means it’s harder than ever to find something that fits if neither of those work well for you.

No, it’s more like “installing software installs files on the system”.

That’s not new by any means. It’s no different than zoom installing a native audio plugin for the os, or other software creating files on the system.

Aha! Same for me. A telling sign to me is it will take him 2-3 turns of “that’s not right” before he’ll say “let me do this properly…” and do what I original requested.

Better than rest is a low bar though. Ultimately agents should rarely be calling raw rest and graphql apis, which are meant for programmatic use.

Agents should be calling one level of abstraction higher.

Eg calling a function to “find me relevant events in this city according to this users preferences” instead of “list all events in this city”.

Alchemy 8 months ago

AI is having the same effect on art as the iPhone did on photography.

There’s a lot more photos now, most of them mediocre, but some exceptional.

It does become harder to filter great photography from noise.

Collaboration sucks 8 months ago

Except, they have one person in the ear. Not 4-5, not people giving opposite opinions, not drive by takes.

By the time a race engineer is communicating with a driver all of that has been shaken out. Specific concrete options are given to the driver, and usually only one.

Pydantic ai is pretty good. There were some growing pains as it moved towards 1.0, but going forward the API should be mostly stable.

It does have slightly more complexity than I’d like, but most of the design decisions are sound and the code is easy to read.

I disagree. The ability of someone to read code doesn't grow exponentially, after a few years of experience everyone hits the same plateau. More years of experience does not mean you can understand more complex code.

That is to say, if you target "readable to the majority of engineers with 3-4 years of experience, without them getting confused" then you've hit the mark.

Obsidian plugins have full, unrestricted access to all files in the vault.

Unless something has changed, it's worse than that. Plugins have unrestricted access to any file on your machine.

When I brought this up in discord a while back they brushed it aside.

Disagree. Hooks took one problem and reshaped it, they didn’t actually solve the problem.

With hooks you still need to think about lifecycle, side effects, and state, but the syntax changes.

The real solution is overall application design and thinking through architecture, but unfortunately that’s higher effort than “just use hooks bro”.

That’s not quite right.

The tools are going to get better, and it’s going to lift everyone while doing so. But it will vary across task.

The bottom tier of engineers will have improvements to their code.

The top engineers will move faster. Top engineers will still be great at what they do.

—-

The same thing is happening in music. Everyone gets lifted but on different dimensions.

I don’t think it’s a craft thing, I think it’s a speed thing. Senior engineers are faster in their existing workflows.

I’ve found ai tools most valuable for:

1. Quick “how to do x in y” language

2. Large scale refactorings that are mostly mechanical.

This still takes a bit of guidance to get the right output (and breaking down the refactoring an into multiple steps). But it does speed things up when I would touch 40-some files. I still review all the code.

Use onshape, it’s so much nicer to use something browser based than desktop based. If you’re a student it’s free.

Watch 2-3 onshape tutorial videos and then just dive in trying to make parts for yourself.

If you’re new to 3d printing you’ll soon learn that what you design doesn’t always print right. Welcome to creating things in the real world. This is part of the learning experience (and why you need to learn by doing).

Onshape also has a bunch of public cad designs, so you can look at how other people made things to learn (sort of like reading source code to learn).

Modern react developers forget that if statements exist. When react was class based it was trivial to do:

  render() {
    if (this.dontNeedToRender) {
      return null
    }
  }
Now, because hooks can't be skipped, react developers jump through many hoops to use an if statement during rendering.