“🌞 Sun With Face. A yellow sun with a kind, smiling face. Not your typical smiling sun with big grin and sunglasses.” #notyourtypicalsun
Of course! See you tomorrow! 👋
rand() is your friend.” #euruko2019
“If Ruby dies, my family will die.” #euruko2019
Obligatory “I’m on a boat” update. 🚢 #euruko2019
Assuming a technical article, split up the work between building a prototype that illustrates your point and gathering the facts, and writing the story.
Keeping those steps separate keeps me from editing the first part before I’m sure where I’m heading. Related: https://twitter.com/jkreeftmeijer/status/1141768367029796864
My current article series is based around writing an example application. As an experiment, I’m writing most of the draft in ~250-word commit messages in the example repository.
To get a very rough outline for the first article, I printed the commit message bodies to a markdown file in reverse.
$ git log --reverse --pretty=format:%b > draft.md
The outline was a good starting point to write the story. It felt more efficient, as the work was split between prototyping and explaining code, and writing and editing an article. Plus, the example repository now has well-groomed commits and good explanations of all changes. 🙌
Yes! Any recommendations for something-anything-whatever-instrumental-rock-bands weekly? :)
Thursday already? That means it’s time for largely-instrumental-progressive-rock-and-math-rock-bands weekly! This week, check out Chon’s new self-titled album, which came out this month. 🎸 https://open.spotify.com/
That could have been more clear indeed. I’ll update the article to feature the finished product a bit more, thanks!
I’ll be at Euruko tomorrow with most of the AppSignal team. Let’s definitely talk more Go then. Have a good trip!
It is! The finished project, including the
State module that keeps track of the board’s state, is in the master branch of the starter app’s repository (https://github.com/
Most of the implementation here is illustrative, so I chose a 1D list to keep the code understandable. I came across your article this morning, and using tuples for the board makes a lot of sense. I’ll go over it more thoroughly while working on part 2. Thanks for reaching out!
“Look at all the things I’m not doing!”
One of these days, I’ll rename a file and remember to make sure I’m updating the renamed version instead of continuing work on the old one. Today is not that day.
Made it. Good morning, I’m off to bed. 😴
close! But this is one night, and all at once. 😅 (https://www.nachtvandevluchteling.nl/route/40-km-utrecht-amersfoort)
brb, walking 40 kilometers to get home tonight.
It sure is! However, I tend to mostly read my e-mail, Slack, Twitter, and browse the internet, so the 1GB RAM on the 6 is fine for me, I guess. Am I missing out? :)
I’m using a list with an element for each position on the board. Whenever a stone is placed, I
List.replace_at to replace the default
nil value with either
Couldn’t wait to deploy the example app for next week’s article on implementing the Go game with Phoenix LiveView. I’d love to know what you think of the implementation! #myelixirstatus
Small world indeed! I’d love to hear your thoughts on my implementation if you’d care to take a look once I get this ready to ship. :)
-jquery). And other default search filters, like
-w3schools. @duckduckgo is that something you’d consider, or is setting cookies like this too much like tracking for your taste?
My main reason to upgrade from my iPhone 6 would be the subtle clicks you get while setting a timer or alarm on newer phones, but that’s about it. 🤷♀️