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.
214 lines
12 KiB
214 lines
12 KiB
<!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-26</h1> |
|
<span class="post-date"> |
|
2020-05-26 |
|
|
|
<a href="https://blog.juliobiason.me/tags/links/">#links</a> |
|
|
|
<a href="https://blog.juliobiason.me/tags/recutils/">#recutils</a> |
|
|
|
<a href="https://blog.juliobiason.me/tags/git/">#git</a> |
|
|
|
<a href="https://blog.juliobiason.me/tags/cobol/">#cobol</a> |
|
|
|
<a href="https://blog.juliobiason.me/tags/paying/">#paying</a> |
|
|
|
<a href="https://blog.juliobiason.me/tags/open-source/">#open source</a> |
|
|
|
<a href="https://blog.juliobiason.me/tags/free-software/">#free software</a> |
|
|
|
<a href="https://blog.juliobiason.me/tags/contributing/">#contributing</a> |
|
|
|
<a href="https://blog.juliobiason.me/tags/boring-stuff/">#boring stuff</a> |
|
|
|
<a href="https://blog.juliobiason.me/tags/accessibility/">#accessibility</a> |
|
|
|
<a href="https://blog.juliobiason.me/tags/great-code/">#great code</a> |
|
|
|
<a href="https://blog.juliobiason.me/tags/steps/">#steps</a> |
|
|
|
<a href="https://blog.juliobiason.me/tags/joel-spolsky/">#joel spolsky</a> |
|
|
|
<a href="https://blog.juliobiason.me/tags/culture-tests/">#culture tests</a> |
|
|
|
<a href="https://blog.juliobiason.me/tags/microsoft/">#microsoft</a> |
|
|
|
<a href="https://blog.juliobiason.me/tags/oil-companies/">#oil companies</a> |
|
|
|
<a href="https://blog.juliobiason.me/tags/marketing/">#marketing</a> |
|
|
|
</span> |
|
<p>GNU Recutils, Tips on Git, Simple COBOL Code, Paying for Open Source, |
|
Contributing to Open Source, Dealing With Boring Stuff, Accessibility, 12 Not |
|
So Great Steps For Great Code, Culture Tests, Microsoft Marketing.</p> |
|
<span id="continue-reading"></span><h2 id="gnu-recutils"><a href="https://labs.tomasino.org/gnu-recutils/">GNU Recutils</a></h2> |
|
<p>So you want to keep a simple database, but don't want to go through the loops |
|
and hoops of creating a script to manage it? Worry no more, the solution is |
|
here!</p> |
|
<p>Recutils is a set of tools that I wasn't aware it existed, but it keeps |
|
information in plain files, allow searching and has a schema.</p> |
|
<h2 id="5-useful-tricks-you-didn-t-know-for-git"><a href="https://densitylabs.io/blog/5-useful-tricks-you-didn't-know-for-git">5 Useful Tricks You Didn't Know for Git</a></h2> |
|
<p>While I'm not a huge fan of the short logs/changes (just "not a fan", not |
|
saying it may be useful), the <code>whatchanged</code> and the other commands are pretty |
|
damn useful.</p> |
|
<h2 id="a-basic-game-in-cobol-for-learning"><a href="https://github.com/BasiliusCarver/TicTacTOBOL">A basic "game" in COBOL for learning</a></h2> |
|
<p>Ah, the good old days of COBOL. Haha, who am I kidding, they were never good, |
|
that's all we had!</p> |
|
<p>But if you never saw a COBOL code, here is a taste of it.</p> |
|
<h2 id="paying-for-software"><a href="https://www.paritybit.ca/blog/paying-for-software">Paying for Software</a></h2> |
|
<p>We have seen this discussion going around for some time, but it's worth |
|
repeating it: In an age of large usage of free software, we must remember that |
|
companies making money with it are not helping fund said software.</p> |
|
<p>But it's also worth mentioning that not every free software needs support. |
|
Going "Open Source" is, sometimes, a marketing plot just to get visibility; |
|
I've seen companies making open source in which they <em>never</em> heard the points |
|
raised by the community itself and even just focused on new features, leaving |
|
the bugfix part to the community (and no, I'll not cite with company/software |
|
does this).</p> |
|
<h2 id="how-to-contribute-to-open-source-software"><a href="https://killalldefects.com/2020/01/26/how-to-contribute-to-open-source-software/">How to Contribute to Open Source Software</a></h2> |
|
<p>I have a presentation on the "Why and How to Contribute To Open Source |
|
Software" (it's in Portuguese, so I won't link it here), but here is a |
|
complete explanation on how to contribute with software -- and yes, there are |
|
more ways to contribute than just writing code.</p> |
|
<p>I like how very "step by step" this post describes how to do it, even if it is |
|
focused on a major service and may not reflect all open source projects (I may |
|
even "steal" some of those for my presentation).</p> |
|
<h2 id="help-i-can-t-learn-do-something-because-it-is-boring"><a href="https://letterstoanewdeveloper.com/2019/09/23/help-i-cant-learn-do-something-because-it-is-boring/">Help, I can't learn/do something because it is boring!</a></h2> |
|
<p>I've done my fair share of boring stuff -- I sadly remember when I have to go |
|
through 30+ AWS Glacier folders to restore one single file on each, with the |
|
interface not allowing me to open each folder in a new tab, so it was <em>really</em> |
|
boring: click, click, click, click, wait, click, click, click, rinse, repeat.</p> |
|
<p>But, if I could, I'd automate the heck of it, and I probably should have taken |
|
some breaks -- which was hard, considering my boss sat in front of me.</p> |
|
<h2 id="standards-for-writing-accessibly"><a href="https://alistapart.com/article/standards-for-writing-accessibly/">Standards for Writing Accessibly</a></h2> |
|
<p>Some tips on how to write interfaces in an accessible friendly mode. And while |
|
you may think "Why should I worry about accessibility when only low-percent of |
|
users have a disability?", you may also wonder how many of those have a |
|
<em>temporary</em> disability, like they just came back from their LASIK surgery, |
|
they broke their arms in a ski accident and so on. Providing accessible |
|
content for people with disabilities may also improve your interface for those |
|
people -- and they would probably be grateful that they don't need to check |
|
your competitor.</p> |
|
<h2 id="the-joel-test-12-steps-to-better-code"><a href="https://www.joelonsoftware.com/2000/08/09/the-joel-test-12-steps-to-better-code/">The Joel Test: 12 Steps to Better Code</a></h2> |
|
<p>An old post by Joel Spolsky, but it is probably worth repeating. This is a |
|
checklist of things you should do for better code. But we need here to discuss |
|
if the whole list is actually good.</p> |
|
<p>I've seen a lot of projects fail 'cause it misses something incredibly simple |
|
like specs, so devs keep running in circles, trying to figure out what |
|
actually needs to be built.</p> |
|
<p>On the other hand, some things feel out of place, in my opinion:</p> |
|
<ul> |
|
<li>Having an up-to-date schedule is good for business, but it could also blind |
|
those people from the "most viable product". In my experience, having a |
|
schedule is ok only on high level, but most of the time is makes people |
|
focus on previously though deliveries and not on what is being built.</li> |
|
<li>Having the best tools money can buy is awesome for developers that like the |
|
latest shinning thing (and hey, I do like it too), but it's not totally |
|
necessary. You can have the "most ok tools" and still be a heck |
|
productive.</li> |
|
<li>Having testers is not something I'm fond. Not that there is something wrong |
|
with tests -- quite the opposite -- but I'd prefer to have test |
|
engineer/designer than testers. Why? Because it should be the developers |
|
testing the system, building automated tests when necessary and specially |
|
'cause writing those would give more understanding of the whole.</li> |
|
<li>Having candidates to write code is bollocks; asking candidates on their |
|
thought process for solving a problem is <em>a lot</em> more effective. Sure, you |
|
could do both, but think about the time the candidate will take for |
|
writing the code, then thinking on how to improve it, while they can |
|
simply describe it for you. "But it's their time"; yes, and you're just |
|
being an asshole if you thing their time isn't worth shit.</li> |
|
</ul> |
|
<p>Honestly, when I picked the link in my feed, I though "Hey, that's a good list |
|
of things to have". But then I started writing this and noticed how broken it |
|
seems. </p> |
|
<h2 id="the-pragmatic-engineer-s-developer-culture-test"><a href="https://blog.pragmaticengineer.com/the-developer-culture-test/">The Pragmatic Engineer’s Developer Culture Test</a></h2> |
|
<p>Instead of the checklist above, I think this makes more sense, even if its |
|
results can only be verified in the long run -- and the Joel list seems more |
|
focused on the short.</p> |
|
<p>It's way more focused on the culture part of the company, what culture the |
|
company is trying to build and such -- and as someone who suffered a lot under |
|
micro-aggressions without realizing, and without <em>my boss</em> realizing, it |
|
surely stroke a never there.</p> |
|
<h2 id="while-microsoft-was-making-its-climate-pledge-it-was-sponsoring-an-oil-conference"><a href="https://www.vice.com/en_us/article/xgqypn/while-microsoft-was-making-its-climate-pledge-it-was-sponsoring-an-oil-conference">While Microsoft Was Making Its Climate Pledge, It Was Sponsoring an Oil Conference</a></h2> |
|
<p>This is from January this year, but I decided to share it 'cause it shows |
|
something a lot of companies do: "We Are The Good Guys" in marketing, "we |
|
don't actually care" in business.</p> |
|
<p>I've read some other stories like this: Promote the Pride March, but ignore |
|
harassment on LGBT+ people inside the company; say you are here to help, but |
|
close repositories and make a contract with ICE. On and on and on.</p> |
|
<p>Just to make the point clearer: This is not something "Microsoft" does, it |
|
what every big company does.</p> |
|
<hr /> |
|
<p>This post was built with the help of</p> |
|
<ul> |
|
<li><a href="https://social.paritybit.ca/@jbauer">Jake Bauer</a></li> |
|
<li><a href="https://mastodon.social/@newsbot">newsbot</a></li> |
|
<li><a href="https://mastodon.social/@hntooter">HN Tooter</a></li> |
|
</ul> |
|
|
|
</div> |
|
|
|
|
|
|
|
|
|
</div> |
|
|
|
</body> |
|
|
|
</html>
|
|
|