home.social

Search

71 results for “ryguw”

  1. I made a tiny decision to become master in Python this year, instead of learning Go or Nim or Elixir. Not because of AI. Though being able to code in Python fluently does indeed open up new career opportunities. But primarily because of its maturity, versatility, and Rust/C interoperability. Still interested in any language that pushes the boundaries of developer productivity in any dimension. You’ll read more about Python here in the future, from a perspective!

  2. Managed to reduce the exec time for 2023 day 23 part 2 from 513 seconds (~8.5 mins) to a stellar 0.310 seconds. Looking back at my commits these were the biggest leaps:

    - By far the biggest leap: Shrink unique nodes to <= 64, then instead of a map simply use a `uint64` bitmask for boolean lookups (visited or not). Saves a lot of map accesses & assignments
    - Prefer `int` when doing most calculations and comparisons, seems super optimized in the Go runtime

  3. That said, running the exact squeezed single-core-optimized algorithm, but for multiple inputs on multiple cores simultaneously with 5 lines of code, feels absolutely awesome! 😎

  4. software is eating the build tools world 🦀

    and there will be more?

  5. 1) Multi-threading: by using `cpu_cores() - 1` workers as pipelines to solve sudokus, it was easy to the workload

  6. needs a simpler generics syntax. The proposal PEP 695 is already here: peps.python.org/pep-0695/ Hope it advances to the next stage this year. In the mean time, is there a transpiler like or another way to use proposed syntax for hobby projects?

  7. After doing I like to think I know quite well now… I miss ternaries. Although famous, nobody actually uses the go keyword. Pointers are fun, I missed them. Tools for testing and profiling are keys to mastering our craft. I deeply want a sound type system like that of and .

  8. Managed to reduce the exec time for 2023 day 23 part 2 from 513 seconds (~8.5 mins) to a stellar 0.310 seconds. Looking back at my commits these were the biggest leaps:

    - By far the biggest leap: Shrink unique nodes to <= 64, then instead of a map simply use a `uint64` bitmask for boolean lookups (visited or not). Saves a lot of map accesses & assignments
    - Prefer `int` when doing most calculations and comparisons, seems super optimized in the Go runtime

    #go #golang #aoc2023 #goroutines

  9. Managed to reduce the exec time for 2023 day 23 part 2 from 513 seconds (~8.5 mins) to a stellar 0.310 seconds. Looking back at my commits these were the biggest leaps:

    - By far the biggest leap: Shrink unique nodes to <= 64, then instead of a map simply use a `uint64` bitmask for boolean lookups (visited or not). Saves a lot of map accesses & assignments
    - Prefer `int` when doing most calculations and comparisons, seems super optimized in the Go runtime

    #go #golang #aoc2023 #goroutines

  10. Managed to reduce the exec time for 2023 day 23 part 2 from 513 seconds (~8.5 mins) to a stellar 0.310 seconds. Looking back at my commits these were the biggest leaps:

    - By far the biggest leap: Shrink unique nodes to <= 64, then instead of a map simply use a `uint64` bitmask for boolean lookups (visited or not). Saves a lot of map accesses & assignments
    - Prefer `int` when doing most calculations and comparisons, seems super optimized in the Go runtime

    #go #golang #aoc2023 #goroutines

  11. Managed to reduce the exec time for 2023 day 23 part 2 from 513 seconds (~8.5 mins) to a stellar 0.310 seconds. Looking back at my commits these were the biggest leaps:

    - By far the biggest leap: Shrink unique nodes to <= 64, then instead of a map simply use a `uint64` bitmask for boolean lookups (visited or not). Saves a lot of map accesses & assignments
    - Prefer `int` when doing most calculations and comparisons, seems super optimized in the Go runtime

    #go #golang #aoc2023 #goroutines

  12. That said, running the exact squeezed single-core-optimized algorithm, but for multiple inputs on multiple cores simultaneously with 5 lines of code, feels absolutely awesome! 😎

    #golang #go #goroutines #aoc2023

  13. That said, running the exact squeezed single-core-optimized algorithm, but for multiple inputs on multiple cores simultaneously with 5 lines of code, feels absolutely awesome! 😎

    #golang #go #goroutines #aoc2023

  14. That said, running the exact squeezed single-core-optimized algorithm, but for multiple inputs on multiple cores simultaneously with 5 lines of code, feels absolutely awesome! 😎

    #golang #go #goroutines #aoc2023

  15. That said, running the exact squeezed single-core-optimized algorithm, but for multiple inputs on multiple cores simultaneously with 5 lines of code, feels absolutely awesome! 😎

    #golang #go #goroutines #aoc2023

  16. After doing #AoC2023 I like to think I know #Golang quite well now… I miss ternaries. Although famous, nobody actually uses the go keyword. Pointers are fun, I missed them. Tools for testing and profiling are keys to mastering our craft. I deeply want a sound type system like that of #Rust and #TypeScript.

  17. After doing #AoC2023 I like to think I know #Golang quite well now… I miss ternaries. Although famous, nobody actually uses the go keyword. Pointers are fun, I missed them. Tools for testing and profiling are keys to mastering our craft. I deeply want a sound type system like that of #Rust and #TypeScript.

  18. After doing #AoC2023 I like to think I know #Golang quite well now… I miss ternaries. Although famous, nobody actually uses the go keyword. Pointers are fun, I missed them. Tools for testing and profiling are keys to mastering our craft. I deeply want a sound type system like that of #Rust and #TypeScript.

  19. After doing #AoC2023 I like to think I know #Golang quite well now… I miss ternaries. Although famous, nobody actually uses the go keyword. Pointers are fun, I missed them. Tools for testing and profiling are keys to mastering our craft. I deeply want a sound type system like that of #Rust and #TypeScript.

  20. [#rediffusion] Petit partage improvisé depuis mon salon : Jean-Sébastien Bach, Courante de la 2e suite youtube.com/watch?v=q3CSa_R8Guw Merci d'avance pour vos vues / likes / abonnements / partages ! #musique #musiqueClassique #classicalMusic #music #myWork #Bach #alto #viola 😍🙏🎶🎻 @music

  21. I took my 'Flow State' track—the one for focus and calm and did the opposite. It's now a liquid drum and bass remix.

    If you fancy hearing what happens when focus music gets a bit more energetic, the teaser is here. Full track coming soon.

    youtube.com/shorts/ryGwqDBEoAY

    #LiquidDnB #DrumandBass #AarDHD #FlowState #Remix #ADHDMusic