/explore
|
You are here 
|
iscinumpy.dev | ||
| | | | |
codeblog.jonskeet.uk
This is a blog post I've intended to write for a very long time. (Other blog posts in that category include a recipe for tiramisu ice cream, and "knights and allies".) It's one of those things that's grown in my mind over time, becoming harder and harder to start. However, there have been three recent... |
|
| | | | | ||
| | | | |
pradyunsg.me
My response to the discussion topic posed in Python Packaging Strategy Discussion Part 1 had become quite long, so I decided to move it to write a blog post instead. This post then started absorbing various draft posts I've had on this topic since this blog was started, morphing to include my broader thoughts on where we are today. Note: I've updated this to cover an aspect of the recent LWN article on the topic as well. |
|
| | | | | ||
| | | | |
bernat.tech
The DRY principle (an acronym for don't repeat yourself) encourages software engineers to abstract code into a separate component and reuse it rather than write it over and over again. If this happens across the system, the best practice is to put it inside a package that lives on its own (a library) and then pull it in from the applications when required. As most of us can't think of every feature that the library might offer or what bugs it might contain, these packages tend to evolve. Therefore, we need some mechanism to encode these evolutions of the library, and most commonly, this is a version number. |
|
| | | | | ||
| | | | |
billyle.dev
Learn how to add Remark42, an open source comment engine with multiple auth providers, to your website without a subdomain. This tutorial will walk you through the steps and dive into the details on how to write the code and set it up on Coolify. |
|
| | | |||
