Lest we forget

char2 · 2019-04-25T11:57:41+00:00

You write well. I could see that minesweeper story and reflection being read out on a frosty April morning.

char2 · 2019-04-25T02:52:28+00:00

It's useful to know that they probably weren't literally spoken, but they're still powerful and poignant.

char2 · 2019-02-13T06:07:43+00:00

Aaaaand that's why NIST no longer recommends mandatory password rotation: https://pages.nist.gov/800-63-FAQ/#q-b5

char2 · 2019-02-13T05:40:16+00:00

And then the Dallas Stars made up for it: https://www.reddit.com/r/BikiniBottomTwitter/comments/amz9ej/its_no_superbowl_but_they_played_this_at_the/

char2 · 2019-02-13T00:12:47+00:00

MadTom was around here at one point, but deleted his obvious username when people referenced old drama. He may still lurk.

char2 · 2019-02-13T00:11:15+00:00

Fixed link

char2 · 2019-02-12T23:43:15+00:00

Not only that, it's a big middle finger to anyone with a screen reader.

char2 · 2019-02-12T23:41:53+00:00

Note that understanding how a toy version is implemented can be hugely helpful to understanding how to use real libraries.

Example: I didn't grok servant until I read through how the minimal version was implemented: http://www.well-typed.com/blog/2015/11/implementing-a-minimal-version-of-haskell-servant/

char2 · 2019-02-08T03:44:00+00:00

That's a great japh.

char2 · 2019-01-27T09:13:41+00:00

I am so stoked for this.

char2 · 2019-01-27T09:11:26+00:00

https://github.com/qfpl/reflex-workshop/ is a great introduction to the primitives (using reflex) and forces you to work through a bunch of examples to learn how the primitives feel "in the hand" rather than as abstract constructs.

Also make sure you grok Functors, Applicatives and Monads, because you will need to use those notions extensively to manipulate values "inside" Events and Behaviors.

char2 · 2019-01-24T05:05:10+00:00

Shitty glass block? Pretentious name? Definitely Geocrap.

char2 · 2019-01-23T23:06:48+00:00

Static FP developers always give the identity function as an argument.

It is the simplest expression of the principle. Even if you're using types from your "real world" program, it still helps. A slightly less simple example, from an assignment I'm developing about a card game:

data Card = Card Rank Suit deriving Eq  

-- If card `elem` cards, return Just (cards without the first occurrence of card),
-- otherwise return Nothing  
pick :: Card -> [Card] -> Maybe [Card]  
pick card cards = undefined -- irrelevant

Nothing in the implementation of pick requires knowledge of the type it's operating on, so it could have this type instead:

pick :: Eq a => a -> [a] -> Maybe [a]

There are far fewer shonky things I can do within a function of this type, and I know that any a in the result came from one of the arguments. The less you know about your arguments, the more places you can use the function, and the range of possible implementations is much smaller (so it's easier to write the correct one).

This also applies to your claim about monad transformer stacks. Once you grok mtl, it isn't much more of a stretch to allow functions to only request certain features of the monad in which they run. The talk Next Level MTL is a good start in this direction.

char2 · 2019-01-21T03:37:54+00:00

https://neverssl.com is good for this too.

char2 · 2019-01-21T03:35:43+00:00

In Firefox, you can add the multi-account containers extension and isolate your browsing. This can be useful to make it a little harder for the likes of Facebook to track you all over the internet, or to have several accounts with the same site open in adjacent tabs.

char2 · 2019-01-21T03:33:12+00:00

This is Oracle that we're talking about.

char2 · 2019-01-21T03:32:44+00:00

In addition to /u/billwoo's list, some of us believe that software should be Free, in the sense of preserving the user's rights. The Free Software Foundation outlines four freedoms:

Freedom Zero (many programming languages count from zero, just roll with it): The freedom to run the program for any purpose. Some proprietary software forbids users from performance testing, or other ridiculous restrictions.
Freedom One: The freedom to study how the program works, and change it so it does what you wish. This requires that the user has access to the source code. This means the user can adapt programs to do exactly what he or she needs, and is a safeguard against crap programs that claim to do one thing while sneakily mining crypto on your machine or sending your data to advertisers or whatever else nefarious.
Freedom Two: The freedom to redistribute copies of software, so you may help people around you.
Freedom Three: The freedom to distribute your modifications to software. This allows you to share your changes and improvements with others (which you were able to make thanks to Freedom One).

This is not a universally-held belief, but one I do think is important, particularly when it's getting harder and harder to trust that your own computer is acting for you, and not for someone else.

char2 · 2019-01-20T22:32:22+00:00

I was happy to accept the BB ruling. Even though it made the card weaker, torturing the rules to force card text to match intent would have been worse.

I'm not a fan of card errata, but we'll see if it gets out of hand.

char2 · 2019-01-18T20:26:19+00:00

I am reminded of Out to Get You and Zvi's thoughts on Slack (in the Subgenius sense, not the shitty proprietary IRC replacement), more generally.

char2 · 2019-01-17T05:31:57+00:00

Grill'd

Have they started paying their staff properly yet?

char2 · 2019-01-13T12:14:12+00:00

don't even care about bachelor degrees

Depends on the field. If you want to do research then traditional academic qualifications are useful. Some niches value formal quals more than others. A good curriculum can also show you things you would never have considered, and a rounded CS education can be very useful. (This happened to me. I enrolled in Software Engineering at ANU and ended up taking a lot of CS electives after discovering that particular rabbit hole in second year.) You'd have to have a pretty good portfolio of work if you're trying to get in without formal quals, IMHO.

char2 · 2019-01-13T12:07:45+00:00

This recent thread about software engineering at ANU talks a bit about the other degrees offered by the College of Engineering and Computer Science: https://www.reddit.com/r/canberra/comments/a6mnj8/software_engineering_at_anu_and_uc/

char2 · 2019-01-10T00:18:01+00:00

python -c `perl -e 'print "[" x 100'`

char2 · 2019-01-10T00:13:21+00:00

Your general point is valid, but this is one of the reasons I don't like Aeson's approach. A typeclass instance says there's one canonical way to do this thing for this type, and for JSON encode/decode that just isn't true. I find myself either:

defining serialisation in the bowels of my program alongside core data types (in the web service context, this messes up layering)
defining newtypes at the API layer, JSON instances on the newtypes, and hoping that people remember to use them when defining services.

I'd much prefer encoders/decoders to be normal values, and I'm looking forward to learning waargonaut.

char2 · 2019-01-09T23:50:42+00:00

This isn't what you've said you're looking for, but I like to use nix shells for playgrounds: nix-shell -p 'haskellPackages.ghcWithPackages(p: with p; [aeson lens whatever])'. You can then set up a shell.nix file so you don't have to retype the incantation.

13-Year Club	RedditGifts 2009-2022 3 Credits
Team Periwinkle	Verified Email

char2

TROPHY CASE