HN user

cdfuller

101 karma

Currently working on FreeInChicago.com

Email: echo pbql@shyyre.pbqrf | tr 'a-z' 'n-za-m'

meet.hn/city/us-Chicago

Socials: - github.com/cdfuller - linkedin.com/in/cody-fuller

Interests: Startups, Web Development, Programming, Dogs, Creative Coding, Pizza

---

Posts1
Comments43
View on HN

As LLMs advance so rapidly I think that all the AI slop code written today will be easily digestible by the LLMs a few generations down the line. I think there will be a lot of improvements in making user intent clearer. Combined with a bad codebase and larger context windows, refactoring wont be a challenge.

I've been thinking about building a browser extension that turns clickbait headlines into factual titles.

"Why is SendGrid emailing me about supporting ICE?" becomes "Phishing Campaign Targets SendGrid Users via Compromised Accounts and Politically Charged Bait"

I think it would be more time than I'd like to commit though.

Can anybody expand on the implications of this?

Being unfamiliar with it, it's hard to tell if this is a minor blip that happens all the time, or if it's potentially a major issue that could cause cascading errors equal to the hype of Y2K.

I imagine the first implementations would be a mix of on-device models and procedural generation. For online multiplayer games I could see the cost of running the models baked into a subscription.

I feel that I don't know enough about the gaming world to actively apply my imagination to the concepts and principles that currently exist in that realm.

Noise 2 years ago

In Chrome I set all sites to be muted by default. I assume Firefox has the same feature.

I think that could be likely. I just asked 4o "When is Cheryl's birthday?" without any other context and was given this reply

Cheryl's birthday puzzle is a logic problem where Albert and Bernard are trying to figure out Cheryl's birthday based on certain clues.

Cheryl provides them with ten possible dates: May 15, May 16, May 19, June 17, June 18, July 14, July 16, August 14, August 15, and August 17.

Here’s the reasoning:

1. Albert knows the month and Bernard knows the day.

2. Albert says he knows Cheryl’s birthday, meaning May and June can be eliminated because they contain unique days (May 19 and June 18). If Albert had been told May or June, he wouldn’t know for sure.

3. Bernard, knowing this, says he now knows Cheryl’s birthday. This eliminates the remaining dates with unique days (July 14 and August 14).

4. Albert then confirms that he also knows the birthday, meaning Cheryl’s birthday must be in July or August, but on a date with no unique days left: July 16, August 15, or August 17.

Thus, Cheryl's birthday is *July 16*.

In the MixRank posting, did you see this section? It looks like they added it after receiving similar criticism.

We're hiring continuously for the positions below— they aren't singular positions that will close once filled. Our philosophy on hiring is that the candidate is more important than the position. For each new member of the team, we design a custom role and responsibilities that are specialized to their interests. Other companies will come up with a long list of specific requirements for a position with the expectation that you'll exactly replace someone from the team, or that you'll be the perfect tetris piece that satisfies the job requirements decided by a committee. MixRank is more pragmatic: we'll first get excited about having a unique individual on the team, then we'll figure out the best way to accommodate their specific talents.

Who is this for? From my understanding it's focused on management level conversations. As a software engineer I wouldn't use this for interview practice right?

Do you build personas with different types of personalities? Grumpy manager on Monday morning, intern who is still getting up to speed, etc.

An example transcript and results/demo would be nice.