rootsofallevil
Joined 13 years ago
Joined 13 years ago
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
We're delivering confusion and thanks to LLMs we're 30% more efficient doing it
That just leaves the other 80-90% to do manually ;)
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 ¯\_(ツ)_/¯
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.
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.
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)
Is there any point in applying for a job without a good idea that they can match your salary expectations?
Solution:
1. Delete Function App
2. Deploy again
3. Profit?