eddyschai

So in all seriousness a functor is a mapping from one category to another, and an endofunctor is a mapping from one category to the same category.

I have my first hour booked Thursday lunch (I took a few hours lessons in school as part of the Air Cadets but lost the log book). I've also started playing Flight Simulator. All I've managed to do there is wreck a few F-18s :( What planes are you flying? Something more realistic to your lessons?

Obligatory "Hitler reacts to Functional Programming"

https://www.youtube.com/watch?v=ADqLBc1vFwI

Maybe if I explain what a Monad is in Plain English it'll help you understand functors?

A monad is just a monoid in the category of endofunctors.

Not debating any of that; originally thought the comment above mine was wrong, looked at the stats, and found they were far closer than I assumed.

Probably not true, but only just. 570 men die of breast cancer each year in the US (latest stats from the Cancer Statistics Center) while 330 people have died in mass shootings in the US this year so far. You can see the stats, taken from the Gun Violence Archive, here: https://docs.google.com/spreadsheets/d/1xB5VWgcpvw5UrWYq-6so...

What class of languages are those?

What are failure domains?

I read this and thought, damn he sounds a lot like a PM I used to work with at IO. Then I saw the username ;) Hope you're doing well man - Ed

ORMs definitely don't help! In my first dev role I worked at a C# shop and everything was through Entity Framework. You can't take that skill with you if you change languages to Python, or Haskell, or whatever, but the core SQL skills to follow you around. It's worth the effort, I think (and it's not particularly hard to get semi-decent at SQL!).

Once you get general topics it's fairly trivial to pick up new frameworks/libraries to pump those APIs out. I'm not saying algorithms for the sake of leetcode!

Saying this, I was interviewing for several roles across the US and EU last April and had algorithm-based questions in almost all of them. So it's pretty useful for that reason too, even if I don't really agree with it.

Not sure what to really take from this article. If it's about what one should spend their time learning, try identify the 'timeless' things. Software design over languages, algorithms over libraries, SQL and JavaScript will probably never die.

You can do something with lxc - I had to use it instead of Docker on a Chromebook a while back. The wrapper isn't as nice, but it's not actually that hard to get going.

I found this pretty funny - read the docs while being totally excited and then saw my name second on the contributors list, I wrote a little code waaaaay back when Crosshair first started but completely forgot about it. Will definitely check out using it later today :)

They can, but most don't.

I found it pretty amazing the codebase that cracked 100T digits (and the previous records too) were started as a guys high school project.