Comments URL: https://news.ycombinator.com/item?id=48121085

Points: 6

# Comments: 1

Money is a bit tight, so I decided against prusa as my first printer.

I am curious if anyone has good experiences with alternatives for the p1s with regards to ASA printing?

[1] https://news.ycombinator.com/item?id=45818562

The government is ramping up the tax rates for EVs. They will pay road tax based on their weight in a few years.

In a different way that what is proposed in this thread. We don't build a small bridge and grow it. We build small bridges, develop a theory for building bridges and use that to design the big bridge.

I don't know of any theory of computing that would help us design a "big" program at once.

Incremental makes less sense to me when you want to go to mars. Would you propose to write the software for such a mission in an incremental fashion too?

Yet for software systems it is sometimes proposed as the best way.

The Laminar profiles perform better, but only when uncontaminated (no bugs or rain). Contaminated turbulent profiles perform better than contaminated Laminar profiles. Since regulations state that you should carry fuel for the worst case scenario, it does not yet make sense to design airliners with Laminar profiles.

Naturally, manufacturers are looking for ways around this.

You can glide faster with the same L/D, so that might be worth it if you try to optimize for speed.

The minimum speed, at which the critical aoa is reached, increases. And therefore the take off and landing speeds.

Have two people sit next to each other, each with a blank piece of paper and a pen.

Have them both simultaneously write down the numbers from 1 to 1: one time in decimal, one time in roman numbers and one time as letters of the alphabet (a=1, b=2...)

One person goes about it system by system (first decimal, then Roman... ). The other goes about it number by number (1,I,A,2,II,B...)

Time them both and compare their times.

Despite all the procedures and tests, the software still managed to endanger the lives of the passengers.

There is probably a lot of long-term value in your process. Given my understanding, I would expect you to look at your employer holistically too, and realize that short term results are also valuable in their own way.

Like with yin-yang, short-term results hold within them the long term results: the money earnt enables the company to exist in the long term. Lessons learnt from delivering value can spark insight for architecture in the future.

Vice versa, the long term enables the short term. A codebase with little technical debt allows you to quickly implement changes in the short term.

I get the impression that the standard still allows hubs to exist, but that you just don't see them in practice.

I would be interested if anyone has ever used a 100mbit hub.

It appears to me that erlang does this.