Engineer on finagle, used to work at tumblr when we started running into problems with finagle. In large part it was because we didn't understand how it worked, and were doing things like reinventing different pieces of finagle, like load balancing and service discovery.
I think saying colossus is "significantly better performing" is a bit of a stretch, although I haven't seen it in the past year, I think the main win was that you called epoll faster than netty, which I think was because you were using a faster timer. What are the performance comparisons you've done recently?
This is good advice. Another good tool to better yourself is reading code. This lets you think about why people have written code the way they have, and whether you agree with how they did it.
I have also had this happen to me--I am part of a fairly large company on github, so this means that suddenly I don't see anything in my strema except for posts about that company, so I had to unwatch nearly everything in it, which I would rather not have to do.
It seems like you get most of this stuff from a basic abstract algebra course. How does category theory help me beyond what I got from modern algebra 101?
edit: this is from the perspective of someone who knows a little abstract algebra, and wonders if it would be sufficient to brush up on my algebra to get these ideas, which seem a little familiar, or if category theory is really important to get these ideas. I'm not trying to be a contrarian.
I had a similar experience, where I found that none of my computers, neither my six year old laptop, nor my one year old laptop (!) could support GNOME 3, which has essentially prevented me from upgrading my fedora from 14. Since Fedora is currently on version 17, this makes me sad, and ruminating about which OS to jump ship to.
Yes, for example Foucault or Derrida is not meant to be skimmed, and part of the point of reading Hegel is to struggle with it. It doesn't make sense to make the reader struggle with an opinion piece, since you are generally trying to persuade someone of your opinion. Although opinion pieces don't necessarily follow the traditional lede + nut graf format, this one appeared to do so, until the actual content was different from the first few paragraphs.
GQ prefers short Anglo-Saxon words because they think it's a style that men prefer to read, and what I am trying to say is that using too many words that were imported from French is generally used to make people sound smart because it was once the language of bureaucracy, but generally makes things harder to read.
Consider, "I don't even know what you're trying to say here. I mean, I can guess, but it makes me queasy." This is an extremely clear sentence, and would be pretty similar if translated into Middle English. This is generally the argument that Orwell makes in Politics and the English Language.
I was skimming this article and thought that the premise was that first person shooters were switching to using the up, left, right, and down arrows instead of wasd. I felt the lede + nut graf (was there even a nut graf here?) was misleading--it was completely about the buttons, not about the identity of the gamer, the game industry, nor society in general.
I am interested in articles about female gamers and how they deal with the unpleasantness surrounding the gaming industry, but I wish that blog posts were held to a slightly higher standard--I am a fairly fast reader, and had to double back to reread large parts of the article to recalibrate as the article started talking about being directed to games with fuzzy animals and facebook games instead of shooters, when I expected the author to be complaining about the wasd keys opening different menus rather than moving around the character.
This seems to be a pretty good argument for paying for better quality journalism. I bought a copy of GQ, not exactly the highest brow magazine in the business, admittedly, and the articles weren't riveting, but it was efficient to read them, because they were written carefully and in the traditional journalistic style, with a lede, nut graf, and transitions. Furthermore, it's a magazine FOR MEN so most of the words were Anglo-Saxon and avoid the errors that Orwell rails against in "Politics and the English Language." I never felt like I was being jerked from one idea to another, and I understood the point of the article if not from the titled or the images associated with it, then at least from the first few paragraphs.
TL;DR: May there be truth in advertising, if bloggers can't write a proper lede, we will have to pay for news.
Using a language with static typing means that there are a lot of tests you don't have to write. Do you remember the units trick from physics? If you forgot which equation you're supposed to use, keep on using identities until you're in the units you're supposed to be. Static typing checks that your units are correct for free.
I generally disagree with what this guy is saying. This is reasonable from the perspective of, "How to pitch yourself to a non-technical founder."
A. Programming languages do matter. Talking to other programmers, a good way to find people who actually love programming is to ask people what languages they use. People who have experimented with haskell or clojure are usually people who love programming more. PG has a good essay on why it makes sense to start a startup based around an esoteric language. I know for a fact that Jane Street uses their heavy reliance on ocaml as a recruiting tool. Your life will be much, much easier if you can hire better programmers. Hence, the startups with the really good engineers will want to know what programming languages you know. So yes, I agree that resumes are not that interesting, but also, programming languages are useful indicators for certain kinds of employers. The recruitee's github should reflect this. [1]
B. Sending links to apps or websites is all well and good, but as another commenter said, for some startups, it is basically useless. If you are trying to be the CTO of a company like 10gen (their CTO is a co-founder, but bear with me) you will want to know about their systems skill, not how pretty they can make a website. Backend talent, or understanding of algorithms is something you absolutely cannot get from this.
So at startups where backend technical skill is not highly valued, and the founder is very non-technical, this might be useful. If you are trying to work at a Palantir or a DropBox, you should probably ignore this advice, although admittedly, both are much further along than this guy is thinking of.
I agree, writing Java without powerful refactoring tools is a bore--that's why it's great to use Eclipse's "Generate Getters and Setters based on Fields" refactoring tool.
Interestingly, I've never really felt the pain of not having a good REPL for java, although I often use it in other languages. Although Java isn't interpreted, unlike the other languages you mentioned, Scala is both interpreted and compiled, so it's not a great argument for why it doesn't have a good REPL. I think eclipse's very strong autocomplete somewhat obviates the need for it, because I know that I mostly depend upon bpython/ipython for the easy access to docstrings and information about arguments.
I wonder if part of the reason why I've never felt the need for a REPL in Java is simply because there isn't one built in, so it isn't a tool that I ever reach for. REPLs are great for prototyping, and for learning, but I've found that the more I learn about a language, the less I tend toward using the REPL, so perhaps it's simply that I got used to being able to edit my code instead of having to type it all in again.
Interesting. My experience with Java is that the only thing that gets in the way of programming in Java is the verbosity, which an IDE with powerful refactoring tools (eclipse, IDEA, eclim) gets around nicely. I would argue that in many ways, Java is easier to program in than a lot of other currently hot languages because there is so much tooling around it (although I would trade basically any python package manager for ivy any day), it is statically typed, and its behavior is generally boring but extremely predictable, and not hard to reason about, excluding the threading library which is not super fun. What have you found is frustrating about using Java?
If the point is to learn front-end development, it seems like you're still sticking to your strengths instead of challenging yourself and delving into actual front-end DOM manipulation stuff.
I wrote something vaguely similar a while back, I imagined it would be useful in a hackathon context for people who had never used git before. The biggest problem was that it doesn't help people understand git, whereas all of the regular git commands fundamentally make sense if you think about the way it's implemented, and also lead you toward and understanding of git.
My version was called jerk--it is a little meaner than git, and supports operations like "undo".
The idea of encouraging the term of "man logic" is man logic. Misogyny is clearly a problem, but saying, "oh but men are dumb too" is not the right way to go about fixing it.
I was about to ask this question. I also can't figure out if the powerups stack or if they're distinct. I wonder if it's possible to win if you get all of the powerups without dying.
I think saying colossus is "significantly better performing" is a bit of a stretch, although I haven't seen it in the past year, I think the main win was that you called epoll faster than netty, which I think was because you were using a faster timer. What are the performance comparisons you've done recently?