|
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:
|
|
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..
|
|
This is for you kid,” said my uncle, “have fun!” I was 12 and I got my first mask and fins. I loved it. I would go every day to the seaside, to the rocky pier, and dive next to … Continue reading →
|
SQL upserts are a combination of an INSERT and/or UPDATE into a single database operation which allows rows to to be added or modified in an atomic, concurrent-safe way. [Continue reading...] PostgreSQL Upserts - INSERT or UPDATE Made Easy The post PostgreSQL Upserts - INSERT or UPDATE Made Easy appeared first on BHoey .
|
|
I show that for the same reason that the golden ratio, $\phi=1.6180334..$, can be considered the most irrational number, that $1+\sqrt{2}$ can be considered the 2nd most irrational number, and indeed why $(9+\sqrt{221})/10$ can be considered the 3rd most irrational number. This blog post was featured on the front page of Hacker News a … Continue reading "Going beyond the Golden Ratio."
|
|
Box layout Y is one of the most used layouts in Codename One. It’s a wonderful, easy to use layout that makes vertical scrollable layout trivial. I love its simplicity, but sometimes that simplicity goes too far. A good example of that is the common layout where we have a button at the bottom of the screen. Historically we solved this by nesting box into a border layout:
|
|
Success goes hand in hand with confidence. But which causes which? Does success cause confidence, or is it the other way around? One way to look at it is to say that successful people gain confidence through their “wins” and display it. We observe their confidence and associate it with success. Another way is to note, that when we see someone confident, we assume they are successful, they are “doing it right”. We treat them with increas....
|