In Europe we all use 220-240V. Common current ratings are between 10 and 16A (2.3kW - 4kW), hence it's practical for most people to be able to charge from a domestic socket getting around 15-30kWh overnight. However, this is not the way it is normally done.

In countries with single phase, almost everyone installs a home charger - typically on a 30-32A dedicated spur. This provides 7.2kW. In places where 3-phase 400V is common (e,g, Denmark) then you will see a lot of home charge points installed with 11kW points (16A 3-phase).

I live in the UK and the typical supply to a house is single phase 240V 100A and new build homes are increasingly coming with 400V 3-phase installation. My home has 400V 3 phase 100A (75kW) and hence I have a charging post with dual 11kW charging points.

Most importantly - this wasn't that expensive to install - the charging post was about $1,000 with the install adding about another $750 (and that's only because I needed armoured cable for the bit that ran underground).

Almost all US houses have 220-240V supplies (for dryers, stoves, etc.) - there is no need to compromise and use Level 1.

Oh look - AMD seems to have funded an open source implementation of CUDA for their competitive chips (announced on Monday). Did that lock in just disappear? I really hope that NVidia can maintain that 50% margin with competition.

The Australian ASX spent six years on this before abandoning their effort to replace the CHESS system in May of this year (https://ancillary-proxy.atarimworker.io?url=https%3A%2F%2Fwww.financemagnates.com%2Fcryptocurrency%2Fasx-abandons-blockchain-based-system-to-replace-chess%2F) I wonder what the LSE will do differently?

Really? For what tasks?

This could have been so much more. Is this what a "Principal Engineer" does these days? I kept thinking that pre-computed tables would have solved the issue better (the results being more stable and consistent) and would have been faster to implement.

An there I am replying to the wrong comment - so maybe I am stupid!

I like your passion, but you have to remember that you canâ(TM)t fix stupid.

Like many from my era... It took years to undo the damage!

East Midlands Trains has wifi, but there is a little bit of inconsistency in their network :-)

64 bytes from 216.34.181.45: icmp_seq=0 ttl=237 time=186.522 ms
64 bytes from 216.34.181.45: icmp_seq=1 ttl=237 time=382.941 ms
64 bytes from 216.34.181.45: icmp_seq=2 ttl=237 time=218.723 ms
Request timeout for icmp_seq 3
64 bytes from 216.34.181.45: icmp_seq=4 ttl=237 time=357.108 ms
64 bytes from 216.34.181.45: icmp_seq=3 ttl=237 time=1866.197 ms
Request timeout for icmp_seq 6
64 bytes from 216.34.181.45: icmp_seq=7 ttl=237 time=189.342 ms
64 bytes from 216.34.181.45: icmp_seq=5 ttl=237 time=3010.007 ms
64 bytes from 216.34.181.45: icmp_seq=8 ttl=237 time=186.937 ms
64 bytes from 216.34.181.45: icmp_seq=6 ttl=237 time=3081.013 ms
64 bytes from 216.34.181.45: icmp_seq=9 ttl=237 time=196.033 ms

Given I'm doing 100+ mph and still have Internet access I guess I'm not going to moan too much.

I agree - it's why I believe you need to focus less on knowledge of the systems you work on, and more on keeping up with current skills and methodologies.

Wow - I haven't been so wound up by a post in a long time. I'm sorry but I need to call out the BS. The development teams I run in has an average age of 40-something. They are working on modern stuff (functional programming, very high performance modern architectures). If you're good, you'll get paid (significantly) over $100K as age has absolutely nothing to do with it. At the extremes I have a brilliant 25 year old and at the other a great late 50-something. What I can tell you is that I've rejected/fired/removed lots of people - all of them based on ability and performance. And I am I working on removing the role of "project manager" from the large (1,500 person) department I (co-manage) entirely.

Funny - agile isn't new. It's actually a shift backwards 20 years getting rid of all the "buzzword-compliant critical-paradigm-shifting methodology". It's really simple at it's heart - you get close to the business, you work on the things they care about most right now and you deliver regularly (weeks rather than months or years). Back to the early 90's. Also, I didn't say remove "overhead" entirely - I only said be wary of being in a group of people who do not actually deliver anything - most especially in these rather challenging times. Management is still needed, but not the 20-40% middle management we see in so many large organizations these days.

Ever been micro-managed? How was it? That's all the theory says.

Interestingly I didn't use the word "developer" or "coder" in my post at all. I only said "worker". If you understand anything at all about what agile is all about, you would know that it requires multi-disciplinary teams that self organize. Self organization doesn't mean dis-organized - in fact I have found that agile teams are at least an order of magnitude more organized than any traditional team where the "organization" is single threaded through an overworked team lead (for example - stuck waiting for input).

Rather sadly I have the title of "chief architect" (which I despise since it means nothing) but I am most proud to be a team member (who writes at least some code every day) delivering the right value at the right time to the business I support (not serve). Thankfully, agile says nothing about architecture - it merely says you focus on the most important things and continue to adapt.

Since I am also one of the management team of 10 people who run the 1,500 person department I work within I am also fully accountable to make it deliver. It didn't deliver very well with waterfall and lots of project managers. It's doing a little better now.

I am in my late 40's and very happy working closely with some great people and a business that really appreciates what we do. This seems to be at odds with many people posting in this thread. It might not be perfect, but at least I'm enjoying myself.

Are you?

The CIO of one of the investment banks once said - in a very public forum - there are really only three roles in IT. Peon - the new guys who don't know very much yet, but should become valuable soon. Worker/do-er - those that actually create the stuff that makes the organization run. Overhead - everyone else. He then said - "be very wary of being promoted into "overhead".

This is very sage advice. There is no such thing as "grunt development work" - developers will make or break your project. Project managers are only there to support the team and to protect them from the rest of the organization.

The world is steadily moving to agile - only those delivering value to the team matter. Everyone else is "overhead". Be wary.