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

My opinion or the opinion of investors who trade individual stock?

Unlike Teslas, several that I've been in had a small display that showed things like current speed in the traditional position behind the steering wheel. Only having that large, center display in newer Tesla's freaks me out. I haven't driven one myself but it seems very unergonomic.

I've been in 6 or 7 between Spain and Indonesia (Uber/Grab). All of them had RGB mood lighting, enormous center displays, large digital gauge clusters, full pano sunroofs, good materials, good sound isolation from outside, and great AC. It's not a surprise the big three in the US are lobbying so hard to keep them out of the US... they'd be obliterated.

I was in Montevideo this weekend and all car service cars I rode were Chinese EVs. They all seemed great and when I had Claude look up pricing they were all very well-priced. While I myself would loe a BYD Seagull or Dolphin, the more expensive ones like the Greely EX5 looked much cooler than much more expensive cars I see on roads in the US.

I live in Punta del Este, we just bought a Geely and a BYD (both) coming from a VW ID.3.

For BYD, a Dolphin 2027 for 21K + VAT. Insane value, by extreme far the best price-perf vehicle in the country’s history. Has every single little thing you might want. For that size and price, at least.

Notably, Tesla is attempting to destabilize the local market, coming in at 30K+VAT for the Premium Model Y which is cheaper than the US, Europe and pretty much anywhere.

I still prefer BYD by far, and not supporting the “controversial fellow”.

At a 20x electricity to gas price ratio (depending on factors, but yes), EVs are key here.


It’s not half. It’s half of who voted. Due to electoral college voting in most states matters Little and turnout is low.

I think he's right in that the software factory somewhat should emerge. You shouldn't start a project by saying "well, I first should build a software factory to make this faster". Start by building the thing by directing an agent. If you find yourself writing the same thing over and over put it into a skill which you should think of and treat as a macro. When you find yourself developing clear patterns what skill gets invoked when it might be time to start a software factory which in essence puts those decisions and relevant informations behind a pretty interface.

My software factory emerged that way and for the 50-70% of simpler tasks I work on this saves me so much time and, more importantly, mental overhead.


I mean, my personal software factory was building one small project with an overtly enthusiastic and strict set of precommit checks that all must pass. Then starting every new project with "using the same precommit checks from project X"

Using Elixir, Phoenix, LiveView and Ash for everything creates a very well defined and verifiable structure for every part of the codebase with a precommit that looks like this:

  precommit: [
    "compile --warnings-as-errors", # Fail compilation if any warnings exist
    "deps.unlock --check-unused", # Fail if unused dependencies are unlocked
    "deps.audit", # Scan dependencies for known security vulnerabilities
    "cmd mix hex.audit", # Audit Hex packages for retired or vulnerable versions
    "migrations.safety", # Check database migrations for unsafe operations
    "format --check-formatted", # Verify code matches the formatter style
    "credo --strict", # Run strict static code analysis checks
    "sobelow --exit --threshold high --skip", # Fail on high-confidence security issues only
    "ash.codegen --check", # Ensure Ash generated code is up to date
    "usage_rules.sync --check", # Verify usage rules are synchronized
    "cmd bun run lint", # If there's JS beyond LiveView
    "test" # Run the full test suite
  ]
The result has been excellent consistency across my code base and the AI learns fast how it should be working. Everything comes out very readable if I want to dig into something.

For the most part, everything I ask for gets 1 shotted with this approach with typically rare minor tweaks and refinements.


Doesn't this suit a prepush hook or CI job better?

I personally want to keep my commits light & fast, so it's not an impediment to commit often. I've always found even a simple reformatter on commit can be a bit annoying. Ideally for every micro-task done I commit, even if it's messy and even if I decide to revert the work later. It becomes kind of like a reasoning trace. Only when the task is completed, must the code comply to all the necessary checks, and then it becomes a PR and CI jobs run to validate


There's a 2 part answer to this.

1. If these all took a very long time to run, it would create a case to defer to the CI. With Elixir, virtually every check you see runs maximally parallel and the entire precommit stack finishes very quickly. I use this as part of queued, local "/goal" commands because I have built up a level of trust that queuing a dozen goals and then reviewing them in the morning will be correct virtually every time.

2. Since everything finishes quickly, having it setup as a precommit check let's the agent see and correct all of the failures locally before anything goes up to the CI itself. All of these checks are duplicated at the CI layer, but it's extremely rare for anything to fail. As a bonus, the AI learns and adapts to the feedback of these checks so it's correct the first time eventually.


I guess people have different working styles.

If you commit early and often, yes this could turn annoying really fast. May be GP works with local-changes/git-index for a bit and commits when somewhat satisfied.


Same. I documented my patterns and conventions into a scaffold project +Claude docs and have been able to confidently vibe code my way to very reasonable projects. My stack is sveltekit+trpc


"The obvious strategy to manifest that would would be to pay them for what they actually do! That is remarkably easy to organise."

How? How do you set a price based on what someone does?


...a market? I can't tell if you're saying "A market, duh" or "Inconceivable! True worth is abstract and platonic and impossible to assess!"


The market doesn't pay more because we somehow discovered the person actually does more. That would only be the case if because of the discovery either more people decided to hire doormen or fewer people would be interested in becoming doormen.


Nobody is paid for effort. Unless you cut down on supply of doormen or increase demand the comp won't change.


Unless Austin is ahead Waymos currently don't go in freeways anyways because the fail more of simply stopping isn't an option there


Have you considered all the jobs in the horse keeping industry when the automobile came around?


Yeah I did consider what happened to many horses: they were sent to glue factories


The Brabham was withdrawn after one race because it sprayed debris at following cars. I the thrusters used for better cornering also might push a car being overtaken just enough to get it off track. Even for track-only this won't fly. Not to mention blasting pedestrians.


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

Search: