Linked is an article about #dokku which is software that lets you run the equivalent (more or less) of #heroku on your own server, including a server instance from a service like #digitalocean. Very nice. Good offering to remember!dokku

Linked is a quite insightful article about good vs bad refactoring. What? Isn’t refactoring always “good”? There are lots of examples of bad ones here.

Linked is a very comprehensive collection of brief explanations of numerous computer science-y data structures. I put it that way because when I think of a data structure and designing a data structure it is to represent some domain data in a way that is most convenient for the algorithm or requirements.

The linked article gets into advanced data structures seem mostly about efficiently storing, accessing, searching and updating very large collections of information. I say very large because the structures and associated algorithms are nuanced and ingenious in order to achieve efficiency when subjected to very large collections. When you need one, you really need it and it can save your application. But you won’t need most of them every day. IMHO of course.

Kinda cool. Linked is a simple tool which formats a cv in one of several styles. But the trick is that the input is a yaml file which contains all the content as a structured text file that you can edit with vscode and version track with GitHub. Nice!

Linked is an article about Zed, a new programmers editor, trying to take the place of vscode. I love articles like this because they follow the kind of crazed thought process that I often have: is there something better than what I am using now?

Linked is a neat article about sonic pi, a less known music synthesizer software. It is so cool and interesting even if you’re not a musician or composer. It builds a world of musical abstractions allowing you to make very interesting music. What is news from this article is that the whole thing is built on top of Ruby, as a DSL!

Linked is a subtle and really interesting article about static vs dynamic typing. I’ve been a fan of python type hints and annoyed with how Ruby, so far has approached the political pressure to have an answer. For the first time for me, this article articulates how type hints may be great for sample code or fairly simple real code, but can become a burden for “real” code. I’ve experienced this myself but did not realize what was going on. He also builds an interesting distinction between type checking and data validation. Maybe Ruby needs an equivalent to pedantic?

For you hardware hackers and builders out there.. linked is a very cool tool to docutment wiring in your robots and other devices as well as generate pretty pictures and even a BOM!

The attached link is an excellent, really excellent review of REST API rules of thumb and gullies.

Wow, I've heard about Nix from time to time. I still don't understand it. But the linked article is the first fairly comprehensive one with a detailed tutorial. Of course I am still too scared to try typing in the commands. They seem to claim that it will be totally isolated but still. Mainly I am not sure what benefit I will get in trying it. You can see though, that someone's have put a ton of effort into getting it to this point.

Linked is a good review of Python Flask and Django. I came from a Ruby world, that’s like comparing Sinatra to Rails. Very different and very related.

I didn’t understand Protocols in Python. Linked is an excellent tutorial that explains not just Protocols, but also contrasts them with duck typing, abstract base classes, talks about use cases and non-use cases. It’s an advanced tutorial.

I think Richard Feynman coined the term “cargo cult” in the 70’s! More important is his description of the scientific process, and his high standard and description of integrity in doing science. Computer Scientists, does your research achieve Feynman’s standard?

Linked is a deep article about type hints in Ruby. When I say deep, I mean it! Requires an in depth understanding to appreciate or follow. And it illustrates how incredibly tough it is to add a major new low level feature to Ruby or any other mature language.

Linked is an article about a feature in Ruby that I didn’t know about. I still think Ruby is superior to python in many ways. Unfortunately circumstances and “the world” and “time” has gotten me leaning more and more into python. Still when I next need to create a web based app, I can’t see using Django over rails.

Linked is an article about plotline, a python graphing package that I was not familiar with. Along the way the example shows how to take your raw data and extract from it the various series you will need building the graph. Excellent examples. But I wonder what gap this new package was filling among the multiple existing, popular and excellent graphing packages.

Linked is a comprehensive explanation of the Ruby LSP. RUBY,I had to look up what the P stood for. Actually the correct usage is either “LSP server” because LSP stands for “Language server protocol”… or just language server. Maybe the name LSP is morphing from a pure acronym to just the name of the feature, detached from the initials. Yes programmers are so pedantic, don’t you agree?

Reading well written, idiomatic code is the best way to improve your code. Linked is a nice example.

Linked is a great analysis of what might have gone wrong to cause the crowdstrike global outage of windows computers. Also software engineering and operations techniques and principles which could have avoided the terrible event.

Linked is a service that generates quite respectable short promotional videos. I tried it on the syllabus to my course and it created something fairly amazing. I mean it’s still obviously ai generated. After your amazement subsides you may still not want to use it but it’s worth checking out. Maybe if you have to generate many short videos. It’s definitely worth checking out.