Dominik Wilkowski

Hey folks. Looking for an awesome front end dev for the Shopify ecosystem in Australia or New Zealand for full time employment. We have a bunch of things cooking and would love to hear from you.

www.linkedin.com/jobs/view/42...

Learning Rust By Building The Old Terminal Game Beast From 1984, Part 1 We are building the terminal game BEAST together to learn to apply Rust to a project. This is the first part in which we setup our board and learn how to move our player.

I’ve written up a tutorial I’ve given to a couple friends and colleges #teaching them #Rust and it’s been a lot of fun.

It’s 4 parts and starts here:

dominik-wilkowski.com/posts/learni...

LangGraph for complex workflows — surma.dev I may be late to the party, but LangGraph lets you build complex workflow architectures and codify them as powerful automations. Also LLMs, if you want. But you don’t have to!

📝 First blog in a long time!

I always like “flow-based” programming, and it’s a very powerful paradigm. LangGraph lets you codify complex workflows as graphs, and also integrates really well with LangChain, if your workflow is LLM-driven.

surma.dev/things/langg...

CSS Only Contrast We've always wanted it, now it looks like we can have it.

🌈 Ever wanted to get the accessible color contrast from a given color using only CSS? Well, here's how:

blog.damato.design/posts/css-on...

After 20 years of writing code and 10 years trying to quit, I did the only logical thing:

I built a website to rant about it.

Introducing SegfaultAndCoffee.com — a collection of sarcastic rants, emotional tech debt, and the kind of Rust-powered existential dread you can’t cargo fix.

Fastest way to check if a year is a leap year?

hueffner.de/falk/blog/a-...

Best part:

"I couldn't immediately find a way to prove it, so I employed the tried-and-true method of getting someone else to do it for me by posting it to the Code Golf StackExchange."

error: encountered diff marker --> crates/cli/src/main.rs:1:1 | | <<<<<<< Updated upstream | ^^^^^^^ between this marker and `=======` is the code that we're merging into | use anyhow: :Result; | ------- between this marker and `>>>>>>>` is the incoming code | >>>>>>> Stashed changes | ^^^^^^^ this marker concludes the conflict region | = note: conflict markers indicate that a merge was started but could not be completed due to merge conflicts to resolve a conflict, keep only the code you want and then delete the lines containing conflict markers = help: if you're having merge conflicts after pulling new code: the top section is the code you already had and the bottom section is the remote code if you're in the middle of a rebase: the top section is the code being rebased onto and the bottom section is the code coming from the current commit being rebased = note: for an explanation on these markers from the ‘git' documentation: visit <https://git-scm.com/book/en/v2/Git-Tools-Advanced-Merging#_checking_out_conflicts> error: could not compile ‘rscpio’ (bin "rscpio") due to 1 previous error

Fun fact \\#2137: the Rust compiler recognizes git diff markers

Back to the future cover changed to "Box <impl Future>"

A fish named Wanda poster changed to A turbo fish called Wanda

Ferris Bueller's day off changed to Ferris' Day Off

Raiders of the lost Ark changed to Raiders of the lost Arc<_>

The movie buff in me and the Rust developer in me approve.
#rustweek

Great article.

> Further, I advocate for Rust developers to document and share their mistakes in the hope that we can all learn from them.

Couldn’t agree more.

This article speaks deeply to what I think the right way is you build a “high performing team/company”. This is how you do it.

I feel seen

If anyone knows if the original author Dan Baker is still online I’d love to chat to him.

GitHub - dominikwilkowski/beast: An ASCII game built in rust in loving memory of the 1984 hit BEAST An ASCII game built in rust in loving memory of the 1984 hit BEAST - dominikwilkowski/beast

Just published BEAST. A recreation of a game I grew up with from 1984. I tried to keep it as close to the original as practical. There is a global Highscore server now too which is cool. Was a lot of fun to write this in #rust and playing it.

github.com/dominikwilko...

Fantastic post and a novel approach to something seemingly unrelated. #rust

Strengths - The three-stage approach (squish immediately, A* pathfinding, push blocks) is well-structured - Good reuse of existing A* implementation - Effective handling of block chains ("blockchains" - nice pun!)

I’m writing the pathfinding for my 2D #CLI #rust game and in there you can move multiple blocks so I added a comment:

// there is a chain of blocks (a blockchain) that can be pushed to squish the player

I think I’m pretty funny. But I just asked Claude to review my code and it came up with this.

They finally got him for Crimes Against Humanity

hackaday.com/2021/03/22/c...

And now… CipherStash Proxy! Introducing version 2 of CipherStash Proxy, our no-code data-protection solution for PostgreSQL.

cipherstash.com/blog/introdu...

This looks amazing!

Folks I’m hiring a principle eng at my company. Web stuff is important and we do a lot of #Shopify stuff but I would LOVE someone with an interest in #rust (either you’re already building it or have an interest in learning it) in Australia or New Zealand.

The work is super exciting.
DMs are open

I really like the default compiler output of VI vine.dev/docs/startin...

Anyone know if there is something like this for #rust? A cargo plugin that shows you interactions (clone, copy, other trait calls) and the memory footprint (heap, stack size)

I have been doing that and I like it. But I’d love to actually make the processor and memory real slow and make myself feel the impact of each allocation :)

Beast (video game) - Wikipedia

I’m re-building a couple 90s ASCII games in #rust right now and would love to dig into those old source codes to see how they dealt with the little memory they had.

Right now the old game called Beast from Dan Baker, Alan Brown, Mark Hamilton and Derrick Shadel

en.wikipedia.org/wiki/Beast_(...

The 90s were a golden age for efficient binaries—hardware constraints forced developers to optimize. Now, we ship layers of abstractions on top of each other.

Lately, I find myself wanting a self-imposed performance limiter, just to build leaner, more efficient software. Even for desktop apps.

This is an interesting read about the Fish shell team's experience porting fish from C++ to Rust. There's some good, some bad, but an improvement in the end.

It's also interesting to see them highlight using Rust will (hopefully) encourage more contributors

fishshell.com/blog/rustport/

Yes that’s the other sign in the garage.

A photo of a kitchen magnetic knife board with some knifes and a label that says: “kitchen use only, not for murdering”

In another episode of #engineering thoughts: >>Explicit over implicit<<

It may just safe lives.

A screenshot of the regex and settings of the design system feed. The regex are: #designsystem|designsystem|designsystems|design system|design token

Looking into this I'm not sure how to improve this... Short of adding a natural language processor. Any ideas?

Yeah the tagged isn’t very sophisticate but perhaps sometime soon.

Hey another tabber :)
Yeah o noticed those false positives too. I’ll have a look to tweak it a bit more. Keep the feedback coming. And welcome to the bluer skies.

I’m the creator of the feed and the way they work is by looking at content and analyzing it. Been busy but if you see things that are not relevant let me know and I tweak it.