You can not select more than 25 topics
Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
213 lines
12 KiB
213 lines
12 KiB
11 months ago
|
<!DOCTYPE html>
|
||
|
|
<html lang="en">
|
||
|
|
<head>
|
||
|
|
<meta http-equiv="X-UA-Compatible" content="IE=edge">
|
||
|
|
<meta http-equiv="content-type" content="text/html; charset=utf-8">
|
||
|
|
|
||
|
|
<!-- Enable responsiveness on mobile devices-->
|
||
|
|
<!-- viewport-fit=cover is to support iPhone X rounded corners and notch in landscape-->
|
||
|
|
<meta name="viewport" content="width=device-width, initial-scale=1.0, maximum-scale=1, viewport-fit=cover">
|
||
|
|
|
||
|
|
<title>Julio Biason .Me 4.3</title>
|
||
|
|
|
||
|
|
<!-- CSS -->
|
||
|
|
<link rel="stylesheet" href="https://blog.juliobiason.me/print.css" media="print">
|
||
|
|
<link rel="stylesheet" href="https://blog.juliobiason.me/poole.css">
|
||
|
|
<link rel="stylesheet" href="https://blog.juliobiason.me/hyde.css">
|
||
|
|
<link rel="stylesheet" href="https://fonts.googleapis.com/css?family=PT+Sans:400,400italic,700|Abril+Fatface">
|
||
|
|
|
||
|
|
|
||
|
|
|
||
|
|
|
||
|
|
|
||
|
|
</head>
|
||
|
|
|
||
|
|
<body class=" ">
|
||
|
|
|
||
|
|
<div class="sidebar">
|
||
|
|
<div class="container sidebar-sticky">
|
||
|
|
<div class="sidebar-about">
|
||
|
|
|
||
|
|
<a href="https://blog.juliobiason.me"><h1>Julio Biason .Me 4.3</h1></a>
|
||
|
|
|
||
|
|
<p class="lead">Old school dev living in a 2.0 dev world</p>
|
||
|
|
|
||
|
|
|
||
|
|
</div>
|
||
|
|
|
||
|
|
<ul class="sidebar-nav">
|
||
|
|
|
||
|
|
|
||
|
|
<li class="sidebar-nav-item"><a href="/">English</a></li>
|
||
|
|
|
||
|
|
<li class="sidebar-nav-item"><a href="/pt">Português</a></li>
|
||
|
|
|
||
|
|
<li class="sidebar-nav-item"><a href="/tags">Tags (EN)</a></li>
|
||
|
|
|
||
|
|
<li class="sidebar-nav-item"><a href="/pt/tags">Tags (PT)</a></li>
|
||
|
|
|
||
|
|
|
||
|
|
</ul>
|
||
|
|
</div>
|
||
|
|
</div>
|
||
|
|
|
||
|
|
|
||
|
|
<div class="content container">
|
||
|
|
|
||
|
|
<div class="post">
|
||
|
|
<h1 class="post-title">Links for 2020-04-29</h1>
|
||
|
|
<span class="post-date">
|
||
|
|
2020-04-29
|
||
|
|
|
||
|
|
<a href="https://blog.juliobiason.me/tags/links/">#links</a>
|
||
|
|
|
||
|
|
<a href="https://blog.juliobiason.me/tags/python/">#python</a>
|
||
|
|
|
||
|
|
<a href="https://blog.juliobiason.me/tags/top/">#top</a>
|
||
|
|
|
||
|
|
<a href="https://blog.juliobiason.me/tags/bash/">#bash</a>
|
||
|
|
|
||
|
|
<a href="https://blog.juliobiason.me/tags/legacy/">#legacy</a>
|
||
|
|
|
||
|
|
<a href="https://blog.juliobiason.me/tags/rewrite/">#rewrite</a>
|
||
|
|
|
||
|
|
<a href="https://blog.juliobiason.me/tags/refactor/">#refactor</a>
|
||
|
|
|
||
|
|
<a href="https://blog.juliobiason.me/tags/tribes/">#tribes</a>
|
||
|
|
|
||
|
|
<a href="https://blog.juliobiason.me/tags/factory/">#factory</a>
|
||
|
|
|
||
|
|
<a href="https://blog.juliobiason.me/tags/git/">#git</a>
|
||
|
|
|
||
|
|
<a href="https://blog.juliobiason.me/tags/branches/">#branches</a>
|
||
|
|
|
||
|
|
<a href="https://blog.juliobiason.me/tags/trim/">#trim</a>
|
||
|
|
|
||
|
|
<a href="https://blog.juliobiason.me/tags/dairy/">#dairy</a>
|
||
|
|
|
||
|
|
<a href="https://blog.juliobiason.me/tags/journal/">#journal</a>
|
||
|
|
|
||
|
|
<a href="https://blog.juliobiason.me/tags/programming/">#programming</a>
|
||
|
|
|
||
|
|
<a href="https://blog.juliobiason.me/tags/caches/">#caches</a>
|
||
|
|
|
||
|
|
<a href="https://blog.juliobiason.me/tags/gnome/">#gnome</a>
|
||
|
|
|
||
|
|
<a href="https://blog.juliobiason.me/tags/screen-recording/">#screen recording</a>
|
||
|
|
|
||
|
|
<a href="https://blog.juliobiason.me/tags/requirements/">#requirements</a>
|
||
|
|
|
||
|
|
<a href="https://blog.juliobiason.me/tags/vim/">#vim</a>
|
||
|
|
|
||
|
|
<a href="https://blog.juliobiason.me/tags/password-manager/">#password manager</a>
|
||
|
|
|
||
|
|
<a href="https://blog.juliobiason.me/tags/google/">#google</a>
|
||
|
|
|
||
|
|
<a href="https://blog.juliobiason.me/tags/adsense/">#adsense</a>
|
||
|
|
|
||
|
|
</span>
|
||
|
|
<p>Python 3.9, A Nice Top in Pure Bash, Rewriting a Legacy System, Programming
|
||
|
|
Tribes, Feature Factory, Python Function Overload, Clean Git Branches,
|
||
|
|
Journaling for Devs, What Programming Is, Caches, GNOME Screen Recording,
|
||
|
|
Requirements, VIM Password Manager, Google AdSense Ransom.</p>
|
||
|
|
<span id="continue-reading"></span><h1 id="new-features-in-python-3-9-you-should-know-about"><a href="https://martinheinz.dev/blog/21">New Features in Python 3.9 You Should Know About</a></h1>
|
||
|
|
<p>The great feature coming in Python 3.9 is the dictionary shortcut (<code>|</code>, as in
|
||
|
|
<code>new_dict = dict1 | dict2</code>), but there are few more incoming changes.</p>
|
||
|
|
<p>I talked about the future of Python on <a href="https://pycaxias.org/">PyCaxias</a> this
|
||
|
|
year, and I pointed that Python grew a lot when it entered the web development
|
||
|
|
area and now that it is getting into the machine learning area, there will be
|
||
|
|
changes coming into the language to support this.</p>
|
||
|
|
<p>And if you ignore the dict operator, there is <em>a lot</em> of things related to ML.</p>
|
||
|
|
<h1 id="bashtop-linux-resource-monitor"><a href="https://github.com/aristocratos/bashtop">BashTop: Linux resource monitor</a></h1>
|
||
|
|
<p>When I first receive the link for this, I thought "I bet it looks like any
|
||
|
|
other bash script". But no, it has a well designed interface and loops
|
||
|
|
interesting as heck.</p>
|
||
|
|
<h1 id="avoid-rewriting-a-legacy-system-from-scratch-by-strangling-it"><a href="https://understandlegacycode.com/blog/avoid-rewriting-a-legacy-system-from-scratch-by-strangling-it/">Avoid rewriting a legacy system from scratch, by strangling it</a></h1>
|
||
|
|
<p>So you don't know how to replace your monolith with another monolith? Here is
|
||
|
|
one idea: Create the same API, put a gateway in front of the old system and
|
||
|
|
slowly reroute calls to the new service.</p>
|
||
|
|
<h1 id="3-tribes-of-programming"><a href="https://josephg.com/blog/3-tribes/">3 tribes of programming</a></h1>
|
||
|
|
<p>It's kinda funny seeing articles that try to pinpoint developers in certain
|
||
|
|
categories and end up just splitting everyone.</p>
|
||
|
|
<p>But this one kinda makes sense, if you're willing to put a random label on
|
||
|
|
yourself.</p>
|
||
|
|
<h1 id="12-signs-you-re-working-in-a-feature-factory"><a href="https://cutle.fish/blog/12-signs-youre-working-in-a-feature-factory">12 Signs You’re Working in a Feature Factory</a></h1>
|
||
|
|
<p>Ah, the good old ways of just pushing buttons and pumping features, with no
|
||
|
|
regard to process or anything else.</p>
|
||
|
|
<p>If you're starting your dev career, at some point you'll work in one of those,
|
||
|
|
and recognizing you're in such situation may help your future.</p>
|
||
|
|
<h1 id="function-overloading-in-python"><a href="https://arpitbhayani.me/blogs/function-overloading">Function overloading in Python</a></h1>
|
||
|
|
<p>Ah, the joys of using decorators to add features to the language. In this
|
||
|
|
case, using decorators, you can add function overloading to Python, and even
|
||
|
|
if it is based on the number of arguments, one could extend this to use the
|
||
|
|
type hints for figuring out the function (with some work, I reckon).</p>
|
||
|
|
<h1 id="git-trim-automatically-trims-your-branches-whose-tracking-remote-refs-are-merged-or-gone"><a href="https://github.com/foriequal0/git-trim">git-trim: Automatically trims your branches whose tracking remote refs are merged or gone</a></h1>
|
||
|
|
<p>Keeping your GIT branches clean is good for your health. Removing those stupid
|
||
|
|
"fix-this" and "fix-that" after they were merged, but not removing "develop"
|
||
|
|
and "master" can be hard work.</p>
|
||
|
|
<p>This small app helps keeping everything nice and tidy.</p>
|
||
|
|
<h1 id="always-be-journaling"><a href="https://letterstoanewdeveloper.com/2018/12/14/always-be-journaling/">Always Be Journaling</a></h1>
|
||
|
|
<p>Today in "Things I Know I Should Be Doing But I Don't": Journaling.</p>
|
||
|
|
<p>I've seen this "pattern" a few times: Take notes of everything you're doing;
|
||
|
|
take notes of problems you solve; keep notes of discussions you had. Those are
|
||
|
|
all important and can save your butt in the future.</p>
|
||
|
|
<h1 id="programming-is-not-a-goal"><a href="https://ralsina.me/weblog/posts/programming-is-not-a-goal.html">Programming is not a goal.</a></h1>
|
||
|
|
<p>I was kinda expecting the "Programming is not a goal, providing value for your
|
||
|
|
customers is", but this is way more direct than you can think. It's the clear
|
||
|
|
suggestion for those who are starting to focus on solving their own problems
|
||
|
|
instead of just coding.</p>
|
||
|
|
<p>Figuring out how to scrap a website is ok, but what will you do with the data.
|
||
|
|
Building a neural network may be used in your CV when you're looking for that
|
||
|
|
high-paying job, but you're going to train to fix <em>what</em>?</p>
|
||
|
|
<h1 id="what-is-cache-penetration-cache-breakdown-and-cache-avalanche"><a href="https://www.pixelstech.net/article/1586522853-What-is-cache-penetration-cache-breakdown-and-cache-avalanche">What is cache penetration, cache breakdown and cache avalanche?</a></h1>
|
||
|
|
<p>I suck at using the "proper" words for some contexts: I used a bunch of
|
||
|
|
patterns, but heck if I can remember (or even if I really know) their proper
|
||
|
|
names.</p>
|
||
|
|
<p>This is the same thing: Just some clarification on how to call some
|
||
|
|
problems/situations with caches.</p>
|
||
|
|
<h1 id="gnome-has-a-secret-screen-recorder-here-s-how-to-use-it"><a href="https://itsfoss.com/gnome-screen-recorder/">GNOME has a ‘Secret’ Screen Recorder. Here’s How to Use it!</a></h1>
|
||
|
|
<p>This is a cool thing: You can record your desktop if you're using GNOME. The
|
||
|
|
recording will appear as a <code>webm</code> in your "Videos" folder.</p>
|
||
|
|
<h1 id="requirements-volatility-is-the-core-problem-of-software-engineering"><a href="https://stackoverflow.blog/2020/02/20/requirements-volatility-is-the-core-problem-of-software-engineering/">Requirements volatility is the core problem of software engineering</a></h1>
|
||
|
|
<p>This should not come as a surprise to anyone who was part any moderately large
|
||
|
|
project: things change.</p>
|
||
|
|
<p>Yes, agile is a way to solve this, but we need to teach developers to "let go"
|
||
|
|
of their code. We write code expecting it to live forever, and then the
|
||
|
|
requirements change and we hung up on those little grouped words and instead
|
||
|
|
of removing and starting with a fresh view, we try to twists and push things
|
||
|
|
around till it works, but is barely recognizable.</p>
|
||
|
|
<p>This part agile doesn't teach us.</p>
|
||
|
|
<h1 id="using-vim-as-a-password-manager"><a href="https://invert.svbtle.com/using-vim-as-a-password-manager">Using Vim as a password manager</a></h1>
|
||
|
|
<p>A little stupid trick using VIM: VIM can encrypt files when saving them, so
|
||
|
|
you can pick a file, put your passwords, and save it in encrypted form.</p>
|
||
|
|
<h1 id="pay-up-or-we-ll-make-google-ban-your-ads"><a href="https://krebsonsecurity.com/2020/02/pay-up-or-well-make-google-ban-your-ads/">Pay Up, Or We’ll Make Google Ban Your Ads</a></h1>
|
||
|
|
<p>Not only we have the problem with Google acting the way it wants with its
|
||
|
|
products -- and as much as we don't like it, we can't deny its in their own
|
||
|
|
right to do so -- now people have to worry about people tricking Google into
|
||
|
|
killing your... revenue.</p>
|
||
|
|
<p>And I think that's one of the basis of the whole problem with privacy and the
|
||
|
|
general use of Google products: revenue. Imagine how scared someone could be
|
||
|
|
if they decide to pay U$ 5000 just to not kill their revenue.</p>
|
||
|
|
<p>There has to be a better way.</p>
|
||
|
|
<hr />
|
||
|
|
<p>This post was built with the help of</p>
|
||
|
|
<ul>
|
||
|
|
<li><a href="https://functional.cafe/@alois">Aloïs Cochard</a></li>
|
||
|
|
<li><a href="https://toots.benpro.fr/@benoit">Benpro</a></li>
|
||
|
|
<li><a href="https://mastodon.social/@hntooter">HN Tooter</a></li>
|
||
|
|
<li><a href="https://mastodon.social/@newsbot">newsbot</a></li>
|
||
|
|
<li><a href="https://botsin.space/@readrust">Read Rust</a></li>
|
||
|
|
<li><a href="https://social.linux.pizza/@redstarfish">Starfish</a></li>
|
||
|
|
</ul>
|
||
|
|
|
||
|
|
</div>
|
||
|
|
|
||
|
|
|
||
|
|
|
||
|
|
|
||
|
|
</div>
|
||
|
|
|
||
|
|
</body>
|
||
|
|
|
||
|
|
</html>
|