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.
210 lines
11 KiB
210 lines
11 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-05-31</h1>
|
||
|
<span class="post-date">
|
||
|
2020-05-31
|
||
|
|
||
|
<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/emacs/">#emacs</a>
|
||
|
|
||
|
<a href="https://blog.juliobiason.me/tags/post-mortems/">#post-mortems</a>
|
||
|
|
||
|
<a href="https://blog.juliobiason.me/tags/rewrites/">#rewrites</a>
|
||
|
|
||
|
<a href="https://blog.juliobiason.me/tags/copyleft/">#copyleft</a>
|
||
|
|
||
|
<a href="https://blog.juliobiason.me/tags/technical-debt/">#technical debt</a>
|
||
|
|
||
|
<a href="https://blog.juliobiason.me/tags/leading/">#leading</a>
|
||
|
|
||
|
<a href="https://blog.juliobiason.me/tags/microservices/">#microservices</a>
|
||
|
|
||
|
<a href="https://blog.juliobiason.me/tags/rust/">#rust</a>
|
||
|
|
||
|
<a href="https://blog.juliobiason.me/tags/cities/">#cities</a>
|
||
|
|
||
|
<a href="https://blog.juliobiason.me/tags/roads/">#roads</a>
|
||
|
|
||
|
<a href="https://blog.juliobiason.me/tags/stallman/">#stallman</a>
|
||
|
|
||
|
</span>
|
||
|
<p>Running Things in Python, Emacs, Everything That Can Go Wrong, Why We Believe
|
||
|
that Rewrites Go Right, Copyleft, Analogies for Technical Debt, Leading
|
||
|
Projects, Microservices in Rust, Cities as Roads, Complaining about Stallman.</p>
|
||
|
<span id="continue-reading"></span><h2 id="the-many-ways-to-pass-code-to-python-from-the-terminal"><a href="https://snarky.ca/the-many-ways-to-pass-code-to-python-from-the-terminal/">The many ways to pass code to Python from the terminal</a></h2>
|
||
|
<p>This is a curious post. Although I've been using Python for a long time,
|
||
|
some of those were completely unknowns to me -- for example, making a zip file
|
||
|
and running it directly with the interpreter.</p>
|
||
|
<h2 id="emacs-productivity-tricks-hacks"><a href="http://www.mycpu.org/emacs-productivity-setup/">Emacs - Productivity Tricks/Hacks</a></h2>
|
||
|
<p>Although I don't usually use Emacs -- I'm a Vim user myself -- I can't stop
|
||
|
myself from sharing a post about Emacs that suggests using Evil, the Vim
|
||
|
keybinds emulation mode.</p>
|
||
|
<p>And the suggestion of using Helm is something that I really need to add on my
|
||
|
Emacs configuration.</p>
|
||
|
<h2 id="postmortems"><a href="https://postmortems.info/">Postmortems</a></h2>
|
||
|
<p>A Discord place for posting things going wrong.</p>
|
||
|
<p>I've been mentioning this for a year already: Most presentations we do, when
|
||
|
we go in public, is to talk about the things the go perfecting fine -- you
|
||
|
just do a build, it will never fail; just write the code, you won't find a
|
||
|
corner case; just create something, everything will be fine -- and that's not
|
||
|
the real life.</p>
|
||
|
<p>Postmortens is a forum exactly for describing things going wrong. And there is
|
||
|
a lot more to learn from things going wrong than from perfect steps that does
|
||
|
not reflect reality.</p>
|
||
|
<h2 id="why-do-we-fall-into-the-rewrite-trap"><a href="https://www.justindfuller.com/2020/01/why-do-we-fall-into-the-rewrite-trap/">Why do we fall into the rewrite trap?</a></h2>
|
||
|
<p>Yes, everybody, at this point, heard about the "Refactor, Don't Rewrite". And
|
||
|
this is just more of that.</p>
|
||
|
<p>But there are some things that really caught my eye<sup class="footnote-reference"><a href="#1">1</a></sup>: First, "Contempt
|
||
|
Culture", the idea that something is bad because it's old and bad and the new
|
||
|
thing is good because it's new. I mentioned this on my "Things I Learnt The
|
||
|
Hard Way in 30 Years of Software Development", but "right tool for the job" is
|
||
|
mostly a way to push an agenda and the right tool is mostly the tool your team
|
||
|
knows the best.</p>
|
||
|
<p>Also, instead of just going through "Rewrite BAD!", it actually list some
|
||
|
situations when doing a rewrite is the right option -- and I won't spoil, but
|
||
|
it does seems <em>really</em> the right situation.</p>
|
||
|
<h2 id="toward-copyleft-equality-for-all"><a href="https://sfconservancy.org/blog/2020/jan/06/copyleft-equality/">Toward Copyleft Equality for All</a></h2>
|
||
|
<p>A lot of the things in this post would be just for me to repeat things I
|
||
|
pointed in other posts: Companies are using the Free Software label just as
|
||
|
marketing, working on new features and charging for it, while leaving the
|
||
|
bugfixing part to the community, for example.</p>
|
||
|
<p>Here, the thing is a bit more complex, and I'm not sure if I can have an
|
||
|
concrete opinion about what is being said. Basically, the idea of
|
||
|
"copyleft" -- using copyright to make sure the code will still be available
|
||
|
and accessible to everything -- has been been subverted with the "dual
|
||
|
licensing".</p>
|
||
|
<p>In one hand, companies should be able to let the code be available and still
|
||
|
charge for it, but the way they have been using free software seems to be only
|
||
|
as a marketing plot. "Look, it's free software!" but listen to the community,
|
||
|
let them point the destiny of the project, making sure contributing is easy,
|
||
|
nothing of that makes part of those projects.</p>
|
||
|
<h2 id="technical-debt-is-like-a-tetris-game"><a href="https://www.fluentcpp.com/2020/01/17/technical-debt-is-like-a-tetris-game/">Technical Debt Is like a Tetris Game</a></h2>
|
||
|
<p>This may be the best Technical Debt analogy I ever seen: It is a game of
|
||
|
Tetris.</p>
|
||
|
<p>In the start, everything is clear and it is simple to fit the pieces. But, if
|
||
|
you don't take the time to clear things from time to time, it will get more
|
||
|
and more chaotic till you lose.</p>
|
||
|
<p>If this isn't an explanation that everyone understands why you need to stop
|
||
|
from just piling up pieces and try to clear the field from time to time, I
|
||
|
really don't know what will.</p>
|
||
|
<h2 id="how-to-lead-a-project-as-a-software-engineer"><a href="https://blog.pragmaticengineer.com/how-to-lead-a-project-in-software-development/">How to Lead a Project - as a Software Engineer</a></h2>
|
||
|
<p>A list of things software engineers should take care when they become project
|
||
|
leaders.</p>
|
||
|
<p>I can attest that the general concept here works, 'cause that's what I did
|
||
|
when I was technical leader in projects.</p>
|
||
|
<h2 id="building-a-microservice-with-rust"><a href="https://medium.com/@diego_pacheco/building-a-microservice-with-rust-957420f196fc">Building a Microservice with Rust</a></h2>
|
||
|
<p>Ok, the fact that I love Rust may be related to me wanting to share this, but
|
||
|
you have to agree that the post is really complete, showing all the hops and
|
||
|
jumps you need to do to make a microservice in Rust.</p>
|
||
|
<h2 id="city-roads"><a href="https://anvaka.github.io/city-roads/">city roads</a></h2>
|
||
|
<p>This is a cool project: Instead of drawing a city using its geographical
|
||
|
limits, draw it using their roads.</p>
|
||
|
<h2 id="burning-the-house-that-richard-stallman-rms-built-an-open-letter-to-gnu-maintainers-who-opposed-rms"><a href="http://techrights.org/2020/05/30/open-letter-to-gnu-maintainers/">Burning the House That Richard Stallman (RMS) Built: An Open Letter to GNU Maintainers Who Opposed RMS</a></h2>
|
||
|
<p>Let's complain about those complaining?</p>
|
||
|
<p>Another one of those "Leave rms alone!" kind of posts. This time, whoever
|
||
|
works for Microsoft -- which is extremely weird for this kind of post for not
|
||
|
calling it Micro$oft -- are the real pirates and who works for Red Hat have as
|
||
|
bad character as them.</p>
|
||
|
<p>Honestly, there is no denying in the work Richard Stallman did to promote free
|
||
|
software. But, at the same time, we can't ignore that, for years, GCC got
|
||
|
stuck on its architecture 'cause any changes were denied and we can't deny
|
||
|
that this "tantrum" in improving GCC is what gave Clang the space it got --
|
||
|
just remember that Apple used GCC to build macOS and iOS binaries. And we
|
||
|
can't ignore that just one day before the pressure for rms to leave the FSF
|
||
|
reached critical levels he was still saying that there was no problem in an
|
||
|
underage girl to have a sexual relationship to an old man.</p>
|
||
|
<p>This kind of though -- "But he did lots, and can say and do whatever he
|
||
|
wants" -- it's the most pure teenage thought of no worrying about the
|
||
|
consequences. "Oh, look at the consequences in the history of Microsoft
|
||
|
against free software! But don't look on what rms is saying and how his
|
||
|
posture hurts important projects and the community, 'cause he's my friend".</p>
|
||
|
<p>The community has grown up -- not only in numbers, but also in its mental
|
||
|
age -- and now we are asking when important figures will be hold responsible
|
||
|
for whatever they say and whatever they do.</p>
|
||
|
<p>... and it is really weird for a post like this that attacks Microsoft and
|
||
|
Red Hat, but says absolutely NOTHING about what Google has been doing with the
|
||
|
term "open source".</p>
|
||
|
<hr />
|
||
|
<div class="footnote-definition" id="1"><sup class="footnote-definition-label">1</sup>
|
||
|
<p>... specially since I saw some things related to this yesterday
|
||
|
morning...</p>
|
||
|
</div>
|
||
|
<hr />
|
||
|
<p>This post was built with the help of</p>
|
||
|
<ul>
|
||
|
<li><a href="https://mastodon.social/@newsbot">newsbot</a></li>
|
||
|
<li><a href="https://mastodon.sdf.org/@EdS">Ed S</a></li>
|
||
|
<li><a href="https://mastodon.social/@hntooter">HN Tooter</a></li>
|
||
|
<li><a href="https://fosstodon.org/@codesections">codesections</a></li>
|
||
|
<li><a href="https://social.linux.pizza/@redstarfish">Starfish</a></li>
|
||
|
</ul>
|
||
|
|
||
|
</div>
|
||
|
|
||
|
|
||
|
|
||
|
|
||
|
</div>
|
||
|
|
||
|
</body>
|
||
|
|
||
|
</html>
|