Stripe has released a static gradual type system for Ruby! https://sorbet.org/blog/2019/06/20/open-sourcing-sorbet
Perhaps the moral here is to worry about a building a great runtime, and only worry about the type system if your language gains traction?
miniblog.
Super impressed to see that Monzo (a modern mobile-first UK bank) has published a detailed post-mortem of a recent outage: https://monzo.com/blog/2019/06/20/why-bank-transfers-failed-on-30th-may-2019/
Favouring interface inheritance over class inheritance, and some examples of gotchas:
Perhaps 'awesome lists' on GitHub are today's web ring?
Although the nice property of awesome lists is that anyone can contribute to them, not just the original authors of the sites.
Smalltalk takes a hardline view on syntax errors and undefined variables: you can't save a new method until it's fixed.
It's a nice way to work, as methods tend to be small, so virtually all your code is in a runnable state all the time.
Neat Emacs package of the day: git-messenger: https://github.com/syohex/emacs-git-messenger
It's a popup for git blame on the current line. Feels much lighter weight than displaying blame information on the whole file.
Factoring out observability from business logic, with a worked example:
This excellent post by @patio11 on building a personal portfolio: https://training.kalzumeus.com/newsletters/archive/do-not-end-the-week-with-nothing makes an interesting comment about GitHub. He argues that a custom website for a project is much better than just having a repo!
A discussion of trends in Wikipedia contributors and the consequences of its policy changes:
I'm regularly impressed by just how good Google Translate is.
I wonder if we'll reach a point where translation tools replace foreign language dictionaries for language learners? A dictionary might say a word has 5 meanings, but a translation tool can consider the context.
There's a threshold where it's just easier to write a patch than to file a bug. It's more likely to result in a fix, but it can be more labour intensive.
I don't know where the line is. It seems to depend on the community's interest in patches, and whether you have commit privs.
I'm not a text supremacist. I've seen fabulous GUIs for inspecting data (database explorers, morphic halos, browser tools). WYSIWYG has a ton of advantages.
Yet I can't find a rich text UI I prefer over writing markdown directly. It's less surprising.
Demographic changes on the internet, the cost of access, and the eternal September in class terms: https://kontextmaschine.tumblr.com/post/185164859368/your-granddad-on-the-internet
Here's a neat GitHub feature that I haven't noticed before: if you hover over Contributors, it shows you profile pictures of major contributors!
This picture is from https://github.com/github/semantic.
Reminds me of JS projects that generate READMEs with this visualisation.
Showing 2,056-2,070 of 7,612 posts