HN user

bbojan

671 karma
Posts5
Comments237
View on HN

Ralph Waldo Emerson is as relevant as always: "A foolish consistency is the hobgoblin of little minds, adored by little statesmen and philosophers and divines."

the team will eventually fix the tech debt when there are not enough feature tickets to exhaust capacity

I have yet to visit this misterious universe you describe.

Thanks for the detailed info, this was the stuff I was looking for but couldn't find quickly.

> is difficult to re-process

That's not a problem. You just don't reprocess it.

There's not enough uranium in the world to last us more then a few decades if we leave 60-80 percent of it unreacted in spent fuel.

Because all masses accelerate at equal rates in a gravitational field either:

1) Inertial mass and gravitational mass are exactly equal without an explanation why

or

2) The acceleration is just an effect of a curvature of space.

Imagine two bodies thrown exactly Northward on a sphere. Although their paths are parallel they would approach each other, as if there was an acceleration. This acceleration would be the same whatever their mass is.

How do you explain airplanes that can fly with wing with symmetrical cross-section profile?

How do you explain airplanes flying upside-down?

Angle of attack is what causes lift. If you have a surface angled against the relative wind, it will produce lift.

For this portion I don't necessarily do TDD, because I remain unconvinced that writing unit tests first is inherently better than writing unit tests afterward.

I would argue that TDD doesn't imply writing unite tests - it's about writing any tests first.

If you have acceptance tests already written out, you're already doing TDD.

Another way, if you know what the code is supposed to do, why write it down in two places?

This would be like criticizing double-entry accounting by asking "if you know what the amount is, why write it down in two places?"

We write the code down in two places because that gives us advantages that far outweigh the added effort:

- Once written, your test will catch regressions forever

- A test is often excellent documentation on what the code does

- It's now much easier to refactor the code, making it more likely that it will be refactored when needed.

SpaceX ahs yet to get us some place we haven't been in space, or at the very least one we have not been to in a long time.

It got us to a place where the cost of a rocket launch is 10 times less than it was before, and soon it will get us to 100 times less. It's just a matter of time that this is leveraged to bring us to new physical places.

And equalizing SpaceX successes with Musk a person does way more than just rub me the wrong way.

He is the person that single-handedly made the decision to start a rocket company, decided on the initial architecture, hired the key people and finance the whole operation.

Same here. I always see people complaining about Python packaging, but rarely run into issues myself. Maybe it's an OS issue? I use Linux.

Some of the projects at work use gigabytes of computer vision dependencies and again I don't remember the last time I had any issues.

Could some of the people who do have issues give an example or two of the problems they run into?

At the moment, the JIT is only used if the function contains the JUMP_BACKWARD opcode which is used in the while statement but that will change in the future.

Isn't this the main reason why it's only a 2-9% improvement? Not much Python code uses the while statement in my experience.

That's not true. Starship was funded and started independently of NASA. NASA is just the first customer that is paying to develop a Moon-landing version of Starship that will be used for its Moon landing mission.