Why is AWS so opaque? Every time I run into a new awkwardly name service I have to parse some redundant management speak to figure out what it does. Does it really matter to anyone that their services have special names with words like "Simple"?

What. Setproctitle actually changes /proc/PID/cmdline? Who thought that was a good idea? Now a bunch of people at my "security" company think that makes the command line a safe way to pass secrets.

So a company sent me a "few days/hours" homework assignment (that conveniently uses their exact software stack) before even doing a phone interview. That's not cool, right?

If you are the lead developer on a big project, and you want your developers to not hate everything about this project, for the love of God please at least have a build server (it doesn't even have to run tests) and make sure your constant screwing around with Maven doesn't break the build for everyone else.

So is it just a standard thing, now, where interviewers get you to do a coding problem remotely on a shared notepad while they watch you over video chat? For me at least, it is the most uncomfortable style of interview I've experienced. I don't think I'll ever get through one :(

JSF: Yeah, we make it so can focus on what's important and you never have to write HTML or CSS like those lowly web developers.

Also JSF: You can't nest <h:form> components because nested forms are invalid HTML. Oh, that breaks the composite component you were trying to use? Ha, fuck off.

Primefaces: You know how you can just provide an ID and OverlayPanel will open on its own? Well, for a Dialog, the API is completely different. Here's a glob of JavaScript in an onclick event.

I swear this entire thing was regurgitated by a murder of seagulls.