-
Notifications
You must be signed in to change notification settings - Fork 0
Expand file tree
/
Copy pathindex.html
More file actions
671 lines (330 loc) · 20.1 KB
/
index.html
File metadata and controls
671 lines (330 loc) · 20.1 KB
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
252
253
254
255
256
257
258
259
260
261
262
263
264
265
266
267
268
269
270
271
272
273
274
275
276
277
278
279
280
281
282
283
284
285
286
287
288
289
290
291
292
293
294
295
296
297
298
299
300
301
302
303
304
305
306
307
308
309
310
311
312
313
314
315
316
317
318
319
320
321
322
323
324
325
326
327
328
329
330
331
332
333
334
335
336
337
338
339
340
341
342
343
344
345
346
347
348
349
350
351
352
353
354
355
356
357
358
359
360
361
362
363
364
365
366
367
368
369
370
371
372
373
374
375
376
377
378
379
380
381
382
383
384
385
386
387
388
389
390
391
392
393
394
395
396
397
398
399
400
401
402
403
404
405
406
407
408
409
410
411
412
413
414
415
416
417
418
419
420
421
422
423
424
425
426
427
428
429
430
431
432
433
434
435
436
437
438
439
440
441
442
443
444
445
446
447
448
449
450
451
452
453
454
455
456
457
458
459
460
461
462
463
464
465
466
467
468
469
470
471
472
473
474
475
476
477
478
479
480
481
482
483
484
485
486
487
488
489
490
491
492
493
494
495
496
497
498
499
500
501
502
503
504
505
506
507
508
509
510
511
512
513
514
515
516
517
518
519
520
521
522
523
524
525
526
527
528
529
530
531
532
533
534
535
536
537
538
539
540
541
542
543
544
545
546
547
548
549
550
551
552
553
554
555
556
557
558
559
560
561
562
563
564
565
566
567
568
569
570
571
572
573
574
575
576
577
578
579
580
581
582
583
584
585
586
587
588
589
590
591
592
593
594
595
596
597
598
599
600
601
602
603
604
605
606
607
608
609
610
611
612
613
614
615
616
617
618
619
620
621
622
623
624
625
626
627
628
629
630
631
632
633
634
635
636
637
638
639
640
641
642
643
644
645
646
647
648
649
650
651
652
653
654
655
656
657
658
659
660
661
662
663
664
665
666
667
668
669
670
671
<!DOCTYPE html>
<!--[if IEMobile 7 ]><html class="no-js iem7"><![endif]-->
<!--[if lt IE 9]><html class="no-js lte-ie8"><![endif]-->
<!--[if (gt IE 8)|(gt IEMobile 7)|!(IEMobile)|!(IE)]><!--><html class="no-js" lang="en"><!--<![endif]-->
<head>
<meta charset="utf-8">
<title>Andy Sinesio</title>
<meta name="author" content="Andy Sinesio">
<meta name="description" content="Year after year, your software grows. Developers are building new systems more quickly than old ones are retired. Eventually, your mix of services, …">
<!-- http://t.co/dKP3o1e -->
<meta name="HandheldFriendly" content="True">
<meta name="MobileOptimized" content="320">
<meta name="viewport" content="width=device-width, initial-scale=1">
<link rel="canonical" href="http://asinesio.github.com/">
<link rel="meta" type="application/rdf+xml" title="FOAF" href="/foaf.rdf" />
<link href="/favicon.png?v=2" rel="icon">
<link href="/stylesheets/screen.css" media="screen, projection" rel="stylesheet" type="text/css">
<script src="/javascripts/modernizr-2.0.js"></script>
<script src="/javascripts/ender.js"></script>
<script src="/javascripts/octopress.js" type="text/javascript"></script>
<link href="/atom.xml" rel="alternate" title="Andy Sinesio" type="application/atom+xml">
<!--Fonts from Google"s Web font directory at http://google.com/webfonts -->
<link href="http://fonts.googleapis.com/css?family=PT+Serif:regular,italic,bold,bolditalic" rel="stylesheet" type="text/css">
<link href="http://fonts.googleapis.com/css?family=PT+Sans:regular,italic,bold,bolditalic" rel="stylesheet" type="text/css">
<script type="text/javascript">
var _gaq = _gaq || [];
_gaq.push(['_setAccount', 'UA-38496623-1']);
_gaq.push(['_trackPageview']);
(function() {
var ga = document.createElement('script'); ga.type = 'text/javascript'; ga.async = true;
ga.src = ('https:' == document.location.protocol ? 'https://ssl' : 'http://www') + '.google-analytics.com/ga.js';
var s = document.getElementsByTagName('script')[0]; s.parentNode.insertBefore(ga, s);
})();
</script>
</head>
<body >
<header role="banner"><hgroup>
<h1><a href="/">Andy Sinesio</a></h1>
</hgroup>
</header>
<nav role="navigation"><ul class="subscription" data-subscription="rss">
<li><a href="/atom.xml" rel="subscribe-rss" title="subscribe via RSS">RSS</a></li>
</ul>
<form action="http://google.com/search" method="get">
<fieldset role="search">
<input type="hidden" name="q" value="site:asinesio.github.com" />
<input class="search" type="text" name="q" results="0" placeholder="Search"/>
</fieldset>
</form>
<ul class="main-navigation">
<li><a href="/">Blog</a></li>
<li><a href="/blog/archives">Archives</a></li>
<li><a href="/about">About</a></li>
</ul>
</nav>
<div id="main">
<div id="content">
<div class="blog-index">
<article>
<header>
<h1 class="entry-title"><a href="/blog/2013/05/20/the-big-ball-of-lights/">The Big Ball of Lights</a></h1>
<p class="meta">
<time datetime="2013-05-20T19:08:00-05:00" pubdate data-updated="true">May 20<span>th</span>, 2013</time>
</p>
</header>
<div class="entry-content"><p>Year after year, your software grows. Developers are building new systems more quickly than old ones are retired.</p>
<p>Eventually, your mix of services, queues, and applications will probably look like this:</p>
<p><img src="/assets/2013-05-20/ball-of-lights.jpg" alt="Christmas Vacation Ball of Lights" /></p>
<p>Of course, you may not realize how tangled it really is until you decide to upgrade or migrate some key part of the infrastructure.</p>
<p>If you’re lucky, you may end up having this conversation <em>prior to deployment</em>:</p>
<blockquote><p>You: “We’re updating ‘Awesome Web Service’ to a new API revision this weekend.”<br/>Developer: “Cool. Did you notify Team Clueless?”<br/>You: “No. Why would they care?” <br/>Developer: “Last year, they needed some data from the ‘Awesome Web Service’, so they started using it. And they didn’t tell anybody and didn’t update the documentation.”</p></blockquote>
<p>When this occurs, you’ll be tempted, a la Rusty Griswold, to give up out of frustration.</p>
<p>If you had thought to implement a basic HTTP call tracking strategy, this would not have happened!</p>
</div>
<footer>
<a rel="full-article" href="/blog/2013/05/20/the-big-ball-of-lights/">Continue reading →</a>
</footer>
</article>
<article>
<header>
<h1 class="entry-title"><a href="/blog/2013/04/05/blink-is-not-the-coming-of-the-apocalypse/">Blink Is Not the Coming of the Apocalypse</a></h1>
<p class="meta">
<time datetime="2013-04-05T00:54:00-05:00" pubdate data-updated="true">Apr 5<span>th</span>, 2013</time>
</p>
</header>
<div class="entry-content"><p>Since Google <a href="http://blog.chromium.org/2013/04/blink-rendering-engine-for-chromium.html">announced they were forking WebKit</a>, I’ve seen nothing but <a href="http://prng.net/blink-faq.html">universally negative reactions</a>.</p>
<p>The primary points seem to be that Blink is bad because:</p>
<h4>“Developers will now have another major browser rendering engine that they will need to test.”</h4>
<p>This is just not true. If you’re building quality web software, you are already testing your site on both Chrome and Safari (Mobile and desktop).</p>
<p>A <a href="http://en.wikipedia.org/wiki/Internet_Explorer_6">web monoculture</a> is bad for everyone. A healthy web ecosystem consisting of equal parts Chrome, Safari, Firefox, Opera, and Internet Explorer means that the users will have a choice, because all web apps will generally need to work with all browsers.</p>
<h4>“WebKit and Blink will diverge and re-implement each other’s features, thus slowing progress.”</h4>
<p>Google already <a href="https://news.ycombinator.com/item?id=5490242">wasn’t contributing</a> much of their code back to WebKit. The announcement of Blink is truly just formalizing what was already happening.</p>
<h4>“Google is going to use this to invade my privacy and track me across the Web.”</h4>
<p>Yes. They were doing that anyway, and they haven’t exactly had a great <a href="http://www.pcmag.com/article2/0,2817,2411916,00.asp">track record</a> of protecting your privacy. If you were concerned about this, you wouldn’t be using Chrome anyway.</p>
<p>Think about it; Google forked WebKit for the same reason Apple replaced Google Maps - Google wants to control their own destiny.</p>
<p>Blink is not the coming of the web browser apocalypse (but it does have a terrible name).</p>
<p>The apocalypse happened when Internet Explorer crushed Netscape. We’ve recovered from that, and we’re never going back.</p>
</div>
</article>
<article>
<header>
<h1 class="entry-title"><a href="/blog/2013/03/05/gamification-of-code-quality/">Gamification of Code Quality</a></h1>
<p class="meta">
<time datetime="2013-03-05T20:35:00-06:00" pubdate data-updated="true">Mar 5<span>th</span>, 2013</time>
</p>
</header>
<div class="entry-content"><p>Quality is one of the most difficult things to define. There have been <a href="http://en.wikipedia.org/wiki/Zen_and_the_Art_of_Motorcycle_Maintenance">entire books written</a> about the topic.</p>
<p>Unsurprisingly, it’s also difficult to define when it comes to software. However, most developers will readily agree that writing <a href="http://en.wikipedia.org/wiki/Unit_testing">unit tests</a> and practicing <a href="http://en.wikipedia.org/wiki/Test-driven_development">test-driven development</a> are tools for writing higher quality software.</p>
<h3>Tests are great, why aren’t you writing them?</h3>
<p>After a few laps on a recent project, I noticed that despite our “test-driven development” goals, our test coverage was lacking. We were hoving around 50% lines/50% methods complete.</p>
<p>After prodding our developers and “vowing to get better”, it wasn’t happening. So I came up with a new plan.</p>
</div>
<footer>
<a rel="full-article" href="/blog/2013/03/05/gamification-of-code-quality/">Continue reading →</a>
</footer>
</article>
<article>
<header>
<h1 class="entry-title"><a href="/blog/2013/02/26/a-software-update-is-required/">A Software Update Is Required.</a></h1>
<p class="meta">
<time datetime="2013-02-26T21:40:00-06:00" pubdate data-updated="true">Feb 26<span>th</span>, 2013</time>
</p>
</header>
<div class="entry-content"><p>My brother gave me <a href="http://us.gran-turismo.com/us/">Gran Turismo 5</a> for Christmas. I’ve played all of the other GT games and loved them. GT5 had been out for awhile, but I was still excited to give it a try.</p>
<p>I returned home from Christmas; after a few days, I finally had a free hour or two, so I booted up the PS3 and threw in the game. And I was greeted by this:</p>
<p><img src="/assets/2013-02-26/ps3-update.jpg" alt="The latest update data was found." /></p>
<p><em>14 hours later</em>, the game finally finished updating and allowed me to play. Too bad that I no longer had the free hour or two, so it took another week before I was able to actually play the game.</p>
<p>It reminded me of this nefarious monstrosity:</p>
<p><img src="/assets/2013-02-26/windows-update.png" alt="Windows Update restart nag" /></p>
<p>“But, I don’t want to update <em>at all</em>,” I plead.</p>
<p>The system scoffs. “Tough shit, buddy. You’re going to have to deal with this now because I don’t value your time.”</p>
</div>
<footer>
<a rel="full-article" href="/blog/2013/02/26/a-software-update-is-required/">Continue reading →</a>
</footer>
</article>
<article>
<header>
<h1 class="entry-title"><a href="/blog/2013/02/23/the-perils-of-the-grails-searchable-plugin/">The Perils of the Grails Searchable Plugin</a></h1>
<p class="meta">
<time datetime="2013-02-23T00:05:00-06:00" pubdate data-updated="true">Feb 23<span>rd</span>, 2013</time>
</p>
</header>
<div class="entry-content"><p>The <a href="http://grails.org/plugin/searchable">Grails Searchable Plugin</a> is generally where developers end up when they are looking to add full-text searching to their Grails application.</p>
<p>It’s got a lot going for it:</p>
<ul>
<li>Simple, embedded Lucene index with minimal initial setup.</li>
<li>Automatic GORM mirroring of changes.</li>
<li>Widely used; according to Grails.org, it’s installed in almost <em>7% of Grails projects</em>.</li>
<li>Fast and simple, it works out of the box.</li>
</ul>
<p>Before I go further: know that I really like the Searchable plugin. It’s a great way to get search in a smaller application.</p>
</div>
<footer>
<a rel="full-article" href="/blog/2013/02/23/the-perils-of-the-grails-searchable-plugin/">Continue reading →</a>
</footer>
</article>
<article>
<header>
<h1 class="entry-title"><a href="/blog/2013/02/19/powerful-admin-interfaces-with-graphite-and-statsd/">Powerful Admin Interfaces With Graphite and StatsD</a></h1>
<p class="meta">
<time datetime="2013-02-19T22:02:00-06:00" pubdate data-updated="true">Feb 19<span>th</span>, 2013</time>
</p>
</header>
<div class="entry-content"><p><a href="http://graphite.wikidot.com">Graphite</a> paired with <a href="http://github.com/etsy/statsd">StatsD</a> is a simple, powerful way to get dramatic insight into your application’s behavior.</p>
<p>The seminal <a href="http://codeascraft.etsy.com/2011/02/15/measure-anything-measure-everything/">Etsy blog post</a> on this subject explains it well:</p>
<blockquote><p>If Engineering at Etsy has a religion, it’s the Church of Graphs. If it moves, we track it. Sometimes we’ll draw a graph of something that isn’t moving yet, just in case it decides to make a run for it.</p><footer><strong>Ian Malpass, Etsy</strong> <cite><a href='http://codeascraft.etsy.com/2011/02/15/measure-anything-measure-everything/'>Measure Anything, Measure Everything</a></cite></footer></blockquote>
<h4>With Graphite, you get:</h4>
<ul>
<li>Beautiful, near real-time graphs of metrics.</li>
<li>A simply awesome API to embed graphs and source data in nearly any other system.</li>
</ul>
<h4>Combined with StatsD:</h4>
<ul>
<li>Fire-and-forget (UDP-based) metric data emission and aggregation.</li>
<li>Metrics that make sense.</li>
<li>Brain dead simple API that works in any language, from Groovy to shell scripts.</li>
</ul>
<h3>Knowledge is Power</h3>
<p>What are the first items that get cut from most software projects? <em>Effective support and administrative tools.</em></p>
<p>Without easy tools at your disposal, how many times have you written some code and thought:</p>
<blockquote><p>“What do I do if something goes wrong? Hmm, that’s hard. I guess I’ll just log the error for now.”</p></blockquote>
<p>I’m certainly just as guilty of this transgression as anyone else. Why would I waste valuable time writing a screen to manage the failures – something that may never be used?</p>
</div>
<footer>
<a rel="full-article" href="/blog/2013/02/19/powerful-admin-interfaces-with-graphite-and-statsd/">Continue reading →</a>
</footer>
</article>
<article>
<header>
<h1 class="entry-title"><a href="/blog/2013/02/15/your-ipad-app-sucks/">Your iPad App Sucks.</a></h1>
<p class="meta">
<time datetime="2013-02-15T00:00:00-06:00" pubdate data-updated="true">Feb 15<span>th</span>, 2013</time>
</p>
</header>
<div class="entry-content"><p>Yeah. It’s harsh, but you know it’s true. Your iPad app probably sucks – <em>when compared to your web site.</em></p>
<p>Web browsing on an iPad is a blissful, unique, and sublime experience. It is, in my estimation, the single greatest advancement in web browsing since the advent of <code>XMLHttpRequest</code>.</p>
<p>On an iPad:</p>
<ul>
<li>Want to scroll? Grab the page and slide it over <em>like a piece of paper.</em></li>
<li>Is the text too small or too large? Stretch or pinch it <em>like silly putty.</em></li>
<li>Want to do something special with a word on the page? <em>Touch and hold.</em></li>
</ul>
<p>These interactions are so brilliant and obvious that it makes browsing almost any website – even this one – <em>fun</em>.</p>
</div>
<footer>
<a rel="full-article" href="/blog/2013/02/15/your-ipad-app-sucks/">Continue reading →</a>
</footer>
</article>
<article>
<header>
<h1 class="entry-title"><a href="/blog/2013/02/13/switch-grails-versions/">Switching Grails Versions</a></h1>
<p class="meta">
<time datetime="2013-02-13T00:00:00-06:00" pubdate data-updated="true">Feb 13<span>th</span>, 2013</time>
</p>
</header>
<div class="entry-content"><p>This is my #firstpost, so I thought I’d share a useful Grails shell script.</p>
<p>(<strong>Update: you really should use <a href="http://gvmtool.net">gvm</a> instead of this script.</strong> It is a similar idea but also handles installation, path setup, and other tools like Gradle, vert.x, and Griffon.)</p>
<p>One of the annoying things about using <a href="http://www.grails.org">Grails</a> from the command line is dealing with multiple Grails versions on your system.</p>
<p>This isn’t an issue if you’re using an IDE that can refer to a Grails version outside of your $PATH. However, I find that using a command-line Grails in combination with an IDE like STS or GGTS is the most productive way for me to write Grails code.</p>
</div>
<footer>
<a rel="full-article" href="/blog/2013/02/13/switch-grails-versions/">Continue reading →</a>
</footer>
</article>
<div class="pagination">
<a href="/blog/archives">Blog Archives</a>
</div>
</div>
<aside class="sidebar">
<section>
<h1>Recent Posts</h1>
<ul id="recent_posts">
<li class="post">
<a href="/blog/2013/05/20/the-big-ball-of-lights/">The Big Ball of Lights</a>
</li>
<li class="post">
<a href="/blog/2013/04/05/blink-is-not-the-coming-of-the-apocalypse/">Blink is not the coming of the apocalypse</a>
</li>
<li class="post">
<a href="/blog/2013/03/05/gamification-of-code-quality/">Gamification of Code Quality</a>
</li>
<li class="post">
<a href="/blog/2013/02/26/a-software-update-is-required/">A software update is required.</a>
</li>
<li class="post">
<a href="/blog/2013/02/23/the-perils-of-the-grails-searchable-plugin/">The Perils of the Grails Searchable Plugin</a>
</li>
</ul>
</section>
<section>
<h1>GitHub Repos</h1>
<ul id="gh_repos">
<li class="loading">Status updating…</li>
</ul>
<a href="https://github.com/asinesio">@asinesio</a> on GitHub
<script type="text/javascript">
$.domReady(function(){
if (!window.jXHR){
var jxhr = document.createElement('script');
jxhr.type = 'text/javascript';
jxhr.src = '/javascripts/libs/jXHR.js';
var s = document.getElementsByTagName('script')[0];
s.parentNode.insertBefore(jxhr, s);
}
github.showRepos({
user: 'asinesio',
count: 3,
skip_forks: true,
target: '#gh_repos'
});
});
</script>
<script src="/javascripts/github.js" type="text/javascript"> </script>
</section>
<section>
<h1>Latest Tweets</h1>
<ul id="tweets">
<li class="loading">Status updating…</li>
</ul>
<script type="text/javascript">
$.domReady(function(){
getTwitterFeed("asinesio", 4, false);
});
</script>
<script src="/javascripts/twitter.js" type="text/javascript"> </script>
<a href="http://twitter.com/asinesio" class="twitter-follow-button" data-show-count="false">Follow @asinesio</a>
</section>
<section class="googleplus googleplus-hidden">
<h1>
<a href="https://plus.google.com/109646729091839976697?rel=author">
<img src="http://www.google.com/images/icons/ui/gprofile_button-32.png" width="32" height="32">
Google+
</a>
</h1>
</section>
</aside>
</div>
</div>
<footer role="contentinfo"><p>
Copyright © 2013 - Andy Sinesio -
<span class="credit">Powered by <a href="http://octopress.org">Octopress</a></span>
</p>
</footer>
<div id="fb-root"></div>
<script>(function(d, s, id) {
var js, fjs = d.getElementsByTagName(s)[0];
if (d.getElementById(id)) {return;}
js = d.createElement(s); js.id = id;
js.src = "//connect.facebook.net/en_US/all.js#appId=212934732101925&xfbml=1";
fjs.parentNode.insertBefore(js, fjs);
}(document, 'script', 'facebook-jssdk'));</script>
<script type="text/javascript">
(function() {
var script = document.createElement('script'); script.type = 'text/javascript'; script.async = true;
script.src = 'https://apis.google.com/js/plusone.js';
var s = document.getElementsByTagName('script')[0]; s.parentNode.insertBefore(script, s);
})();
</script>
<script type="text/javascript">
(function(){
var twitterWidgets = document.createElement('script');
twitterWidgets.type = 'text/javascript';
twitterWidgets.async = true;
twitterWidgets.src = 'http://platform.twitter.com/widgets.js';
document.getElementsByTagName('head')[0].appendChild(twitterWidgets);
})();
</script>
</body>
</html>