51–60 of 65 posts
Earlier quoted context omitted.
> This role is based in our new office in Bielsko-Biala, Poland. Out of all the places in Poland, this choice is pretty strange. :)
Isn't it right next to the largest agglomeration in Poland? Also close to two (maybe three) other countries connected via highways?
Earlier quoted context omitted.
[flagged]
Please don't post unsubstantive comments like this on HN. You've been here long enough to know we're trying for something better here. https://news.ycombinator.com/newsguidelines.html
Earlier quoted context omitted.
>A single job posting for an engagement team A single job posting for an engagement team in Poland.
A person from Poland here: why does the country matter here? What are the implications you're implying?
Apple is unusually centralized (they don’t even have different business units; the company has a single balance sheet at P&L) and corporate level decision making is pretty much all done by the same small team at the mother ship.
So while all sorts of decisions are made locally, a hire outside Cupertino (which all of Poland happens to be) is extremely unlikely to signal a corporate shift.
Even a job ad for a role in Los Angeles would be equally unlikely to signal such a shift.
That tells us nothing, nothingburger speculation. However, Apple had that major incident in its history when they made Adobe mad when they went out and shopped for final cut pro, color, and a handful of compositing apps. Didn't turn out well for Apple at the time.
"MotionVFX, a Warsaw-based company"
Earlier quoted context omitted.
Please don't post unsubstantive comments like this on HN. You've been here long enough to know we're trying for something better here. https://news.ycombinator.com/newsguidelines.html
I disagree. It was relevant, succinct, and meant to inspire introspection leading to positive change.
That tells us nothing, nothingburger speculation. However, Apple had that major incident in its history when they made Adobe mad when they went out and shopped for final cut pro, color, and a handful of compositing apps. Didn't turn out well for Apple at the time.
Was that as mad as when Adobe didn't believe Apple when they said to switch to 64bit so they didn't because FCPStudio wasn't updated to 64bit only to have Apple release FCPX instead causing Adobe to miss an entire upgrade version on Mac? (you should read that run-on breathlessly as intended)