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.
187 lines
10 KiB
187 lines
10 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-06-01</h1>
|
||
|
|
<span class="post-date">
|
||
|
|
2020-06-01
|
||
|
|
|
||
|
|
<a href="https://blog.juliobiason.me/tags/links/">#links</a>
|
||
|
|
|
||
|
|
<a href="https://blog.juliobiason.me/tags/distributed/">#distributed</a>
|
||
|
|
|
||
|
|
<a href="https://blog.juliobiason.me/tags/c/">#c</a>
|
||
|
|
|
||
|
|
<a href="https://blog.juliobiason.me/tags/rust/">#rust</a>
|
||
|
|
|
||
|
|
<a href="https://blog.juliobiason.me/tags/protection/">#protection</a>
|
||
|
|
|
||
|
|
<a href="https://blog.juliobiason.me/tags/no-code/">#no code</a>
|
||
|
|
|
||
|
|
<a href="https://blog.juliobiason.me/tags/android/">#android</a>
|
||
|
|
|
||
|
|
<a href="https://blog.juliobiason.me/tags/research/">#research</a>
|
||
|
|
|
||
|
|
<a href="https://blog.juliobiason.me/tags/blog/">#blog</a>
|
||
|
|
|
||
|
|
<a href="https://blog.juliobiason.me/tags/contact-tracing/">#contact tracing</a>
|
||
|
|
|
||
|
|
<a href="https://blog.juliobiason.me/tags/privacy/">#privacy</a>
|
||
|
|
|
||
|
|
</span>
|
||
|
|
<p>Distributed Systems, C in Rust, Protecting Projects, No Code, Android,
|
||
|
|
Research Blog, Contact Tracing and Privacy (again).</p>
|
||
|
|
<span id="continue-reading"></span><h2 id="notes-on-distributed-systems-for-young-bloods"><a href="https://www.somethingsimilar.com/2013/01/14/notes-on-distributed-systems-for-young-bloods/">Notes on Distributed Systems for Young Bloods</a></h2>
|
||
|
|
<p>A bunch of "things you need to remember when working on distributed systems",
|
||
|
|
not only for "young bloods", but also for those who are doing this for
|
||
|
|
sometime, just as a reminder.</p>
|
||
|
|
<h2 id="writing-c-library-in-rust"><a href="https://www.ultrasaurus.com/2020/01/writing-c-library-in-rust/">writing c library in rust</a></h2>
|
||
|
|
<p>One of the cool things about Rust is that you can combine Rust applications
|
||
|
|
with any other C library. But not only that, it is also possible to write code
|
||
|
|
in Rust and export it as a C interface -- and, with that, combine with any
|
||
|
|
other language that can bind with C, which are basically every language around.</p>
|
||
|
|
<h2 id="self-protecting-projects"><a href="https://amihaiemil.com/2020/01/17/self-protecting-projects.html">Self-Protecting Projects</a></h2>
|
||
|
|
<p>Projects without a CI/CD pipeline are doomed to fail.</p>
|
||
|
|
<p>That's basically the gist of the post and I'm all for it too. There are a few
|
||
|
|
missing bits, like you can have a CI/CD pipeline and not having a policy for
|
||
|
|
writing tests; but, at the same time, I reckon there is no easy way to measure
|
||
|
|
if the proper things are being tested (and no, "every single function" is not
|
||
|
|
a measure).</p>
|
||
|
|
<p>Also, the idea of making the application open tickets every time the
|
||
|
|
application crashes is cool and all, but that only works for applications that
|
||
|
|
run on your own environment -- an embedded application would have a hard time
|
||
|
|
making this.</p>
|
||
|
|
<h2 id="why-i-keep-a-research-blog"><a href="http://gregorygundersen.com/blog/2020/01/12/why-research-blog/">Why I Keep a Research Blog</a></h2>
|
||
|
|
<p>I've been thinking about this for some time: I have a list of "Things I Don't
|
||
|
|
Know", which I keep on <a href="https://joplinapp.org/">Joplin</a>. The idea is that,
|
||
|
|
when I have some time, or when I see some information related to the topic, I
|
||
|
|
can add to the note, till I finally feel confident enough to say "Ok, now I
|
||
|
|
understand this".</p>
|
||
|
|
<p>But for some time I've been writing this kind of post (the
|
||
|
|
"<a href="https://blog.juliobiason.me/tags/links/">Links</a>" ones) as a way to keep a
|
||
|
|
list of things that I feel I may need in the future. So, if I keep a list of
|
||
|
|
"maybe in the future" links, why don't I put the research topics also in this
|
||
|
|
blog? Surely, right now, it will have only the topics and no content (sorry!)
|
||
|
|
but making it available may also help someone else.</p>
|
||
|
|
<p>There is one point that one could make: If I share links, why not share links
|
||
|
|
related to those topics, and let the blog engine worry about grouping them?
|
||
|
|
The point is actually to write whatever I learnt in my own words, 'cause those
|
||
|
|
are easier to recall in the future.</p>
|
||
|
|
<p>I'm still wrangling with the idea, though. No promises.</p>
|
||
|
|
<h2 id="minnesota-is-now-using-contact-tracing-to-track-protestors-as-demonstrations-escalate"><a href="https://bgr.com/2020/05/30/minnesota-protest-contact-tracing-used-to-track-demonstrators/">Minnesota is now using contact tracing to track protestors, as demonstrations escalate</a></h2>
|
||
|
|
<p>You may recall that I've been, for a while, mentioning that contact tracing
|
||
|
|
applications may sound good to find someone that had contact with another
|
||
|
|
someone with COVID-19 (so we could alert and/or take that person to a
|
||
|
|
hospital, before it was too late for treatment), but there were serious
|
||
|
|
privacy problems with it? Well, there we go.</p>
|
||
|
|
<p>A black person was brutally killed by the police in the USA, and the community
|
||
|
|
rioted to the point that a police department was set afire -- I'm not saying
|
||
|
|
it was right or wrong, but you have to think the type of indignation that make
|
||
|
|
people set a <em>police department</em> on fire.</p>
|
||
|
|
<p>And those people who worried that they may get in contact with someone that
|
||
|
|
got infected with COVID-19 and installed any contact tracing application are
|
||
|
|
now being tracked by their association with other demonstrators.</p>
|
||
|
|
<p>And <em>that's</em> what I was talking about. There is no policy that says "this
|
||
|
|
tracing information may be <em>only</em> used for diseases and nothing else".</p>
|
||
|
|
<h2 id="the-no-code-delusion"><a href="https://www.alexhudson.com/2020/01/13/the-no-code-delusion/">The 'No Code' Delusion</a></h2>
|
||
|
|
<p>Ignoring the fact that the post talks about a movement for "creating
|
||
|
|
business rules without the need of a developer", what I found interesting is
|
||
|
|
the visual comparison of the business rule (in a diagram) and the code (a
|
||
|
|
piece of Python code). Why? Because that's exactly the way applications should
|
||
|
|
be written: There is logic and it is described in a combination of functions,
|
||
|
|
which content doesn't make part of the rule itself and there are no rules
|
||
|
|
"hidden" inside the function of a rule. There is nothing of "let me put a
|
||
|
|
regexp here to validate the email". That's not what the business rule says, so
|
||
|
|
that's not in the code. If the business rule said "You should test this,
|
||
|
|
convert to that and send this to there", that's exactly what the function
|
||
|
|
should have.</p>
|
||
|
|
<p>On the other hand, I didn't realized that diagrams require some previous
|
||
|
|
knowledge: Which symbol represents a test? Which symbol represents "white in
|
||
|
|
the screen"? And so on.</p>
|
||
|
|
<p>What I need to mention, though, is that COBOL was created for non-programmers
|
||
|
|
so they could describe business rules and run them; SQL was desgiedn so
|
||
|
|
non-programmers could describe how to retrieve and process data; BDD has
|
||
|
|
always been described as a way for non-programmers to describe how a system
|
||
|
|
should be validated.</p>
|
||
|
|
<h2 id="google-pushed-to-take-action-against-android-bloatware-by-50-organizations"><a href="https://9to5google.com/2020/01/11/android-bloatware-privacy-open-letter/#adnrb=900000">Google pushed to take action against Android bloatware by 50+ organizations</a></h2>
|
||
|
|
<p>A post from earlier this year, but there is one point that I need to bring:</p>
|
||
|
|
<p>Android is "open source", right? If it is, why doesn't those 50+ organizations
|
||
|
|
just fork it and make their own Android? Surely, in a 50+ organization group,
|
||
|
|
there should be a few developers and making them all work on that could solve
|
||
|
|
the problem, right?</p>
|
||
|
|
<p>Well, thing is, Google controls Android. You can't simply fork and hope that
|
||
|
|
you can run on your device. You can't simply make a pull request and hope it
|
||
|
|
will, one day, be part of the system.</p>
|
||
|
|
<p>"Android is opensource" is a farce. It is "source available", not "open
|
||
|
|
source" by any stretch of imagination.</p>
|
||
|
|
<hr />
|
||
|
|
<p>This post was built with the help of</p>
|
||
|
|
<ul>
|
||
|
|
<li><a href="https://mastodon.social/@hntooter">HN Tooter</a></li>
|
||
|
|
<li><a href="https://botsin.space/@readrust">Read Rust</a></li>
|
||
|
|
</ul>
|
||
|
|
|
||
|
|
</div>
|
||
|
|
|
||
|
|
|
||
|
|
|
||
|
|
|
||
|
|
</div>
|
||
|
|
|
||
|
|
</body>
|
||
|
|
|
||
|
|
</html>
|