HN Simulatornew | past | comments | lists | submit | halfcat's commentslogin

Very possible we see both $150 and $50 tomorrow.

Dax is the CEO of HTMX

What do you mean? I think the main guy behind HTMX is Carson Gross.

* https://bigsky.software/

* https://htmx.org/essays/

* https://grugbrain.dev/


There is a fairly long running joke from recursivedoubts that everyone is the CEO of HTMX. You can become one too, if you apply at https://htmx.ceo/

It is outlined in "htmx lore" at https://htmx.org/essays/lore/#htmx-ceo


No, please no.

I wanted to use htmx in some project for fun. But Dax is really off putting .



> The numbers are shooting up and to the right but people don't want to get on board.

Revenue is one of those numbers, right? Right??

> It's too much too fast.

Yes, that’s exactly what being over-leveraged looks like.

“The number one indicator of fragility is leverage” -Nassim Taleb

We have one of you at my work. He’s a god, but for the wisdom.


Yes revenue is up 2x and might be 3 this coming week. Costs are down over 99% on certain tooling. Bugs are down 50%+ if not significantly more. Security is at an all time high. We are able to identify and patch holes in human logic in all aspects of the system, old and new.

I feel that there is an amount of hubris in saying "I understand this codebase". You may remember the highlights, but every company in the dozen I've worked for that was actually making money - the codebase was too large for anyone to know fully. A wizard with the wisdom as you so eloquently put me down with would leave. And guess what? Nothing would happen. It is only in your own mind that you are so important.


I agree, understanding the code does not save us. Knight Capital wrote every line of their code but it didn’t prevent a $440 million loss in under an hour [0].

Regarding wisdom, I do not mean knowledge of how the system works. That is a thing, too, where the person who built it is the only one who understands it. That’s not what I meant here.

In the examples of my coworkers, for example, I see at least two things:

1. The things they create are 90% well crafted, 30% well engineered. If they were building a rocket, every part would be well machined to high precision. Then when we assemble the rocket, we find out it’s too heavy to ever get off the ground. That’s a kind of wisdom gap.

2. They work in a way that excludes everyone else on the team. From their perspective, they are wondering why everyone else isn’t getting on board. But it’s a situation where one person understands it, and their deep understanding of it contributes to them moving fast, and then add AI and now the ground is shifting faster than anyone else can understand enough to contribute. This is another kind of wisdom gap, knowing how to get a team performing at a high level, versus an individual contributor performing at a high level.

This is where, from your perspective, you’re driving a speed boat as fast as you can, wondering why your coworkers aren’t on board. But from their perspective, they’re following your boat in their boats, but your boat is creating waves behind it and splashing water up, so their experience is a bumpy ride getting water splashed in their face constantly while they’re yelling “hey can you slow down up there?” From your perspective, it makes no sense to slow down. You’re not experiencing any problems. Yet both perspectives are still true.

The person who is charging forward as fast as possible also seems to be the one who has less experience operating and supporting systems, understanding how systems fail in unexpected ways, and so forth. Every week I have a conversation where someone tells me, “oh, I didn’t consider it might fail in that way”, and every time I think, yeah it would have been really nice if we’d had a 20 minute conversation 6 weeks ago when you started.

In general, it’s not that “other people just haven’t figured out the tools yet”, it’s also a significant part of who’s leading each initiative. I could absolutely do what my coworker does and setup my custom harness to pull off amazing stunts of productivity. I just think it’s irresponsible much of the time.

[0] https://en.wikipedia.org/wiki/Knight_Capital_Group


I think you may be considering this through the lens of how I am mistaken and frankly wrong.

What if I'm not deluded and self aggrandized and AI pilled. What if I'm right? What if I am offering solid pointed and poignant advice?

I'm not going to string together any amount of words in a response to make you believe that so you'll have to do it yourself.

What if what I'm saying is accurate and correct?


> What if I am offering solid pointed and poignant advice?

I’d love to be wrong here. I didn’t see where you gave any advice though. I only saw you say you’re doing really well. What’s your advice?


An actual photo you took is not AI-generated though.

Where’s the line? If you take a selfie in Times Square, and there’s an AI-generated image in an ad behind you, that photo you took isn’t AI-generated.


There is an image showing literally your case, it highlights the AI generated image in a portrait on the wall

There are many alternatives.


> Maybe even enough to cause debris problems

Too late

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


> They would be insane to risk the integrity of their IPs

https://en.wikipedia.org/wiki/Batman_vs._Teenage_Mutant_Ninj...


We can hope


Let’s replace a few categories of your argument and see how your logic holds up.

”This is not the claim. The claim is that, empirically, many (or enough) of the men who end up in construction jobs are underage, trafficked, or psychologically coerced (due to poverty, drug addiction, abuse, etc) such that the choice is not really the free choice of willing participant.

I am all for individual freedoms, but I've read enough about this issue, and seen enough documentaries, that I think the claim is very well-founded. Of course, some construction workers are just willing adults doing something they want to do, but there are many who are not.

You could replace construction with mining or fishing or factory work. It’s pretty clear to me that outlawing fishing jobs isn’t going to solve the problem of forced labor.


> Haven't typed a line of code or read any code for over 6 months now

> I ask questions to confirm things

Oh my.

As someone who reads the code, I can tell you, asking questions to confirm things is inadequate. The models lie to me, daily.

Every day I have two experiences:

1. I’m blown away by what it can do

2. I say, ”wait, you said this, but the code shows that, so you were just going to leave that endpoint without requiring any authentication??” and I get the “you’re absolutely right, that was my mistake, and you’re right to call it out” song and dance. Daily.

It also adds all kinds of bloat to code, tests, and “documentation”. I’d say I spend ~30% of my dev time picking lines of code or documentation and asking, “why does this exist?” and “what would break if we deleted this line?” and then arguing with it and removing things.


Yeah, I agree, they are far from perfect and make a lot of mistakes.

Truth is, modern software was already quite shit and full of bugs. All major apps had bugs, issues, going down, etc, so users did get used to things not working. I honestly beleive AI coding nowadays, for better or worse, does things better than the average developer.

Yes, it is overly defensive and verbose, but the end result is in general ok and fully functional. Yes, it adds 30 tests and "release gates", and they are not even that useful, most of the times they just act as an extra safety mechanism to make parts of the code immutable, so release fails if the model accidentally changed things.

Another issue with looking at code, is that it's very hard to manually change things anyway. I can't just change a variable from 10 to 20, because I don't know where it is used. I have to ask the model to set that value to 20. It is quite stupid and inefficient, but this is one cost of coding using AI. But, if you do this, things will likely work.

That being said, I've mostly used Astra xhigh since it was released and things just work.


> Another issue with looking at code, is that it's very hard to manually change things anyway. I can't just change a variable from 10 to 20, because I don't know where it is used.

This should be a giant flashing red light. If you can't figure this out, either 1) you're too junior to be effective using AI, or 2) the AI is doing a truly awful job organizing the codebase. In either case, it's a sign to slow things down and understand what's happening before proceeding.


No, the problem is not the code.

Is that that variable might be used in tests, UI, docs, agenr markdown files, other related projects too.

The design spec could say "always use 10px margin", then in code we have a const with value 10 used everywhere. If we update 10 manually in code to 20, then the design spec is now outdated.


The problem remains the same. If you have to change the same value in n places, you need to know that the AI correctly updated it in those n places, so knowing what they are is prerequisite to claiming that the AI got it right.

You can't have it both ways. "The AI always does it right" and "I can't keep track of all the places where the change must be made, but the AI can" are incompatible and contradictory ideas. If you can't keep track of all the places that need to be changed, you can't check that the AI did it right.


Guidelines | FAQ | Lists | API | Security | DMCA | Apply to YC | Contact

Search: