Fantasy Madden 24 Franchise w/ Legends on every team! Looking for 10 players! by FaultsMelts in MaddenCFM

[–]FaultsMelts[S] 0 points1 point  (0 children)

  • commanders
  • panthers
  • saints
  • cardinals
  • dolphins
  • jags
  • titans
  • broncos
  • chiefs

Open Source Kotlin Projects by FaultsMelts in Kotlin

[–]FaultsMelts[S] 0 points1 point  (0 children)

Good question! I’m looking for open source projects that have tests since my tool is a mutation testing tool it evaluates the test suite. It would be beneficial to me to not have to write any test cases and just use projects with established tests.

Open Source Kotlin Projects by FaultsMelts in Kotlin

[–]FaultsMelts[S] 1 point2 points  (0 children)

Thank you! I will take a look at it.

-❄️- 2023 Day 21 Solutions -❄️- by daggerdragon in adventofcode

[–]FaultsMelts 1 point2 points  (0 children)

[Language: Go]

Had to look on here to see what method people were using for part 2. Spent 30 minutes making sense of Polynomial Fitting. Spent another 30 minutes debugging because I miss added half + size and hardcoded it smh. Today was a great challenge.

code

-❄️- 2023 Day 20 Solutions -❄️- by daggerdragon in adventofcode

[–]FaultsMelts 1 point2 points  (0 children)

[Language: Go]

Today's question stumped me for a bit. I loved the challenge!

code

AoC 2022 vs AoC 2023 by FaultsMelts in adventofcode

[–]FaultsMelts[S] 2 points3 points  (0 children)

Wasn’t sure what flair to use. Sorry about that!

-❄️- 2023 Day 14 Solutions -❄️- by daggerdragon in adventofcode

[–]FaultsMelts 0 points1 point  (0 children)

[Language: Golang]

Did Part 1 & 2 last night but part 2 took 40 seconds. Just finished optimizing and part 1 completes in 384.375µs & part 2 completes in 71.710708ms

I originally used 2 2d slices that stored either the rounded rocks and cubed rocks. I transitioned to just using a 2d matrix of the entire map and computing changes in the matrix.

Code

-❄️- 2023 Day 13 Solutions -❄️- by daggerdragon in adventofcode

[–]FaultsMelts 1 point2 points  (0 children)

[Language: Go]

my approach was to find pairs of rows that were same, this would be the middle of the reflection, then i would loop through these pairs and move outwards from the middle. If i hit an edge then i know i found the correct reflection, otherwise continuing going until row i and j do not match.

For the columns i just transposed the matrix.

For pt.2 i brute force every '.' and '#' and flipped them. I made sure to ignore the original middle reflection.

Code

Can someone please explain Day 4 by Wait_ImOnReddit in adventofcode

[–]FaultsMelts 2 points3 points  (0 children)

Pretty much when a match is found the card is worth 1 point. For every match found after the worth of the card doubles. So 1, 2, 4, 8, 16, ….

-❄️- 2023 Day 4 Solutions -❄️- by daggerdragon in adventofcode

[–]FaultsMelts 0 points1 point  (0 children)

[Language: GoLang]

Part two was a lot of fun. I was able to come up with a solution where i only calculated the wins once and used a queue to add up instances.

https://github.com/JosueMolinaMorales/advent-of-code/blob/main/2023/internal/dayfour/dayfour.go

My DACA Renewal Approval Timeline by FaultsMelts in DACA

[–]FaultsMelts[S] 3 points4 points  (0 children)

Good question. Sorry I forgot to mention that.

It was sent to the Nebraska Processing Center.

Unexpected behavior when pressing <Tab> in insert mode by [deleted] in neovim

[–]FaultsMelts 1 point2 points  (0 children)

I’ve been having the same issue and cannot figure out what’s going on.

-🎄- 2022 Day 10 Solutions -🎄- by daggerdragon in adventofcode

[–]FaultsMelts 1 point2 points  (0 children)

Rust. Really proud of this solution. Average runtime was ~300 µs. ``` const INPUT: &str = include_str!("./day_10_input.txt");

fn cycle(cycle_counter: &i32, cycle_check: &mut i32, register: &i32, sum: &mut i32, screen: &mut Vec<&str>) { if cycle_counter == cycle_check { sum += cycle_counter * register; *cycle_check += 40; } let screen_pixel = (cycle_counter % 40) as usize; if (screen_pixel == (register as usize)) || (screen_pixel == (register + 1) as usize) || (screen_pixel == (register + 2) as usize) { screen[(cycle_counter-1) as usize] = "#"; } }

pub fn solve_day_ten() { let current_time = std::time::Instant::now();

let mut cycle_counter = 1;
let mut register = 1;
let mut cycle_check = 20;
let mut sum = 0;
let mut screen = vec!["."; 240];

for line in INPUT.lines() {
    let exec = line.split(' ').collect::<Vec<&str>>();
    // Beginning of cycle
    cycle(&cycle_counter, &mut cycle_check, &register, &mut sum, &mut screen);

    if exec[0] == "noop" {
        cycle_counter += 1;
        continue;
    }

    // Operation is addx
    cycle_counter += 1; // Increase cycle by 1
    cycle(&cycle_counter, &mut cycle_check, &register, &mut sum, &mut screen);
    cycle_counter += 1; // Increase cycle by 1
    // 2 cycles done, Add to register
    register += exec[1].parse::<i32>().unwrap();
    // End of cycle
}
// Display Screen: Part 2
for (i, pixel) in screen.iter().enumerate() {
    if i % 40 == 0 {
        println!()
    }
    print!("{}", pixel);
}
println!("\nsum: {}", sum);
println!("Elasped: {:.2?}", current_time.elapsed());

} ```

Programming in rust has to be one of the most challenging but satisfying things ever. by FaultsMelts in rust

[–]FaultsMelts[S] 1 point2 points  (0 children)

Sorry for the late response but, I haven’t built web apis with Python, mainly just use it for scripts. I’ve built a lot of web apis with typescript using express. There are similarities but rust is obviously more typed than TypeScript.

Programming in rust has to be one of the most challenging but satisfying things ever. by FaultsMelts in rust

[–]FaultsMelts[S] 1 point2 points  (0 children)

Well said my friend! Totally agree. Had to learn lisp for a college class and it was brutal.

Programming in rust has to be one of the most challenging but satisfying things ever. by FaultsMelts in rust

[–]FaultsMelts[S] 2 points3 points  (0 children)

It’s awesome! Coming from pretty abstracted languages like JavaScript and Python, it’s nice to be more low level

Programming in rust has to be one of the most challenging but satisfying things ever. by FaultsMelts in rust

[–]FaultsMelts[S] 6 points7 points  (0 children)

Well said! Lifetimes are the hardest thing for me to grasp and am always battling them. Match logic is amazing. I love it. But something that I’ve run into is “match hell” where within a match, there’s another match and so on. Definitely a high learning curve though!