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.
123 lines
5.1 KiB
123 lines
5.1 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">Clean Code: A Handbook of Agile Software Craftsmanship - Robert C. Martin</h1>
|
||
|
|
<span class="post-date">
|
||
|
|
2015-01-25
|
||
|
|
|
||
|
|
<a href="https://blog.juliobiason.me/tags/books/">#books</a>
|
||
|
|
|
||
|
|
<a href="https://blog.juliobiason.me/tags/robert-c-martin/">#robert c. martin</a>
|
||
|
|
|
||
|
|
<a href="https://blog.juliobiason.me/tags/it/">#it</a>
|
||
|
|
|
||
|
|
<a href="https://blog.juliobiason.me/tags/reviews/">#reviews</a>
|
||
|
|
|
||
|
|
<a href="https://blog.juliobiason.me/tags/stars-3/">#stars:3</a>
|
||
|
|
|
||
|
|
<a href="https://blog.juliobiason.me/tags/published-2007/">#published:2007</a>
|
||
|
|
|
||
|
|
</span>
|
||
|
|
<p><a href="https://www.goodreads.com/book/show/3735293-clean-code">GoodReads Summary</a>:
|
||
|
|
Even bad code can function. But if code isn't clean, it can bring a
|
||
|
|
development organization to its knees. Every year, countless hours and
|
||
|
|
significant resources are lost because of poorly written code. But it doesn't
|
||
|
|
have to be that way. </p>
|
||
|
|
<span id="continue-reading"></span><div>
|
||
|
|
★★★☆☆
|
||
|
|
</div>
|
||
|
|
<p><strong>About the edition</strong></p>
|
||
|
|
<p>If there is one single weird thing about the Kindle edition is the code
|
||
|
|
formatting. While reading code in non-monospaced font is weird but not
|
||
|
|
impossible, reading code in non-monospaced font that is justified like normal
|
||
|
|
text <em>is</em>.</p>
|
||
|
|
<p>The really annoying part is that, at the end of the book, the full listing of
|
||
|
|
the discussed code is shown as "images", large blocks of code that don't
|
||
|
|
follow the selected Kindle background and doesn't seem to allow selection, but
|
||
|
|
it <em>is</em> monospaced and it is <em>not</em> justified. Why won't they use
|
||
|
|
it all over the code is beyond me.</p>
|
||
|
|
<p><strong>About the content</strong></p>
|
||
|
|
<p>The book goes with a good start, listing almost all the pet peeves I have with
|
||
|
|
other people code ("why the <em>fuck</em> they named things like
|
||
|
|
<em>this</em>?", "why the <em>hell</em> this function have that many
|
||
|
|
parameters?" and so on -- heck, even the problem with consistent style was
|
||
|
|
there). Although it points the problem and how to improved it, it sometimes
|
||
|
|
lacks the <em>why</em> those changes need to be made.</p>
|
||
|
|
<p>But, then, things start to really go downhill, with lots of stuff that
|
||
|
|
contradicts previous statements (specially the Single Responsibility
|
||
|
|
Principle), and a bunch of things that are language specific. There is one
|
||
|
|
really good chapter that picks a code and goes slowly showing the principles
|
||
|
|
discussed in the start of the book, applying one after the other, so you can
|
||
|
|
see the code changing and becoming easier to read. The sad part is that it is
|
||
|
|
used only once.</p>
|
||
|
|
<p>Honestly, I which there was a lot more of "why you should do this", only
|
||
|
|
because as a seasoned programmer, I agree -- and use -- with a lot of the
|
||
|
|
points in the book, but I lack the experience the tell younger programmers
|
||
|
|
<em>why</em> they should not do what they are doing.</p>
|
||
|
|
<p>It's a good book, nonetheless, although not exceptionally good.</p>
|
||
|
|
|
||
|
|
</div>
|
||
|
|
|
||
|
|
|
||
|
|
|
||
|
|
|
||
|
|
</div>
|
||
|
|
|
||
|
|
</body>
|
||
|
|
|
||
|
|
</html>
|