meta user
network profile
| bio | website | github.com/ahammar |
|---|---|---|
| location | Trondheim, Norway | |
| age | 27 | |
| visits | member for | 2 years, 1 month |
| seen | 13 hours ago | |
| stats | profile views | 40 |
CS student at NTNU, Trondheim, Norway.
|
Apr 20 |
awarded | Yearling |
|
Dec 1 |
comment |
Why is the sudden increase in number of Git submitters on Debian popcon graph in 2010-01? By the way, it's popcon (**pop**ularity **con**test), not popcorn. |
|
Jun 8 |
awarded | Constituent |
|
Jun 8 |
awarded | Caucus |
|
May 5 |
comment |
Is it bad practice to name an unused variable with a single underscore? Strictly speaking, at least in Haskell, _ is a pattern, not a variable. It's a subtle difference, but it means that you can use it multiple times in something like (x, _, _) = ..., whereas trying to bind the same variable multiple times would be an error. |
|
Apr 20 |
awarded | Yearling |
|
Feb 28 |
answered | What are the drawbacks of elastic tabstops? |
|
Feb 4 |
awarded | Commentator |
|
Feb 4 |
comment |
Is there any reason why most programming languages don't have '!>' (not greater than) and '!<' (not less than) operators? They are, however, usually not equivalent when using floating-point numbers. For example, comparing anything with NaN is false, so !(2 < NaN) == true, while (2 >= NaN) == false. |
|
Dec 22 |
awarded | Nice Answer |
|
Dec 6 |
comment |
Does simplicity always improve Readability? @Steve314: [a..b] is syntactic sugar for enumFromTo a b, so they are exactly the same. |
|
Nov 15 |
comment |
Introducing Programming To a Mathematician Also, Eleven Reasons to use Haskell as a Mathematician. |
|
Oct 3 |
comment |
Should we attempt to review all our code? @TomSquires: Exactly. When you've been working with a piece of code for a long time, you can become "blind" to otherwise obvious flaws in it, because you see it as what it's supposed to be instead of what it is. These problems will be easier to spot for someone who has never seen the code before. Writers have the same problem, and just like books don't get released without proofreading, code should not be released without review. There are also other benefits to doing code reviews, for example it's good for transferring knowledge between the members of your team. |
|
Sep 1 |
revised |
What is the reason for creating the symbols ∞ on the client side? added 159 characters in body |
|
Sep 1 |
answered | What is the reason for creating the symbols ∞ on the client side? |
|
Aug 29 |
comment |
If this is camelCase what-is-this?like-this-casing is very common in LISP/Scheme variants. |
|
Aug 5 |
comment |
Haskell code accompanying the Paul Hudak 1994 US Navy experiment paper In case you read the code and wonder what Dialogue is, it's what Haskell used for IO before monads were introduced to the language in 1996. |
|
Jul 14 |
answered | Inheritance gone wrong |
|
Jul 11 |
comment |
What are the simplest Code Katas There's a nice list of katas at the Coding Dojo wiki. |
|
Jun 27 |
awarded | Citizen Patrol |
