This week has been about Rust, the sad story of time, Git flows, the Brave scam, computational notebooks and how to organise your system.
An article with a comprehensive warning against relying on timestamps for ordering. May or may not apply to your current situation but time is messy and understanding why will help prevent unpleasant events.
A pearl (of many) you will find in the article:
Jumps in time can cause problems, so services like ntpd often prefer to slow down or speed up the system clock until it gradually approaches the correct time (this is called 'slew' correction).
A very much needed article around the hype of gitflow. If you use Git, you won't regret reading it.
A service to search for availability and stability of Rust features. Similar idea but simpler of the famous caniuse for web features.
An article explaining the Brave “business model”. Some of us would call this a scam, judge by yourself.
You might also like this complementary reading.
A paper describing a field study on the current computational notebook landscape to identify pain points and improvement opportunities.
# Finding your service boundaries (video)
A talk on how to organise your system (application, service, etc). Long but clearly shows how to apply DDD thinking to your system no matter the level of abstraction.