Updates. By Jeff Kreeftmeijer

A canoe trip in Norway in 2017. We pitched our tent on a slope, so I couldn’t sleep. Instead, I decided to keep the fire going. It didn’t really get any darker than this.

https://twitter.com/louispilfold/status/1352777015133351938

Thanks! I have some experience writing Rust,but would like to get more comfortable with it.

I came across he crash course a while back, but forgot all about it. Thanks for mentioning it, I’m probably going to go through that first, then still read the Book.

I’m quite liking how minimal Gleam’s gleam/otp/actor is. Having a single function that returns a Continue or Stop tuple clearly reveals how keeping state is just a loop in a process.

https://github.com/jeffkreeftmeijer/shine/blob/stats/src/shine/reporter.gleam

I can appreciate horror video games, although I don’t have the nerve to actually play one myself. The furthest I’ll go is watching a video of somebody else play through while I’m doing something else on my other screen. I think that counts.

Listen. I forgot to sign into Slack for an hour this morning, then did. Guess what?

“No unreads”. 😎

With the upcoming curfew, I’ll probably have more time to dive into properly learning Rust, aside from the time I’ll take at work.

Is “The Rust Programming Language” still the best book to read? Any other suggestions?

Thanks! The original idea was to have more colors left over to use for UI elements like search and diffs (which are still colored), but I haven’t really changed anything there.

I guess it’s mostly because it looks nice, and I learned I don’t really need actual highlighting. 🤔

Thanks! I think I’ll stick to this for a while. I like how this looks, and haven’t missed the colors at all. 🧛‍♂️

Turns out https://github.com/github/scripts-to-rule-them-all exists with the same ideas, but through shell scripts.

I like Makefiles to keep everything contained in a single file, but I’ll switch to suggesting to use shell scripts as described by Github to help propagate their standard.

Awesome. Reading through, this looks exactly like what I was thinking of. I’m partial to Makefiles as they keep everything in one file, but that’s implementation.

The most important thing would be to have a standard, so I’ll advocate for this. Thanks! :)

I think Grim is just about ready to be released. Use Dim? Please give Grim a shot and let me know how it looks for you. Who knows? You might even join the monochrome side.

https://github.com/jeffkreeftmeijer/vim-dim/pull/5

Ah, yes. I knew I saw this somewhere before, just thought it was using Rake tasks instead of shell scripts.

Do you also use ./script/test on CI to make sure everything runs through the same command?

Trying this. Two nice things about this make test task:

1. I don’t need to know which command runs the tests in this project. That’s an implementation detail.

2. It runs formatting checks whenever tests are run locally (as formatting errors break CI)

https://github.com/jeffkreeftmeijer/shine/blob/ad49421f27c063729c8f438d2b5ca9838ea9584e/Makefile#L1-L4

An idea: instead of listing commands in your README, provide a Makefile in your project root:

• make setup installs dependencies
• make test runs the test suite (also on CI)
• make server starts the app
• make format formats your code
• make deploy publishes releases

In general: feel free to reach out if you think I can be of help.

Shoutout to http://weeknummer.nl ❤️

Case in point.

https://twitter.com/jkreeftmeijer/status/1351863320048001027

Bwhaha, I’m literally at 4G right now.

With the upcoming curfew, now’s probably the time to get a proper internet connection at home. 🤔

I just unmuted myself to say this during our integrations team meeting:

“You need the internet to download things from the internet.” 🧠

Shine has a logo now, contributed by @wesoudshoorn. 🤩

Whenever I want to make that joke about hard problems in computer science, I’ll look up https://martinfowler.com/bliki/TwoHardThings.html and realize I should just post this instead.

https://twitter.com/pbowden/status/468855097879830528

More suggestions came in. The shortlist now; “imminent”, “queued”, “ready”. They weren’t kidding, this is a hard problem. 🤔

Thanks everyone, I think “Imminent” is the best fit so far. Thanks @stiller!

https://twitter.com/stiller/status/1351629371627470853

Alright, naming things. A test has states, like “passed”, “failed” and “skipped”. What’s should the state before the test is run be called? Any suggestions?

Right now, “upcoming” is the best I can come up with. Or “pending”, but that’s used by libraries like RSpec to describe skipped tests, so using that could be confusing.