|
I read a lot of books and once I start reading a book I normally finish it. This article proposes that it may be more valuable to have a bunch of books that are unread. Not sure I completely buy in to the proposition that “Read books are far less valuable than unread ones” however maybe I won’t feel so guilty buying a book and then leaving it unread.
|
|
I read a lot of books and once I start reading a book I normally finish it. This article proposes that it may be more valuable to have a bunch of books that are unread. Not sure I completely buy in to the proposition that “Read books are far less valuable than unread ones” however maybe I won’t feel so guilty buying a book and then leaving it unread.
|
|
We’re closing out #NoServerNovember with a special-edition virtual hackathon for AWS re:Invent. Participate from anywhere, win cool prizes.
|
|
One of the things I like most about our subscription base is its solid nature. We still have a lot of subscribers in the $9 per month plan which we discontinued several years ago (it was so long ago I can’t find the relevant blog post anymore). That’s wonderful, it means people like our product and are with us for the long run. However, flexibility is important too. The fact that subscriptions can be canceled easily is important. Cancelin..
|
|
Types of Development #1 Rage driven development Where an existing application/process causes one to rage so hard you spend the next 6 weeks over-engineering a solution to solve a simple problem. Example Perl. Types of Development #2 Test driven development Where previous projects and death marches result in a violent reaction of over-correcting for past failures and everything must be tested dammit. Example includes any project ..
|
|
Been saving admin code snippets in my own org source blocks , some requiring root access. Handy for keeping tiny self-documented scripts to easily bootstrap other machines. TIL org source block's :dir argument can be used to run block as root by using tramp syntax: /:dir sudo:: As user: #+BEGIN_SRC sh whoami #+END_SRC #+RESULTS: : user As root: #+BEGIN_SRC sh :dir /sudo:: whoami #+END_SRC #+RESULTS: : root
|
|
We write a lot of unit tests while working on the SoundCloud iOS application. Unit tests are obviously great. They’re short, they’re…
|
|
Almost every company accumulates tech debt as time goes on. Tight deadlines, changing requirements, scaling issues, poor or short-sighted system designs, knowledge silos, inconsistent coding practices, turnover of key staff — these things all happen and can contribute to tech debt. So what can be done about it once it’s there?
|
|
Via objc.io and Max Howell's retweet , TIL about Swift's inline computed properties. Another one to try on Org Babel . func greetWorld() { var message = "hello" var betterMessage: String { return "\(message) world" } print(betterMessage) } greetWorld()
|
|
Paul Hudson's tweet introduced me to Swift's multiline string indentation control using closing quotes. Neat! Being an org-mode fan, I thought I'd give Swift multiline strings a try using Org Babel's ob-swift . I get to verify it and document at the same time. Win. Swift org mode source blocks (ie. BEGIN_SRC/END_SRC) can be added as follows: #+BEGIN_SRC swift :exports both print(""" Hello World """) print(""" Hello World ""..
|
|
Almost every company accumulates tech debt as time goes on. Tight deadlines, changing requirements, scaling issues, poor or short-sighted system designs, knowledge silos, inconsistent coding practices, turnover of key staff — these things all happen and can contribute to tech debt. So what can be done about it once it’s there?
|
|
We write a lot of unit tests while working on the SoundCloud iOS application. Unit tests are obviously great. They’re short, they’re…
|
|
Proving the hardness of an algorithm for non-polynomial algorithms takes skill. As we wrap up our journey of The Algorithm Design Manual we’re going to leave you with some final tips to help prove the hardness of these intractable problems. But first, onto the Daily Problem:
|
|
We’ve already looked at intractable problems with straightforward translations. In this post, we are going to look at more creative reductions for problems where we don’t have a simple, singular translation available. But first, onto the Daily Problem:
|
|
In the last article we covered the most elementary examples of how you can reduce one problem into another. In this article, we’re going to provide some more reductions in the context of computer science, particularly in relation to our extensive study of graphs. But first, onto the Daily Problem:
|
|
We’re rounding the final corner in our algorithms series to focus on seemingly impossible problems. In our dynamic programming segment, we focused on taking very hard problems in exponential time and leveraged caching to get them down into polynomial time. We hinted that certain applications cannot benefit from this optimization, such as the Traveling Salesman Problem. So how can you possibly solve the most complex problems when they are un..
|
|
Proving the hardness of an algorithm for non-polynomial algorithms takes skill. As we wrap up our journey of The Algorithm Design Manual we’re going to leave you with some final tips to help prove the hardness of these intractable problems. But first, onto the Daily Problem:
|
|
We’ve already looked at intractable problems with straightforward translations. In this post, we are going to look at more creative reductions for problems where we don’t have a simple, singular translation available. But first, onto the Daily Problem:
|
|
In the last article we covered the most elementary examples of how you can reduce one problem into another. In this article, we’re going to provide some more reductions in the context of computer science, particularly in relation to our extensive study of graphs. But first, onto the Daily Problem:
|