The contracts should include a simple number "you must pay us $X each month". Then the customer can check if they can pay it.

Ah to live in a perfect world...

That doesn't mean Coca cola can solve those problems.

Stop looking. I am big foot.

I would love an app that can tell me wich of the myrad of threads a pipe connection has. Is it NPT? Is it BSP-T? Is it metric?

I expect it's protection against invasion of privacy is limited.

From my experience: fear usually inhibits creativity. Thus a FDD shop is probably not really innovative.
This may seem suitable for run of the mill work, even there I wouldn't advise FDD. All your good programmers are going to wise up and get a new job, in a company like Gazzonyx's.

Any important data should be backed up.

I spend half the winter hoping that polar vortex would come our way. Our winter sucked. It was wet and not cold enough.

We'll just use Dutch gas.

- Castiel, in Supernatural

That is just not how it works. You can't convert an athlon to a custom ASIC. The part that is the Athlon is the hardware.
To make a custom ASIC you need to make different hardware. That means making masks (cost a few million $), testing, making new masks, testing, running a batch, testing, testing testing.
With this batch size it isn't really interesting unless they need the additional speed ASICs bring.

FPGA's and CPUs are different enough that it is hard to compare the speed. For some tasks FPGA's are way faster, for most tasks CPU's are way faster.
Think of the FPGA as a hummer and the CPU as a Ferrari. Most driving is done on roads, where the Ferrari is faster. However, in rough country I would bet on the Hummer.

Converting FPGA programming to chips means you need to invest millions to produce masks. You ain't gonna do that for a few hundred if you can avoid it.
Those chips are called ASICs. They are usually faster then the FPGA. And if you need many then they are cheaper.

Assuming that list is accurate it is less than 8.3%.

That the models predict an amount of lithium with narrow error bars.
It's a really neat prediction, it just happens not to agree with the measurements.

Since the cars drive 11 mph according to TFS the bikes are the fast ones. They have to limit their speed to match the slow cars.
The pedestrians are even slower than the cars so the speed delta is bigger for bike-pedestrian accidents.
Besides, dunno about the US but here the sidewalks are often paved with 30x30 cm (1 footx1 foot) concrete tiles. Those are unsuitable for bikes because they are just not flat enough.

'Round here (NL) better bike paths do usually increase speed for cars, because a percentage of drivers start biking. Then there are less cars on the road and thus less congestion.