Some shots I took of the various booths my colleagues set up at WordCamp US. I love the creativity on display here.
WordCamp US has been great.
I find myself hitting the screen capture button fairly often in this game, which is kind of nice. It gives me a record of what I’ve been doing and the things I’ve been messing with in the game.
My son and I are still playing together almost nightly, and it’s been a lot of fun. And we recently joined SafeGamers, giving us some groups we can play with who are respectful of our time and of us—a welcome change from a lot of online gaming experiences.
I’ve managed my first Destiny series raid, and cleared it a few times since then. I expect fewer screenshots next month, if only because I’m exhausting a lot of the content in the game prior to the first DLC release coming this December. (And I included the Legacy screenshots, which showcase some pretty neat art from various experiences I completed in the first game. I’m hoping my next Legacy is much more complete.)
Also, I’m aware there are some resolution problems with the carousel for these images; if you want to see the (much sharper) originals, use the button that appears when you are browsing the images in carousel.
My summer vacation has started, which usually means it’s almost time for Summer Games Done Quick. GDQ is a twice-annual speedrunning marathon, and each one lasts for a week. The summer one tends to be my favorite; the runs can be a bit more laid back and the charity is preferable to the one they use for the winter marathon.
Keep in mind when watching these speedruns that many of them will involve the players going through the game in ways you haven’t in the past. If a run doesn’t call for glitchless or other restrictions, you’re likely to see things done to intentionally break the game and skip large amounts of the actual intended gameplay. This takes some getting used to and can look really weird the first time you watch a run for a favorite game.
That said, if you just relax and watch some people play games while using quite frankly amazing execution, muscle memory, and crazy amounts of practice, you can have a pretty good time. I suggest you find games you have played and liked on the schedule and trying to watch those to get started.
If you aren’t sure, here are some runs I think are likely to be great this week:
There’s plenty more I could have put in here, but these are the things I’d suggest to anyone who asked me about GDQ and what they should peek in on.
I hope you watch and have some fun doing so. Please consider donating to the event!
I’m fortunate to work at a great company that refreshes our laptops with new tech every couple of years, and today was MacBook Christmas for me: my new Touch Bar MacBook Pro showed up.
Whenever I do a laptop refresh, I choose to install everything new instead of using a system transfer, specifically so I can reevaluate what apps I use, whether there are other options available, and find new things in those apps’ settings that I might not have seen before.
As part of this process, I’m going to do a series of blog posts showcasing the apps I use on a regular basis and explaining why I choose to use them and how they fit into my personal workflows.
Once I have them going, I’ll post a link to the archives here, but if you’d like to know when I post them, feel free to follow my blog. :)
I get about a half-dozen emails a year via my contact form asking me this question or asking related questions, like how to craft a resume, or what it’s like to work at Automattic. I thought I’d jot something down so I can just send a link the next time this happens, as my advice hasn’t changed much over time. :)
I’ve been here for seven years as of this writing, so I thought I’d share what I tell people who ask me this question (in a slightly expanded format). I’m not involved in hiring. This is not “official” advice of any kind. It’s just what I say to people, made public and repeatable.
First things first:
I will extol the virtues of my job whenever you ask me about it. It’s the best place I’ve worked, and I have found it to be very rewarding.
Not everyone will feel this way. The amount of freedom we have to get or not get our jobs done is unlike anything else out there. It can be very isolating and lonely to not see your team in person more than two to three times per year. I think even those of us who have embraced what we do struggle with this from time to time, and for some it can be significant.
But if you are willing to engage without having to be asked to do so, love working with people who are intelligent and come from all walks of life, and are down with being challenged often, you’ll probably fit in well.
So, how to get a job here? Let’s talk.
You can find Automattic’s open positions here. Take a look and see if you spot something you’d enjoy doing and think you can do well. Read the job description and requirements to make sure you understand them and know how you would theoretically fit in the role.
Now, take a strong, focused look at the part of the job listing that talks about how to apply. This is going to be very important. :)
There are some things you will see in every job listing regarding how to apply. Take note of them and follow them. They are not there at random. Basically:
You might get a trial; you might not. But putting yourself out there is the first step.
(Oh, and if you don’t know about how our hiring works with the trial process, where you perform contract work to see how that goes, you should probably read about that.)
I’m not lying when I say that’s pretty much it. When you boil down the process of applying for a job here, it’s pretty simple. That said:
Again, let me stress this is my opinion and not in any way “official.” Nothing I say here is even remotely a guarantee, and I don’t have anything to do with hiring (really, I don’t), but these are things I will usually recommend to someone when they ask me personally what they can focus on.
These are mostly things I really like to see or admire in people I work with. :)
It’s totally possible you’ll be rejected for the job, either before or during the trial process. When this happens, you may receive some reasons why you were turned down. Or you’ll receive some constructive feedback during your trial. Be open to it. Embrace the idea that you don’t know everything, because believe me—as a full-time employee for many years now, I still realize this often.
I applied to Automattic three separate times over a year-and-a-half before I received a trial. I had to change focus mid-trial before I was hired based on feedback. Some of the best colleagues I have at Automattic went through a trial, received feedback and a rejection, and then trialed again later with success. If and when you receive feedback, take it to heart and then apply it. Or apply again. Or both. :)
I would rather work a million times over with someone who is willing to admit when they don’t know something or are stuck on something and ask for help than someone who tries to fake it. Admitting you need help is not a weakness. It is literally impossible for everyone to be an expert at everything.
I’m big on leading by example. Everyone has gifts and strengths, and everyone is at a different level. Just as you should be willing to let others help you, be willing to share your knowledge and experience with others. Be kind and instructive. Don’t always offer to just take charge of things—though on occasion, that’s necessary—but aim to level up your (potential) team.
Automattic contains the most diverse and interesting group of people alongside whom I have ever worked. It is an amazing collection of individuals from whom I have learned much and with whom I have enjoyed spending time during meetups. Embrace this and be willing to commit yourself to it as well. (BTW, if the real you is introverted, that’s totally OK. There are lots of us here. If you have to take a break, we understand.)
How much of this depends greatly on the job for which you are applying. Some positions might not require a lot of PHP or familiarity with WordPress. Others will be based almost entirely around this. I think it’s a good rule of thumb to at least know the core business of Automattic and what we do before wanting to work here. :)
An open source ethos drives Automattic and is core to our identity. Know what that means. Past and ongoing contributions to open source projects, whether it’s code, testing, design, documentation, or whatever, will give you valuable experience in what it’s like to work with those types of projects and is a bonus.
(Again, this will somewhat depend on your desired job role.)
To be honest, I still have trouble with this sometimes. Text communication is hard. Without vocal inflections, facial expressions, and other body language, it’s easy to read something and get the wrong impression.
It’s a skill to craft your text communication in a way that others will understand your tone and intention. Dedicate yourself to learning that skill. (Yes; sometimes this means using emoji. They are very, very helpful for establishing tone.)
I’m sure there are things I’m not thinking of, but I have been writing this blog post for three days and I should probably just publish it. If you are a fellow Automattician and reading this, and I forgot something obvious, ping me and let me know. If you are a reader and you have additional questions, feel free to contact me. I’ll edit some things in to this post later if needed.
I will never stop learning. I won’t just work on things that are assigned to me. I know there’s no such thing as a status quo. I will build our business sustainably through passionate and loyal customers. I will never pass up an opportunity to help out a colleague, and I’ll remember the days before I knew everything. I am more motivated by impact than money, and I know that Open Source is one of the most powerful ideas of our generation. I will communicate as much as possible, because it’s the oxygen of a distributed company. I am in a marathon, not a sprint, and no matter how far away the goal is, the only way to get there is by putting one foot in front of another every day. Given time, there is no problem that’s insurmountable.
I’ve actually never played this game before, but this tournament(?) of matches for an (I’m assuming relatively) obscure Neo-Geo title with the timer set to only one second is beautifully insane:
A port of the title to PS4 was released last week, and you can buy that here for $7.99.
It’s been confirmed the one-second round timer is possible in the port:
Mystery game tournament runners: you can set the round timer to one second in the PlayStation Network version of Galaxy Fight. pic.twitter.com/fy2YO3ZM6Z
— Ian Walker (@iantothemax) May 3, 2017
If anyone knows any of the other rules that were used in the Japanese tournament video, let me know; it looks like it’s at least set to Level 1. I’m not sure there are any other settings that matter. :)
I was messing around with doing some (very early) work with NodeCG tonight.
(It’s not going well so far, but that’s because I’m generally clueless.)
While doing this, I considered the idea of fighting game overlays that could be used with a “toggle” for whatever game is being played (or even key off an external API like Challonge). I then realized that it is really useful to have static reference images for various games to make sure you are not putting overlay images in bad places.
This has a lot of utility even for setting up OBS or Xsplit, because you can add the image as a background and then maneuver your layout stuff as you need to make sure you are not obscuring any screen items, especially meters.
I’ll put this behind a more link just so casual visitors to my site don’t get hit with OMG WALL OF IMAGES. If there is a game that is not represented here that you would like to see, or I have made a mistake, please drop me a note and let me know which one. I’ll see if I have it and can whip up some images for you.
All HUD elements are in default locations.
Click on any image to view as full-size.
You can also download a ZIP archive of all current screens. If you stream large events with regularity, please contact me and I can give you access to a Dropbox share of these images. If you want to know when I update the screens, you should follow me on Twitter.
Use the images to do cool things with your streams. :) If you find them helpful or useful, please consider dropping me a tip or just following my Twitch channel where I play games poorly.
This year’s Extra Life marathon was another great time. I spent some time playing games with my kids, had a great co-op session with my best friend, and generally enjoyed the 25 hours of video games (with some breaks!) while fundraising for St. Louis-area children’s hospitals.
To date, you have helped me raise just over $700 for this cause.
For that, I thank you all. Your support every year when I do this crazy thing means a ton to me and it’s good to know you are interested in helping with this cause.
And know that it’s not too late! You can still donate to this year’s campaign by going to this page and giving what you are able or moved to do:
I fell short of my goal, but that’s OK. It’s the effort and your assistance that counts. :)
I’ll be working on some additional stream stuff and a different kind of donation goal starting later this month. I’ll be posting about that soon. :)
Howdy! I just finished giving this presentation at WordCamp US 2016 about code review: about why and how you should do code review on your projects.
Here’s a SlideShare embed of the presentation deck:
I referenced a bunch of things in my talk and mentioned that you could find those sources in this post, so here’s the list in the order you’ll run across it in the presentation:
If you have any questions, comments, corrections, or whatever, please contact me. I’ll be happy to hear from you.