Or things like aluminium smelting/electrolysis.
On crypto, if it’s green energy and there is enough of it, what’s wrong? (It’s not great, and a waste of hardware, but not as awful)
Or things like aluminium smelting/electrolysis.
On crypto, if it’s green energy and there is enough of it, what’s wrong? (It’s not great, and a waste of hardware, but not as awful)
Good for them! Theoretically that should attract industries that need a lot of electricity and everything balances out cost and demand wise.
#Rust
initially, for part two I was trying to ignore a bad pair not a bad value - read the question!
Only installed Rust on Sunday, day 1 was a mess, today was more controlled. Need to look at some of the rust solutions for std library methods I don’t know about.
very focussed on getting it to actually compile/work over making it short or nice!
`
pub mod task_2 {
pub fn task_1(input: &str) -> i32{
let mut valid_count = 0;
let reports = process_input(input);
for report in reports{
let valid = is_report_valid(report);
if valid{
valid_count += 1;
}
}
println!("Valid count: {}", valid_count);
valid_count
}
pub fn task_2(input: &str) -> i32{
let mut valid_count = 0;
let reports = process_input(input);
for report in reports{
let mut valid = is_report_valid(report.clone());
if !valid
{
for position_to_delete in 0..report.len()
{
let mut updated_report = report.clone();
updated_report.remove(position_to_delete);
valid = is_report_valid(updated_report);
if valid { break; }
}
}
if valid{
valid_count += 1;
}
}
println!("Valid count: {}", valid_count);
valid_count
}
fn is_report_valid(report:Vec<i32>) -> bool{
let mut increasing = false;
let mut decreasing = false;
let mut valid = true;
for position in 1..report.len(){
if report[position-1] > report[position]
{
decreasing = true;
}
else if report[position-1] < report[position]
{
increasing = true;
}
else
{
valid = false;
break;
}
if (report[position-1] - report[position]).abs() > 3
{
valid = false;
break;
}
if increasing && decreasing
{
valid = false;
break;
}
}
return valid;
}
pub fn process_input(input: &str) -> Vec<Vec<i32>>{
let mut reports: Vec<Vec<i32>> = Vec::new();
for report_string in input.split("\n"){
let mut report: Vec<i32> = Vec::new();
for value in report_string.split_whitespace() {
report.push(value.parse::<i32>().unwrap());
}
reports.push(report);
}
return reports;
}
}
`
Might just be that there are loads of British drivers on the grid ATM.
I have no problem with the safety ones being penalised like that, they are really lax with it most of the time.
The problem is that because the stewards change all the time their harshness keeps changing.
For the stop go - as long as everyone else gets checked and similarly penalised then it’s fine. Norris SHOULD have lifted, if even a token lift.
Nope, was flickering for a while, then they dropped it even with the debris…
Norris must be getting close to a track limit penalty by now?
They will have to examine who else didn’t lift for the yellow and give them all a 35 second penalty…
Pff. This is what happens when you fire two race directors…
Should have thrown a VSC
Punctures from the straight inc!
But by clicking it, you save other people’s attention!
Depends where you buy it I suspect?
Any chance of getting someone like Vettel to apply do you think? He would be good.
Probably fired them all
Did you read the article, they address that and how this detects that (apparently)
It does mention that they send some of these in, and sometimes they get responses back that they are fine.
That covers all of your senior engineers that end up spending more time speccing/investigating things than code.
This kind of tool is probably very useful in ‘fiefdom’ companies where middle managers refuse to fire people because then they lose a headcount, or just protect their cronies. Having a central team that cuts across the company investigating that would be a good idea.
Unfortunately in a lot of cases, I can see people being fired off that even though they are doing other work, just because management don’t understand what they do. Or worse because someone sells the tool as being flawless and they just fire anyone it picks up.
Did they then add a ‘legal fees’ line item to your maintenance invoice though?
If there was more competition they (probably) wouldn’t be doing this stuff as people would leave.
I hope someone stands against him next year…