190 karma · joined January 23, 2019
A week later I finished something early and was instructed to not bring anything else into the sprint because, you know, visibility is more important than actually being productive.
I get that deadlines and metrics are important. And I get that managers/mgmt will never see eye to eye with developers about how long stuff takes. But this is just sheer idiocy, encouraging doing the bare minimum and a culture of fear instead of rewarding good work. If I actually told the next up the chain about it, they'd absolutely sweep it under the rug.
So yeah I'm interviewing looking to go somewhere way, way smaller at this point.
Also one of my friends just bought for the first time and he indicated it's expensive as hell. As a single person I'm not sure I want to get into that type of financial commitment when I have a sneaking suspicion the economy's about to collapse.
Like, I'm staffed at a company that isn't Arthur Anderson right now on an internal project and our SM/PO came back from scrum of scrums and said everyone was massively overestimating tasks to make sure they got them in on time. If you finish early you get pushback on starting something else because it looks 'so bad' if work goes from one sprint to the next.
Slow work and hitting metrics > everything, I guess.
So yeah. I like that. But what's the endgame? Is this high profile Battlestar reboot supposed to generate enough subscriptions to cover the cost or is it just getting people involved in the NBC / Peacock ecosystem? Like, this is the same company that routinely cancels (nearly) every good show on SyFy (where, you know, I would kind of expect a Battlestar reboot to actually be) because they aren't getting enough viewers.
Now that it's a streaming service and their collecting the money directly from the viewer rather than going through Comcast does it make that much of a difference?
They support the hell out of their game though. I just started playing again and there's so much new stuff to do.
Posts derailing this 'high bar' are posted semi-daily to Hacker News, no? It's a really big dilemma (extensive hiring process that weeds out good candidates due to time and frustration or take risks) and it makes it sound like it's just something, you can, you know, do on a Tuesday in your spare time, and then on Wednesday you can solve the architecture problem.
And that's pretty much this list summed up. It's nice on paper, and maybe it will make a difference if someone consults it when making tough decisions. Thanks for your effort.
I wrote it off at the time because reasons but to think that society, parents, or getting a low score on a single test would all but force them into a position like that is mind boggling. This was over a decade ago too, I can only assume it's gotten worse for a lot of people.
I can't see anything like this happening in the US because of half the country being red states that would be appalled at the thought of not getting married and having kids.
So they redacted that law then had to fast track an updated version of it a few years later when someone got arrested for taking upskirt photos and then it wasn't illegal. My cousin was an aide to a state lawmaker and had to explain to his boss what it meant at the time.
I typically won't do programming challenges. I don't believe it's fair for the applicant, because if it becomes the industry norm then applying for 10 jobs means 10 separate programming challenges just for the opportunity to get an onsite. But, recently, during a phone interview with a shipping logistics company with a common first name in their name, I vibed with the lead I spoke to and decided I would give their hackerrank a go.
There was an interpolate json feed into an object question. There was a semi-complex array sorting / manipulation question. There was a javascript quirks question. There was a sql question that I probably would have solved using both code and sql rather than just sql. The solution I came up with was using a temp table, that hackerrank permissions did not allow. The array question, my (working) solution timed out because one of the tests used an array with several million units in it. There was no indication of a certain time this should run under. It took about five minutes after submitting to realize a way that probably wouldn't have timed out, but at the time I was happy with my solution given the whole test was timed and I had written six lines of code to solve this problem.
The final question of the test, after all of these and a few I won't go into, was to write an html form field that updated a list via javascript and had alternating CSS colors. I was so frustrated that they would throw in something so very menial and time consuming after the rest of the (timed!) test that I didn't even attempt it. (to be clear, basic javascript knowledge had already been demonstrated on the prior fizzbuzz).
I had really thought my answers would grant me an onsite, but it didn't. So yeah, back to not doing stupid timed tests.
This was a month ago. The position is still open and I expect it to be for the near future.
If anyone read this far, I have given some thought about my various interviews after some interesting ones recently (another recent time at a .net shop I was asked to demonstrate sorting a list so i did a toarray() then sort and they were like no, do it manually).
I'm probably going to put together a blog about my interviews over the years since I've had all sorts. I feel like as deep as retrospective as I can remember over my decade of interviewing might give me some insight as how I should be better.
What are the odds that the US actually puts something like GDPR with the current campaign finance system as it currently is?