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.
148 lines
7.3 KiB
148 lines
7.3 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-20</h1>
|
||
|
|
<span class="post-date">
|
||
|
|
2020-04-20
|
||
|
|
|
||
|
|
<a href="https://blog.juliobiason.me/tags/links/">#links</a>
|
||
|
|
|
||
|
|
<a href="https://blog.juliobiason.me/tags/c/">#c</a>
|
||
|
|
|
||
|
|
<a href="https://blog.juliobiason.me/tags/csp/">#csp</a>
|
||
|
|
|
||
|
|
<a href="https://blog.juliobiason.me/tags/async/">#async</a>
|
||
|
|
|
||
|
|
<a href="https://blog.juliobiason.me/tags/django/">#django</a>
|
||
|
|
|
||
|
|
<a href="https://blog.juliobiason.me/tags/ddd/">#ddd</a>
|
||
|
|
|
||
|
|
<a href="https://blog.juliobiason.me/tags/org-mode/">#org-mode</a>
|
||
|
|
|
||
|
|
<a href="https://blog.juliobiason.me/tags/blog/">#blog</a>
|
||
|
|
|
||
|
|
<a href="https://blog.juliobiason.me/tags/optimization/">#optimization</a>
|
||
|
|
|
||
|
|
<a href="https://blog.juliobiason.me/tags/technical-specs/">#technical specs</a>
|
||
|
|
|
||
|
|
<a href="https://blog.juliobiason.me/tags/apple/">#apple</a>
|
||
|
|
|
||
|
|
<a href="https://blog.juliobiason.me/tags/amazon/">#amazon</a>
|
||
|
|
|
||
|
|
<a href="https://blog.juliobiason.me/tags/zoom/">#zoom</a>
|
||
|
|
|
||
|
|
<a href="https://blog.juliobiason.me/tags/meetings/">#meetings</a>
|
||
|
|
|
||
|
|
</span>
|
||
|
|
<p>Async C, DDD + Django, From Org-Mode to Blog, Optimizable Code, Writing
|
||
|
|
Technical Specs, Apple and Amazon, Zoom and Meetings.</p>
|
||
|
|
<span id="continue-reading"></span><h1 id="libcsp"><a href="https://libcsp.com/">Libcsp</a></h1>
|
||
|
|
<p>Yes, C is pretty bad and such, but <em>holy cow</em>, this is pretty: a library for
|
||
|
|
async function calling in C on the communicating sequential processes (CSP)
|
||
|
|
model, which is the same used by Go.</p>
|
||
|
|
<p>And, personally, the code looks <em>prettier</em> than Go.</p>
|
||
|
|
<h1 id="doing-domain-driven-design-with-django"><a href="https://slides.com/mafinarkhan/ddddd#/">Doing Domain Driven Design with Django</a></h1>
|
||
|
|
<p>Slides to a presentation about doing DDD with Django. Although it's a
|
||
|
|
presentation and, thus, this means is has to be short and not specific, but
|
||
|
|
it does a good job in explaining DDD and how does it relate (or not) to the
|
||
|
|
Django architecture.</p>
|
||
|
|
<h1 id="how-to-blog-with-emacs-org-mode"><a href="https://opensource.com/article/20/3/blog-emacs">How to blog with Emacs Org mode</a></h1>
|
||
|
|
<p>In pushing the "everything plus the kitchen sink" of Emacs features, this post
|
||
|
|
explains how to write things in Org-Mode and publish it into HTML, making it
|
||
|
|
easier for someone to write posts in Org-Mode and then publish.</p>
|
||
|
|
<p>(Hey, this blog is written in Markdown and them published in HTML, so that's
|
||
|
|
not that weird!)</p>
|
||
|
|
<h1 id="optimizable-code"><a href="https://deplinenoise.wordpress.com/2013/12/28/optimizable-code/">Optimizable Code</a></h1>
|
||
|
|
<p>The great question about optimization. Sure, not do it prematurely, but this
|
||
|
|
boils down to memory alignment. This post gives some tips about it.</p>
|
||
|
|
<h1 id="a-practical-guide-to-writing-technical-specs"><a href="https://stackoverflow.blog/2020/04/06/a-practical-guide-to-writing-technical-specs/">A practical guide to writing technical specs</a></h1>
|
||
|
|
<p>A roadmap on how to write a spec. While I don't agree with the front matter
|
||
|
|
part -- why the heck do you need to know who wrote it, when it was created and
|
||
|
|
when it was updated? -- it gives the general template for writing a spec.</p>
|
||
|
|
<h1 id="how-to-provide-test-fixtures-for-django-models-in-pytest"><a href="https://realpython.com/django-pytest-fixtures/">How to Provide Test Fixtures for Django Models in Pytest</a></h1>
|
||
|
|
<p>While I'm not a huge fan of Pytest -- unittest is there already, even if it is
|
||
|
|
that panacea of methods -- this explains pretty well how to integrate Pytest
|
||
|
|
into Django, specially since it takes the road from the original unittest, the
|
||
|
|
one you learn when reading the Django documentation, and turns into Pytest.</p>
|
||
|
|
<h1 id="apple-amazon-and-common-enemies"><a href="https://stratechery.com/2020/apple-amazon-and-common-enemies/">Apple, Amazon, and Common Enemies</a></h1>
|
||
|
|
<p>This is a point about Apple doing what every monopoly does: If it can take
|
||
|
|
something from whoever needs you, you take. But don't think this is exclusive
|
||
|
|
to Apple: Google does that, Amazon does that, and so on.</p>
|
||
|
|
<h1 id="zoom-is-not-the-problem-our-meeting-centric-workflow-is"><a href="https://blog.nuclino.com/zoom-is-not-the-problem-our-meeting-centric-workflow-is">Zoom Is Not the Problem – Our Meeting-Centric Workflow Is</a></h1>
|
||
|
|
<p>This feels, initially, another of those "shut up and let me work" kind of
|
||
|
|
posts, but once again there is the call for "async communication" -- a.k.a.
|
||
|
|
"write a doc and send an email".</p>
|
||
|
|
<p>Personally, I saw both sides of this coin: Either we have a lot of emails
|
||
|
|
floating around, which made really hard to follow everything that was going
|
||
|
|
on, or we had too many personal talks and nothing was being saved for future
|
||
|
|
reference. I believe what you really need to have things written down, even if
|
||
|
|
they are preliminary and prone to change, but you also need a direct
|
||
|
|
discussion about some points from time to time, beyond the simple daily
|
||
|
|
"Yesterday, I did this, that and that, and that's it", which does not explain
|
||
|
|
the reason for doing this, that and that.</p>
|
||
|
|
|
||
|
|
</div>
|
||
|
|
|
||
|
|
|
||
|
|
|
||
|
|
|
||
|
|
</div>
|
||
|
|
|
||
|
|
</body>
|
||
|
|
|
||
|
|
</html>
|