HN user

CleverLikeAnOx

659 karma
Posts3
Comments73
View on HN

This blog post shows how not to use AI. The author would have been unlikely to write such a uselessly redundant conclusion if they had to type it themselves.

Edit: I like the post, but it didn't need to be padded with fluff.

This is impressive and mirrors a lot of thoughts I have had about the future of backend frameworks. I love the focus on local development for things like pub/sub.

An old timer I worked with during my first internship called these kinds of issues "the law of coincidental failures" and I took it to heart.

I try a lot of obvious things when debugging to ascertain the truth. Like, does undoing my entire change fix the bug?

I use it for programming and math. When I started using kagi almost 2 years ago, I had to go back to Google occasionally. Now I basically never go back to Google search.

I took a class psychology class on learning that was superb.

It taught how to memorize stuff: spaced repetition and semantic encoding. Spaced repetition is reviewing the thing at increasingly spaced intervals of time. Semantic encoding is coming up with connections to the idea. The wilder the better as that tends to be memorable.

The class taught some strategies for creativity such as use of analogies and trying to combine disparate ideas.

The class also taught cognitive biased, like loss aversion.

This class was life changing. It was also easy because the teacher applied the best practices she was teaching.

I would say something like that class is the basis for teaching people how to think.

You can improve without measurement by using reasoning and experience. As an example, Groupon drove itself into the ground by only improving itself in ways it could measure. They added many nagging features that a/b tests showed worked. However, the CEO ignored his less measurable feeling that this was cheapening the brand.

Why:

Avoid time wasting nit-picks on PRs.

Consistent formatting may be easier to quickly read.

Why not:

Avoid taking a dependency.

Avoid "fix formatting" commits (or the complexity of having a system auto-apply formatting).

Formatters don't always make the most readable code. Sometimes non-standard formatting actually communicates more clearly.

I found I formed a deeper connection with my D&D group once we started doing non-D&D things together. It was a switch from consistent friends to close friends.

It would probably be a stretch and overreach, but the angle I would take is that they are competing not on the merit of their products.

Consider airline miles. Each time I purchase a ticket, instead of choosing the best deal (fair competition), I am incentivized to choose an airline I have chosen in the past so as not to fragment my points across several accounts. And of course, these "rewards" are all a price passed on to the consumer.

This places all the trust in the institution that mints verifiable credentials. (or the institution + Auth0 if they use Auth0).

This is good for use cases where you want to assert that an organization says something about you (e.g., you have a degree).

It is not good for use cases where you want to assert that you say something (e.g., I voted for Blah, or I authorized this transfer).

I think for every spite spender there is at least one other person who is habitually cautious now. I have found it harder to get some people to go out and do things.

AI may rival programmers some day, but it isn't close yet. We can't extrapolate from Topcoder questions to software development as a whole. Requirements are rarely so crisp, and the systems we build are never so small. If an AI could optimize the layout of a few cogs, it does not follow that it could also design a whole factory.

The idea with Bear is to refine the existing features to the point of perfection, instead of building new features or pushing monetisation.

I love this. I wish more software was built with limited scope. Not every application needs to grow larger and change forever.

Could be to allow running untrusted backend code. E.g., so kind of third-party extensions system for your product. Webassembly is good for sandboxing.