Nuclear doesn't have a great record in other countries either. I might have the wrong figures but Hinkley Points C is over 2 times over budget and likely to be 5+ years late.
The exemption being France and maybe China?
France did a programme of nuclear power stations rather than the 1 or 2 offs that seem to be the norm elsewhere and that seems to have worked pretty well.
I'd be surprised if HPC is competitive with solar + wind + BESS when it comes online but I could well be wrong
I haven't really done any c# for 5+ years. What has changed?
I remember trying to effectively reverse-engineer a codebase (code available but nobody knew how it worked) with a lot of DI and it was fairly painful.
Maybe it was possible back then and I just didn't know how ¯\_(ツ)_/¯
> I think performance under pressure is a virtue. An important job is never going to be entirely free from stress - you want somebody reliable who will take that in their stride, you don't want someone who will buckle when things get difficult.
Some people experience extraordinary high levels of stress in an interview setting. From your comment, I suspect that you are not one of them and might have trouble imagining what these levels of stress feel like.
>I wonder if tech is unique in having an implicit mistrust for everything on the resume. I've worked at several large companies where people don't even bother looking at them before interviews.
I blame the FizzBuzz blogpost (https://blog.codinghorror.com/why-cant-programmers-program/) for making everyone deathly afraid of imposters. It's a masterpiece in ego-stroking - of course you can write FizzBuzz, look at all these sorry suckers who can't. Resumes are lies, only a 45 minute brainteaser on CoderPad can reveal the truth (ignore existence of Leetcode).
While I agree with you on the whole, I have had interviewed candidates who couldn't code.
One of them basically said that they would learn (CS degree but 4 years as a PM), which was fine but not what we were looking for.
Another simply refused help and proceeded to bat their head against the brick wall of simply syntax. Didn't show signs of nervousness, panic, etc ... just seemed not to be able to code.
In short, I think they exist (programmers that can't program) but they are the exception not the rule.
>In reality if I'm considering a senior candidate from FAANG (like, actually senior, not 4 years out of school), simply talking about past experience is perfectly fine. The work is the fucking same, everyone is migrating from legacy system X to a distributed system with zookeeper and kafka, they'll fit right in. It would take a truly psychopathic liar to fake their way through all the mundane details you could ask about a project like this. And if one slips through the cracks, they'd probably make a great PM anyway. (As long as they're on your side.)
I agree with you that an interview probing the experience of the candidate by getting them to talk about what they've done seems like a far better proposition. You will get a better idea of what the candidate knows, doesn't know.
> If I'm doing something complex enough to really benefit from "everything is and object" then why not just use a more capable language like python?
I've seen this line of reasoning mentioned a lot but never justified.
A few reasons to stick with Powershell over Python:
Team might not be familiar with Python (and the benefits of learning might be outweighed by the learning curve, shallow as it might be)
Hard to judge what the cutover point is (namely at what point does a script benefit from being written in Python?)
A lot (some?) of stuff out of the box in PS requires libraries in Python, which requires installation, which cannot happen during the script (I think at least, I've not done that much Python)
>There will be false positives, but the rate is low
What do you base this on?
My experience is that if you are perceived to be good you can get away with being a low performer for a lot longer than if you are not perceived to be good, I have seen it quite a few times.
> 1) The speed limit obviously an arbitrary choice - the chance of death is decent at 50k/h (standard "town" speed limit in Slovenia) (so why not 40hm/k or 30km/h), and e.g. Germany has no speed limit on the highways (in some places) so there's really no good reason to set a limit of 130km/h (why not 110km/h or 150km/h)?
As are most limits.
I get that driving on a motorway at say 85 mph is probably not that much dangerous than the speed limit (70 mph) but 100? 120? 140?
I know about Germany, but would you say that Britain's or Slovenia's road are designed and kept to the same standard?
> 2) The easiest objection to (1) is "society has jointly decided about acceptable risk limits" but that clearly isn't true. Speed limits are simply a bad idea. A much better idea is speed constraints - roundabouts, speed bumps, chicanes [0] - i.e. actually forcing people to drive slower or else they ruin their cars.
how do you constrain speed on a motorway?
> The fact that governments default to traffic cameras etc. is proof (revealed preference) that they don't actually care about safety and people driving slowly, but what they want most is making their citizens live in fear, punishing them and extracting money from them. This is particularly obvious when there's a hidden police / traffic control on some section of the road where it's obviously safe to drive fast, but it's just technically within city limits so it has a low speed limit.
In this country (UK) there is this myth that the cameras are money making devices, when during the 2008 crisis they were turned off to save money for some constabularies, this is the same type of argument.
> Patriotism is the belief that your country is the best by virtue of you having been born in it
I can't find the original quote but I 100% agree with you that it is pretty odd to take pride in something you have an extremely tangential relationship with
Solution:
1. Delete Function App
2. Deploy again
3. Profit?