This is similar to how wild boar was hunted in Europe - there were special spears made with extra crossbars to reduce the chance of a boar reaching the spear holder after being impaled.
to those unaware: 11 is the laughing taunt in aoe2 and is used in the community like lol. the poster above was describing how you hunt a boar in aoe2 which is a vital source of food in early game. it is risky to use your towncenter to weaken a boar because if you kill it with the towncenter you can not harvest the food
Thanks, I think that's a style/level of in-joke that needed an explanation for the wider audience. Particularly since the first arrow-part sounds almost plausible. (And "11" on its own is unlikely to give many useful hits.)
I’m surprised that this doesn’t get talked about more - I’ve worked with plenty of women, minorities, and immigrants at large tech companies, but I can’t recall a single person with a southern accent.
I recently worked with a guy from the south who had a wicked accent. I could understand him because I spent time in the military and one gets used to all kinds of accents, but no one else could understand him. He was pretty smart and I’m sure he will do fine, but his accent definitely got some mean comments. I told a few people to knock it off because he didn’t deserve them.
The other obvious missing part is African Americans, especially for tech roles. I'd be shocked if more than 1% of SDEs at FAANG are African Americans. The biggest social elevator of the past few decades and they're completely cut off from it.
I wouldn't frame it as "cut off" as much as it is "unknown unknowns."
If you don't have family/close friends in this industry and don't have any resources or the wherewithal to help you/yourself break into it, then you're kind of SOL.
I think that you should mention that this is specific to 90 degree v8 engines - other engine designs can have similar crankshaft / firing order trade offs but would not be described as “flat plane” or “cross plane”.
That’s not their best hardware deal, but you also have to understand that you are paying for rack space, electricity, bandwidth, on-site staff for repairs, etc. They are actually absurdly inexpensive compared to competitors.
Fair, I looked at their other offerings and saw current gen specs at competitive rates - in that case we are agreed that's a lot better than most others.
The piano is not the canonical model of a scale - it’s just a bit more visual than some other instruments. I went to music school and primarily play guitar and violin but can sort of play some keys. I could definitely figure out pretty much any scale on a piano but couldn’t just sit down and immediately play most of them.
People underestimate the performance cost of 4K. The step from 720p to 1080p was a mere doubling of pixel count, but going to 4K was another 4x increase.
The choice of a relatively low screen resolution is one of the main reasons that the deck can run modern games so well.
There’s still basically one with a couple storage options - they have shipped with different fans though. My (fairly recent) unit has very reasonable fan noise.
Remote: Prefer to work in-office, but would consider remote opportunities.
Willing to relocate: Possibly, for the right opportunity.
Technologies: Linux, Python, Rust, C, Kubernetes
I have been working in SRE/infrastructure roles for the past 13 years at employers including Google, Facebook, and several smaller companies.
I am interested in both SRE-type positions and roles developing systems software. I'd especially like to work with rust or on open source software.
My job search started a few days ago so I don't have an updated resume yet, but my work history can be found on my LinkedIn:
https://www.linkedin.com/in/markatto
I had very mixed experiences as a customer in ~2009 - it was definitely possible to get through to someone very competent, but it was pretty difficult. We were trying to use their "cloud" VPS offerings (I believe it was openstack-based, and I liked the idea of supporting something more open than AWS), which were extremely buggy (for example, we had to default-retry every api operation multiple times in scripts because pretty much every type of call failed 40% of the time.) I generally had better success getting information about outages by reaching out employees I knew on freenode than I did through official support channels.