marxama

7 ms·

31.
by marxama 10y ago
No joke, I'm 31, only 2-3 years ago the companies were all over me, I would get offers right and left. Now, not so much, I've noticed a pretty huge difference.
32.
by marxama 10y ago
I love Smallworld, and yeah, I never get tired of it. Another one whose rules are pretty straightforward is Power Grid, been playing it for years and it hasn't gotten old yet (except for the sometimes pretty sudden and ruthless endgame
33.
by marxama 10y ago
One thing is that a lot of testers are still working in a very rigid way. First, design and write down the test cases (based on a specification that is most likely flawed and incomplete). Then, perform the tests. Then, document the results.
34.
by marxama 10y ago
I don't understand why people seem to think that testers could or should be replaced by automated tests. I've worked a lot with test automation, and I find it super important to have automated tests for any long-living project, bu
35.
by marxama 10y ago
Great read, thanks! The same effect was used brilliantly in Monaco.
36.
by marxama 10y ago
I think it's also interesting to note that sometimes when choosing immutability as the default, which gives a slight performance penalty for basic operations compared to doing normal mutation, you end up being able to save lots of perf
37.
by marxama 11y ago
That's good to know, thanks for pointing it out!
38.
by marxama 11y ago
IRL, I've actually met two people who've watched and enjoyed talks by Hickey, but I haven't met a single one who's actually tried Clojure...
39.
by marxama 11y ago
I disagree, I've come across several cases where front-end-only state need to be shared by components not naturally sharing some common parent component in which the state should reside.
40.
by marxama 11y ago
This post is enough for me to decide to get this NOW.
41.
by marxama 12y ago
Every so often, I use strings in my code. F# gives me no compile time checks against null references when I'm dealing with strings, nor any other reference type. I did mention that the constructs F# provide are not nullable, which is n
42.
by marxama 12y ago
> no null reference => no null reference exception This is only true in the same sense that there are no NRE in C# as long as you don't use reference types. F# seems to be a fine language, and its non-nullable types are certainly
43.
by marxama 12y ago
> 6. Nulls are NOT allowed, in general. I really want to like F#, but that's a really big "in general". I love the idea of option types, but I often hear with regards to F#, "forget about NullReferenceExceptions!&quot
44.
by marxama 12y ago
That's really nice. Is it possible to do the destructuring directly in the argument list?
45.
by marxama 12y ago
ClojureScript, along with Reagent (or some other React.js wrapper like Om or Quiescent - I currently prefer Reagent, which has been gaining lots of traction recently), Figwheel and a browser REPL, has really had a lot of impact on how I vie
46.
by marxama 12y ago
I got to use it a bit in a Real-Time Systems course I took recently. I wasn't too excited about it starting out, it didn't initially feel like much more than a different C. As I've been spending some time with Clojure's
47.
by marxama 12y ago
Another thing is that the F# example has equality semantics built in, whereas in the C# example, you'd have to override Equals (and GetHashCode), adding more lines still (for some tedious work that you shouldn't have to do).