kenbot

9 ms·

1.
The worst thing in our Scala code: Futures(rea.tech)
2 points by kenbot 10y ago|0 comments
2.
Imagine a world without mocks(youtube.com)
1 points by kenbot 11y ago|0 comments
3.
by kenbot 11y ago
It's time for this terrible "Objects in the large, functions in the small" idea to be put to bed. FP can do side-effects, asynchrony etc just fine, it's just about controlling them so you can still reason about your prog
4.
Your data structures are made of maths(slideshare.net)
3 points by kenbot 11y ago|0 comments
5.
by kenbot 12y ago
Hopefully! We'll find out soon. Fingers crossed.
6.
by kenbot 12y ago
I went into more verbal detail in the actual presentation; the argument is something like: 1) Programming is maths 2) Programming is about abstraction and finding patterns 3) CT describes abstract patterns in maths, and is therefore directl
7.
by kenbot 12y ago
Hi everyone, author here. One thing to remember is that each slide had a lot of verbal explanation around it, so I'm not surprised that it's confusing by itself! We took a video, so hopefully it turns out OK so we can put it onlin
8.
by kenbot 12y ago
Hi Jeremy, author here. Firstly, thanks for all your great stuff on Math/Programming, it's been a great source of inspiration! I would have liked to include Universal Properties, but I decided it was just too much to grasp for one
9.
To Kill a Mockingtest(techblog.realestate.com.au)
13 points by kenbot 12y ago|3 comments
10.
by kenbot 12y ago
The vast differences between software and buildings correspond to the vast differences in designing them. In context here, "minute detail" is obviously a relative term comparing the requirements of software and architecture design
11.
by kenbot 12y ago
They have almost nothing in common, and it's accidental when they do. For instance: - Designing software in minute detail beforehand is generally neither necessary nor possible. - It is impossible for someone to be a capable software &
12.
by kenbot 12y ago
There's certainly great value in reading application source code, but it has nothing to do with physical Architecture. I do wish people would let go of this tired and completely wrong metaphor.
13.
by kenbot 12y ago
"Weak" and "strong" are not well-defined terms, and you'll find different defs around the place. I deliberately used "weak" in the title as a loose umbrella term for the sundry malpractices detailed below.
14.
by kenbot 12y ago
Hi Manicdee! The point is that with any unityped representation you can come up with, the name tells you nothing certain; any conclusions you think you can draw from it are pixie-dust and moonshine. Even with nonsense names, the argument
15.
by kenbot 13y ago
Lisp for the 21st century and it's.... _more_ object oriented?
16.
by kenbot 13y ago
A superset of ... what the? Why do you keep trotting out this garbage thread after thread? Every language takes influences from others, if that's what you meant. Scala is influenced by Java, C# and Haskell, in that order. Kotlin is
17.
by kenbot 13y ago
There's a lot of "seems" going around from people who haven't used the language, or dynamic-typing folk who obviously aren't going to pick a language that bets the farm on static types. As a long-time Java dev mysel
18.
by kenbot 13y ago
You can write any program with a Turing machine. That's a silly definition of a type system. I've never heard this usage anywhere else.
19.
by kenbot 13y ago
> Can you not write any program using either? While you can make do with either, they have complementary strengths and weaknesses, which are useful in different situations. See "Expression Problem", and "Visitor Pattern&q
20.
by kenbot 13y ago
How is Scala faltering?
21.
by kenbot 13y ago
You ran with this "three complete type systems" line in the last thread, and it's still totally wrong. ADTs/pattern matching are not "a complete type system". Structural types are not "a complete type sys
22.
by kenbot 13y ago
Erk, no it isn't. If your semantics require an optional value, then encode it that way explicitly. Don't inflict special cases and bugs on everyone else.
23.
by kenbot 13y ago
Title should have been (-> read eval print λove) :)
24.
by kenbot 13y ago
It reads disconcertingly like a patent application.
25.
by kenbot 13y ago
Try looking at the pattern the letters form on the keyboard...
26.
by kenbot 13y ago
I'm not at all sure what your point is. There's nothing controversial about the benefits of referential transparency and immutable state, for modularity, composition and simplicity. What is obscure to you? It won't be to everyone.
27.
by kenbot 14y ago
The US... what? How? The North started the Korean war, not the US. US troops maintain a balance of power in the region, which has allowed South Korea and Japan to develop into wealthy, stable industrialised democracies. Regardless of the lo
28.
by kenbot 14y ago
Bloody Mercator. Confusing generations of Australian schoolchildren since ...always. "But you said we were the biggest island!"
29.
by kenbot 14y ago
Yep, thanks for the link. :) I'm inclined to think that anyone with his success and media profile will inevitably have jealous rivals who think he's a show pony, and that they'd be lining up to stick in daggers now he's down. So maybe the a
30.
by kenbot 14y ago
Bob Hawke had an affair with his biographer while he was Prime Minister of Australia in the 80s, and they are still married. The incident is barely a footnote on his Wikipedia page covering his long and successful career. It's beyond me wh

More ›