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.
254 lines
14 KiB
254 lines
14 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-16</h1>
|
||
|
<span class="post-date">
|
||
|
2020-05-16
|
||
|
|
||
|
<a href="https://blog.juliobiason.me/tags/links/">#links</a>
|
||
|
|
||
|
<a href="https://blog.juliobiason.me/tags/gleam/">#gleam</a>
|
||
|
|
||
|
<a href="https://blog.juliobiason.me/tags/java/">#java</a>
|
||
|
|
||
|
<a href="https://blog.juliobiason.me/tags/python/">#python</a>
|
||
|
|
||
|
<a href="https://blog.juliobiason.me/tags/code/">#code</a>
|
||
|
|
||
|
<a href="https://blog.juliobiason.me/tags/images/">#images</a>
|
||
|
|
||
|
<a href="https://blog.juliobiason.me/tags/troff/">#troff</a>
|
||
|
|
||
|
<a href="https://blog.juliobiason.me/tags/nroff/">#nroff</a>
|
||
|
|
||
|
<a href="https://blog.juliobiason.me/tags/typesetting/">#typesetting</a>
|
||
|
|
||
|
<a href="https://blog.juliobiason.me/tags/vim/">#vim</a>
|
||
|
|
||
|
<a href="https://blog.juliobiason.me/tags/documentation/">#documentation</a>
|
||
|
|
||
|
<a href="https://blog.juliobiason.me/tags/porn-industry/">#porn industry</a>
|
||
|
|
||
|
<a href="https://blog.juliobiason.me/tags/testing/">#testing</a>
|
||
|
|
||
|
<a href="https://blog.juliobiason.me/tags/covid/">#covid</a>
|
||
|
|
||
|
<a href="https://blog.juliobiason.me/tags/second-order-thinking/">#second order thinking</a>
|
||
|
|
||
|
<a href="https://blog.juliobiason.me/tags/metrodome/">#metrodome</a>
|
||
|
|
||
|
<a href="https://blog.juliobiason.me/tags/diagrams/">#diagrams</a>
|
||
|
|
||
|
<a href="https://blog.juliobiason.me/tags/react/">#react</a>
|
||
|
|
||
|
<a href="https://blog.juliobiason.me/tags/react-native/">#react native</a>
|
||
|
|
||
|
<a href="https://blog.juliobiason.me/tags/windows/">#windows</a>
|
||
|
|
||
|
<a href="https://blog.juliobiason.me/tags/macos/">#macos</a>
|
||
|
|
||
|
<a href="https://blog.juliobiason.me/tags/bytecodes/">#bytecodes</a>
|
||
|
|
||
|
<a href="https://blog.juliobiason.me/tags/secrets/">#secrets</a>
|
||
|
|
||
|
<a href="https://blog.juliobiason.me/tags/word-generator/">#word generator</a>
|
||
|
|
||
|
<a href="https://blog.juliobiason.me/tags/firebase/">#firebase</a>
|
||
|
|
||
|
<a href="https://blog.juliobiason.me/tags/privacy/">#privacy</a>
|
||
|
|
||
|
<a href="https://blog.juliobiason.me/tags/blogging/">#blogging</a>
|
||
|
|
||
|
<a href="https://blog.juliobiason.me/tags/sharring/">#sharring</a>
|
||
|
|
||
|
<a href="https://blog.juliobiason.me/tags/material-design/">#material design</a>
|
||
|
|
||
|
</span>
|
||
|
<p>Gleam, Java From a Python View, Code Images, UNIX TypeSetting Tools, History
|
||
|
of VIM, Writing Documentation, Fighting COVID with Porn, Thinking Beyond
|
||
|
Problems, A Metronome, Diagrams in Python, React Native for Windows (and Mac),
|
||
|
Secrets in Python Bytecodes, Word Generator NeuralNet, Firebase Blunders,
|
||
|
Standups, Sharing as a Dev, Material Design.</p>
|
||
|
<span id="continue-reading"></span><h2 id="gleam-v0-8-released"><a href="https://lpil.uk/blog/gleam-v0.8-released/">Gleam v0.8 released!</a></h2>
|
||
|
<p>Gleam is another language focused on the BEAM (Erlang) VM. And the new version
|
||
|
brings a lot of stuff that makes me really curious about using it in the
|
||
|
future.</p>
|
||
|
<h2 id="why-java-tales-from-a-python-convert"><a href="https://sookocheff.com/post/java/why-java/">Why Java? Tales from a Python Convert</a></h2>
|
||
|
<p>Not that I'm converted from Python to Java -- I can see I'm productive with
|
||
|
Java, but the fact is, I'm not having <em>fun</em> being productive with it. Sure, it
|
||
|
gets the job done, but it lacks something.</p>
|
||
|
<p>Even with that, I think this post brings a lot of things that are actually...
|
||
|
interesting... in recent Java releases, and does a good job in breaking that
|
||
|
feeling that Java sucks.</p>
|
||
|
<h2 id="create-and-share-beautiful-images-of-your-source-code"><a href="https://github.com/carbon-app/carbon">Create and share beautiful images of your source code</a></h2>
|
||
|
<p>I used Carbon before but I keep forgetting when I need it the most. </p>
|
||
|
<h2 id="where-vim-came-from"><a href="https://twobithistory.org/2018/08/05/where-vim-came-from.html">Where Vim Came From</a></h2>
|
||
|
<p>People believe Vim to be unfriendly, but what happens is that the lineage of
|
||
|
it comes from a long way, always improving and changing. Understanding why Vim
|
||
|
is designed the way it is is one way to understand it -- and, as anything in
|
||
|
history, to avoid repeating the same mistakes again.</p>
|
||
|
<h2 id="unix-text-formatting-using-the-ms-macros"><a href="https://www.hactrn.net/ietf/rfcgen/textms.html">UNIX Text Formatting Using the -ms Macros</a></h2>
|
||
|
<p>Yes, another post about "the tools of the ole age" -- <code>troff</code> is used to build
|
||
|
man pages -- but there is something about the simplistic approach on due the
|
||
|
typesetting that is really interesting.</p>
|
||
|
<h2 id="encouraging-a-culture-of-written-communication"><a href="https://www.mcls.io/blog/encouraging-a-culture-of-written-communication">Encouraging a Culture of Written Communication</a></h2>
|
||
|
<p>This articles pushes towards better written communication due the fact that
|
||
|
most of us are working remotely, but I have to push that this should be the
|
||
|
norm, not the exception.</p>
|
||
|
<p>Documentation can be used for a long time after a developer leaves the project
|
||
|
or the company, and keeping it up-to-date can ease the onboarding of new
|
||
|
developers. So no, it's not just because we jumped into the remote working era
|
||
|
that documentation must be a priority: It should be way before that.</p>
|
||
|
<h2 id="why-the-porn-industry-has-a-lot-to-teach-us-about-safety-in-the-covid-19-era"><a href="https://www.statnews.com/2020/05/08/porn-industry-model-for-reopening-amid-covid19/">Why the porn industry has a lot to teach us about safety in the Covid-19 era</a></h2>
|
||
|
<p>Ah, the kind of news headlines that you won't expect to see.</p>
|
||
|
<p>But the thing boils down to the fact that the porn industry had to deal with
|
||
|
HIV and now makes HIV testing a common, periodic thing. And with COVID-19, a
|
||
|
virus that has no cure (yet), and something that we'll have to learn to live
|
||
|
with, doing something similar is almost required.</p>
|
||
|
<p>Obviously, porn stars are just a small set of people compared to the general
|
||
|
population, and thus way more expensive, but we really need to start thinking
|
||
|
about this.</p>
|
||
|
<h2 id="second-order-thinking-what-smart-people-use-to-outperform"><a href="https://fs.blog/2016/04/second-order-thinking/">Second-Order Thinking: What Smart People Use to Outperform</a></h2>
|
||
|
<p>A psychological article, for a change, and something most developers can learn
|
||
|
from: Instead of focusing on the problem of "this", also thing on what the
|
||
|
issues the solution will create.</p>
|
||
|
<h2 id="metronome"><a href="https://flathub.org/apps/details/com.jvieira.tpt.Metronome">Metronome</a></h2>
|
||
|
<p>I think I saw this application running in the last year PythonBrasil, and here
|
||
|
is the link for the Flatpak of it.</p>
|
||
|
<p>It's a great tool to time stuff, and it is also nice that it is a desktop
|
||
|
application with responsive layout.</p>
|
||
|
<h2 id="diagrams"><a href="https://diagrams.mingrammer.com/">Diagrams</a></h2>
|
||
|
<p>I'm a sucker for this kind of stuff -- so much that <code>dot</code> is part of my usual
|
||
|
development tools. But writing diagrams in Python... that's a freaking awesome
|
||
|
way to do it.</p>
|
||
|
<h2 id="react-native-for-windows-macos"><a href="https://microsoft.github.io/react-native-windows/">React Native for Windows + macOS</a></h2>
|
||
|
<p>A long time ago, Microsoft promised people could write Windows applications
|
||
|
using only XML and JavaScript. That thing never happened.</p>
|
||
|
<p>Then it promised you could write UWPs (Universal Window Programs), again in
|
||
|
Javascript, that would run in any Windows platform (tablet, phone and
|
||
|
desktop). That too, never happened.</p>
|
||
|
<p>And now we have React Native for Windows and Mac. While the suspicion that
|
||
|
this may again be a bust, at least React Native has some market presence to
|
||
|
maybe make this work.</p>
|
||
|
<h2 id="finding-secrets-by-decompiling-python-bytecode-in-public-repositories"><a href="https://blog.jse.li/posts/pyc/">Finding secrets by decompiling Python bytecode in public repositories</a></h2>
|
||
|
<p>The same problem people have with compiled applications -- which can be easily
|
||
|
be extracted using <code>strings</code> -- exists with Python bytecode files.</p>
|
||
|
<h2 id="this-word-does-not-exist"><a href="https://www.thisworddoesnotexist.com/">This Word Does Not Exist</a></h2>
|
||
|
<p>After <a href="https://www.thispersondoesnotexist.com/">This Person Does Not Exist</a> and
|
||
|
<a href="https://thisfursonadoesnotexist.com/">This Fursona Does Not Exist</a>, someone
|
||
|
decided to train a neural net to make words and descriptions.</p>
|
||
|
<h2 id="report-estimated-24-000-android-apps-expose-user-data-through-firebase-blunders"><a href="https://www.comparitech.com/blog/information-security/firebase-misconfiguration-report/">Report: Estimated 24,000 Android apps expose user data through Firebase blunders</a></h2>
|
||
|
<p>Security is hard. Keeping users information from leaking is a full time job
|
||
|
and can happen no matter what database/storage you use -- the standards for
|
||
|
90% of the installs is "make it easier for developers to start working, and
|
||
|
later they can secure it" instead of the other way around it. So this is not a
|
||
|
Firebase issue at all.</p>
|
||
|
<p>The troubling bit, though is this "A December 2019 report shows that Google
|
||
|
scrubs these vulnerable database URLs from its search results. However, they
|
||
|
are still indexed by other search engines like Bing."</p>
|
||
|
<p>How the fuck assholy you have to be that you hide the wronging of people
|
||
|
using your product, just because you have, basically, the monopoly on search
|
||
|
engines? Sure, using that information may help bad actors accessing random
|
||
|
people -- people that have no direct contact with the tool besides using
|
||
|
something someone else built -- but heck, cancel the damn account till they
|
||
|
learn how to protect people data instead of just hiding the problems under the
|
||
|
hug. "But that would cause people to stop using our product!" Then your
|
||
|
product have a design problem and you should fix it.</p>
|
||
|
<p>But, again, hiding it under the hug is no solution. At all.</p>
|
||
|
<h2 id="your-daily-standups-should-be-async-here-s-why"><a href="https://www.cadencework.com/blog/async-standups.html">Your daily standups should be async. Here's why</a></h2>
|
||
|
<p>I freaking hate these kind of posts: "Here, thing does work. We should get rid
|
||
|
of it." This goes one step further and points what people are going with the
|
||
|
thing and <em>still</em> points that thing is broken. Heck, why can't we point
|
||
|
<strong>why</strong> something exists and try to teach people on how to do it properly?</p>
|
||
|
<p>Nope, complaining that it is broken is way easier.</p>
|
||
|
<h2 id="the-most-successful-developers-share-more-than-they-take"><a href="https://stackoverflow.blog/2020/05/14/the-most-successful-developers-share-more-than-they-take/">The most successful developers share more than they take</a></h2>
|
||
|
<p>"You do not really understand something unless you can explain it to your
|
||
|
grandmother. If you can't explain something to a six-year-old, you really
|
||
|
don't understand it yourself." is one of Richard Feyman's famous quotes.</p>
|
||
|
<p>I do like to post opinions on my blog. I do like to do presentations. Mostly
|
||
|
'cause, when I'm explaining, I'm learning. I may think something is worth
|
||
|
explaining and do some research on how to better explain it.</p>
|
||
|
<p>Also, sometimes I write things I learnt down so I can remember it better
|
||
|
later.</p>
|
||
|
<p>That's why some of those "Month of blogging" exist.</p>
|
||
|
<h2 id="material-design-is-a-political-choice"><a href="https://www.imaginarycloud.com/blog/material-design-is-a-political-choice/">Material Design is a political choice</a></h2>
|
||
|
<p>Ok, maybe the title is a bit too bait, but there is one point that really
|
||
|
caught my eye:</p>
|
||
|
<p>"We are representing Google, whatever that might mean."</p>
|
||
|
<p>I do have my problems with Material design -- in my opinion, its natural
|
||
|
evolution would eventually get to the interfaces we have right now, so it's
|
||
|
basically a step back -- but that really is something.</p>
|
||
|
<hr />
|
||
|
<p>This post was built with the help of</p>
|
||
|
<ul>
|
||
|
<li><a href="https://floss.social/@alcinnz">Adrian Cochrane</a></li>
|
||
|
<li><a href="https://mastodon.social/@yogthos">Dmitri</a></li>
|
||
|
<li><a href="https://mastodon.social/@hntooter">HN Tooter</a></li>
|
||
|
<li><a href="https://mastodon.social/@newsbot">newsbot</a></li>
|
||
|
</ul>
|
||
|
|
||
|
</div>
|
||
|
|
||
|
|
||
|
|
||
|
|
||
|
</div>
|
||
|
|
||
|
</body>
|
||
|
|
||
|
</html>
|