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.
216 lines
12 KiB
216 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-24</h1>
|
||
|
|
<span class="post-date">
|
||
|
|
2020-04-24
|
||
|
|
|
||
|
|
<a href="https://blog.juliobiason.me/tags/links/">#links</a>
|
||
|
|
|
||
|
|
<a href="https://blog.juliobiason.me/tags/databases/">#databases</a>
|
||
|
|
|
||
|
|
<a href="https://blog.juliobiason.me/tags/wallpapers/">#wallpapers</a>
|
||
|
|
|
||
|
|
<a href="https://blog.juliobiason.me/tags/studio-ghibli/">#studio ghibli</a>
|
||
|
|
|
||
|
|
<a href="https://blog.juliobiason.me/tags/creative-commons/">#creative commons</a>
|
||
|
|
|
||
|
|
<a href="https://blog.juliobiason.me/tags/cc/">#cc</a>
|
||
|
|
|
||
|
|
<a href="https://blog.juliobiason.me/tags/california/">#california</a>
|
||
|
|
|
||
|
|
<a href="https://blog.juliobiason.me/tags/covid/">#covid</a>
|
||
|
|
|
||
|
|
<a href="https://blog.juliobiason.me/tags/lockdown/">#lockdown</a>
|
||
|
|
|
||
|
|
<a href="https://blog.juliobiason.me/tags/contact-tracing/">#contact tracing</a>
|
||
|
|
|
||
|
|
<a href="https://blog.juliobiason.me/tags/gact/">#gact</a>
|
||
|
|
|
||
|
|
<a href="https://blog.juliobiason.me/tags/python/">#python</a>
|
||
|
|
|
||
|
|
<a href="https://blog.juliobiason.me/tags/corotines/">#corotines</a>
|
||
|
|
|
||
|
|
<a href="https://blog.juliobiason.me/tags/facebook/">#facebook</a>
|
||
|
|
|
||
|
|
<a href="https://blog.juliobiason.me/tags/privacy/">#privacy</a>
|
||
|
|
|
||
|
|
<a href="https://blog.juliobiason.me/tags/paradox/">#paradox</a>
|
||
|
|
|
||
|
|
<a href="https://blog.juliobiason.me/tags/writing/">#writing</a>
|
||
|
|
|
||
|
|
</span>
|
||
|
|
<p>Understanding Databases, Studio Ghibli Wallpapers, Creative Commons, The Good
|
||
|
|
Side of COVID, Contact Tracing, Corotines in Python, Facebook, Privacy
|
||
|
|
Paradox, Writing.</p>
|
||
|
|
<span id="continue-reading"></span><h1 id="things-i-wished-more-developers-knew-about-databases"><a href="https://medium.com/@rakyll/things-i-wished-more-developers-knew-about-databases-2d0178464f78">Things I Wished More Developers Knew About Databases</a></h1>
|
||
|
|
<p>A very long article about the different things different databases do.
|
||
|
|
Although it doesn't focus on specific databases, a lot can be inferred from
|
||
|
|
the points.</p>
|
||
|
|
<p>... although it focus on relational databases only.</p>
|
||
|
|
<p>Another point that I could add here is that you should pick a database for
|
||
|
|
making your data <em>read ready</em>. For example, if you built some sort of response
|
||
|
|
and it basically doesn't change, it is ok to put the whole thing in a database
|
||
|
|
(in JSON format or using a key-value database instead). Putting the work of
|
||
|
|
doing sums and averages and whatnot <em>outside</em> the database can really save
|
||
|
|
your butt.</p>
|
||
|
|
<h1 id="studio-ghibli-wallpaper-for-use-in-web-conferences-etc"><a href="http://www.ghibli.jp/info/013251/">"Studio Ghibli Wallpaper" for use in web conferences, etc.</a></h1>
|
||
|
|
<p>Studio Ghibli, of "Princess Mononoke" and "My Neighbor Totoro" released a
|
||
|
|
bunch of wallpapers for people to use as background of their videoconferencing
|
||
|
|
or even computer wallpapers.</p>
|
||
|
|
<p>And it's free.</p>
|
||
|
|
<p>(This was a pain to finally find it in full: It was a toot on Mastodon, which
|
||
|
|
took me to BoingBoing, with pointed to OpenCulture, which <em>finally</em> went to
|
||
|
|
Studio Ghibli website with the images.)</p>
|
||
|
|
<h1 id="understanding-free-cultural-works"><a href="https://creativecommons.org/share-your-work/public-domain/freeworks">Understanding Free Cultural Works</a></h1>
|
||
|
|
<p>Creative Commons, known for their licenses-for-not-software (sorry, I can't
|
||
|
|
find a better description) released an article explaining the different types
|
||
|
|
of licenses they have.</p>
|
||
|
|
<p>And yes, I'm sharing this 'cause I am, again, worried about the amount of
|
||
|
|
stuff that doesn't get a proper license and may be abused.</p>
|
||
|
|
<h1 id="crashes-and-traffic-are-down-by-half-saving-state-40-million-per-day-during-shelter-in-place"><a href="https://www.ucdavis.edu/news/california-covid-19-traffic-report-finds-silver-lining/">Crashes and Traffic Are Down by Half, Saving State $40 Million Per Day During Shelter-In-Place</a></h1>
|
||
|
|
<p>While we sit on our houses, wondering when we can get out again -- some of us
|
||
|
|
wondering <em>if</em> we could get out at some point -- some things seem to be
|
||
|
|
improving outside the COVID problem.</p>
|
||
|
|
<p>After India reported <a href="https://www.msn.com/en-us/news/world/india-s-coronavirus-lockdown-is-having-a-dramatic-impact-on-pollution/ar-BB11ZmD5">dramatic reduction in
|
||
|
|
pollution</a>,
|
||
|
|
now California is reporting that, due people staying at their homes, the
|
||
|
|
number of traffic accidents reduced the costs taking injuries, damages and
|
||
|
|
deaths.</p>
|
||
|
|
<p>Not that we should raise a statue to COVID, but at least some good things are
|
||
|
|
coming out of this lockdown. Let's hope we can make these results permanent in
|
||
|
|
the end.</p>
|
||
|
|
<h1 id="google-apple-contact-tracing-gact-a-wolf-in-sheep-s-clothes"><a href="https://blog.xot.nl/2020/04/19/google-apple-contact-tracing-gact-a-wolf-in-sheeps-clothes/">Google Apple Contact Tracing (GACT): a wolf in sheep’s clothes.</a></h1>
|
||
|
|
<p>Contact Tracing is one of those things that look good in theory, but when
|
||
|
|
confronted with the challenges of privacy, doesn't seem so great.</p>
|
||
|
|
<p>The idea behind Contact Tracing is to make mobile devices talk to each other,
|
||
|
|
so in case someone finds out they got some transmittable disease, like COVID,
|
||
|
|
authorities can trace back who had contact with that person. It's good 'cause
|
||
|
|
you can alert those people earlier, preventing some huge explosion of
|
||
|
|
contamination cases around.</p>
|
||
|
|
<p>But the problem is that the owner of said mobile device can't opt out of this.
|
||
|
|
The data is not kept in a secure place -- like the person mobile device -- but
|
||
|
|
shared on the respective device company.</p>
|
||
|
|
<p>And how long till COVID is gone and this is used to trace, say, who some
|
||
|
|
journalist spoke when they got some information that puts pressure on a
|
||
|
|
government? True, I'm again jumping into the slippery slope of fallacies, but
|
||
|
|
we need to worry about those things when mobile devices are basically part of
|
||
|
|
us: We don't recall our appointments 'cause our devices do that for us; we
|
||
|
|
don't remember our friends phones 'cause it is in the device.</p>
|
||
|
|
<h1 id="building-finite-state-machines-with-python-coroutines"><a href="https://arpitbhayani.me/blogs/fsm">Building Finite State Machines with Python Coroutines</a></h1>
|
||
|
|
<p>I found more curious that Python has corotines than the idea behind using them
|
||
|
|
for state machines.</p>
|
||
|
|
<p>The only point I see is how weird the floating <code>yield</code> appears in the code and
|
||
|
|
how non-Pythonic the corotine appears (<code>send</code>? Where that came from?)</p>
|
||
|
|
<h1 id="how-does-facebook-know-so-much-about-me"><a href="https://theprivacyissue.com/data-tracking/how-does-facebook-know-so-much">How Does Facebook Know So Much About Me?</a></h1>
|
||
|
|
<p>Dunno if it is because I cancelled my Facebook account, but I've noticed some
|
||
|
|
decline in the number of news about Facebook privacy "standards".</p>
|
||
|
|
<p>This is a short summary of what Facebook does to collect information about
|
||
|
|
you, even some without your consent -- a few weeks ago, there were some news
|
||
|
|
about a board member admitting they have "dark profiles", information about
|
||
|
|
people that do <em>not</em> have a Facebook account.</p>
|
||
|
|
<h1 id="decoding-the-privacy-paradox"><a href="https://theprivacyissue.com/privacy-and-society/decoding-privacy-paradox">Decoding the Privacy Paradox</a></h1>
|
||
|
|
<p>Knowing that our data is being captured everywhere and doing nothing to change
|
||
|
|
that is the so called "privacy paradox".</p>
|
||
|
|
<p>An interesting and sad read.</p>
|
||
|
|
<h1 id="doing-more-with-less-time-critical-skills-for-productive-programmers"><a href="https://codewithoutrules.com/2020/04/20/productivity-skills/">Doing more with less time: critical skills for productive programmers</a></h1>
|
||
|
|
<p>While this is focused on developers, one thing really hit me hard:</p>
|
||
|
|
<blockquote>
|
||
|
|
<p>Output = Productivity × Time Worked</p>
|
||
|
|
</blockquote>
|
||
|
|
<p>Why? Because a lot of things around here in Brazil -- industry, specially --
|
||
|
|
try to focus on increasing output by changing the "Time Worked" instead of
|
||
|
|
focusing on "Productivity", using better tools or investing in better
|
||
|
|
equipment.</p>
|
||
|
|
<p>And while it is not mentioned in the post (although it mentions the limit of
|
||
|
|
"time worked" though), we, developers, can also take a look on increasing
|
||
|
|
Productivity. The easiest way is to automate the heck of what we can: The less
|
||
|
|
time we waste on bureaucratic/repetitive actions, the more we can produce.
|
||
|
|
Some harder way is to change our current tools to something that can take less
|
||
|
|
of our time, and that's harder 'cause we believe we will "lose time" learning
|
||
|
|
something new or changing our workflows.</p>
|
||
|
|
<h1 id="on-writing-well"><a href="https://syften.com/blog/post/writing-style/">On Writing Well</a></h1>
|
||
|
|
<p>For someone like me who is constantly writing something -- either blog posts,
|
||
|
|
either translating/writing a book, or just outputting small opinions about
|
||
|
|
diverse topics, like I'm doing right now -- having a proper idea on how to
|
||
|
|
write is important.</p>
|
||
|
|
<p>And I feel like I need to share this 'cause what I put on this kind of post is
|
||
|
|
only a short amount of what I read. Most of the links I save to read later
|
||
|
|
prove to be just short pieces of opinions but some are very complex and hard
|
||
|
|
to follow due their writing style. If I get tired reading, I won't get the
|
||
|
|
point and if I don't get the point, I don't think I should reshare -- no
|
||
|
|
matter how interesting the topic at hand is.</p>
|
||
|
|
<hr />
|
||
|
|
<p>This list of links was built with the help of :</p>
|
||
|
|
<ul>
|
||
|
|
<li><a href="https://tooot.im/@boingboing">Boing Boing</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://mastodon.social/@diggity">Sean O'Brien</a></li>
|
||
|
|
</ul>
|
||
|
|
|
||
|
|
</div>
|
||
|
|
|
||
|
|
|
||
|
|
|
||
|
|
|
||
|
|
</div>
|
||
|
|
|
||
|
|
</body>
|
||
|
|
|
||
|
|
</html>
|