945 karma · joined February 12, 2011
[ my public key: https://keybase.io/niksko; my proof: https://keybase.io/niksko/sigs/4_K48wgjxKBXyJFpmjrvHFlKOAJVWwd3S-VbG3-S6Ng ]
The first is that I feel that text is an AWFUL medium for communication for these sorts of discussions and criticisms, unless expertly crafted (as this article was, I feel). Numerous times I've had arguments with friends via text that get out of hand because of subtle misinterpretations of intent and phrasing, where as in person they're much more civilised. You can draw a few conclusions here: either we suck at communicating via text and need to get a lot better, or discussions of this nature are better had face to face, where intent and nuance of expression are easier (for many) to judge. What feels like normal discourse and 'clinical' (for lack of a better word) discussion to you may not feel the same way to others, simply because short-form text is an imperfect medium.
The other point of contention I have is that it's fine to treat diversity programs with scientific rigour, but you also need to allow for the proper timescales in which to study the effects. If you subscribe to an intersectional feminist viewpoint, then it stands to reason that you need to observe the success or failure of such diversity programs over a generational timescale in order to assess their efficacy. Change on that scale simply isn't going to be visible over a one or two year period before you decide the diversity program doesn't work and you axe it.
> Because contemporary moral codes delineate women as vulnerable or marginalised, we stop seeing them as individuals with unique talents and idiosyncrasies, but as representatives of a victimised class.
I think labeling or delineating women as 'vulnerable or marginalised' and ignoring their unique qualities and idiosyncrasies is robbing Peter to pay Paul. Acknowledging that women are 'vulnerable or marginalised' shouldn't remove their individuality, you can easily have both, but that's beside my point here)
I legitimately didn't realise what the tone or conclusion of the article were going to be when I first started reasoning, because it does a good job of presenting scientific research without any inherent judgements. The other thing this article achieves that the cited manifesto failed to achieve was not to necessarily provide judgement, criticism or suggestions around 'what should be done about problem xyz'. It presents some facts, presents some opinions, and then (thankfully) doesn't decide to rip the hard work of well intentioned people to shreds. And for that, I think this should be commended.
So yes, there will be GTFS formatted timetables for Melbourne, no real-time though.
"The big guys won't go for it. Therefore, it won't succeed". That's a recipe for somebody who isn't a "big guy" to start their business literally this instant, and outcompete the "big guys" in five years because they were able to throw off the shackles of tradition and learn from the past as well as embracing current technology.
Perhaps the focus is wrong. Perhaps it's not the 'technical' part of the technical interview that causes this disparity. Perhaps it's just good ol' fashioned racism or prejudices, and really the part of the technical interview that causes a disproportionate number of white males to be hired is simply the fact that the interviews happen with the interviewer fully cognizant of the applicants race and gender. You'll notice that the article also mentioned their disdain for being able to see the applicant.
To dismiss a fact that reasonably straightforwardly follows from empirical evidence and limited options for causality is simply obstinancr.
Everything sucks if you do it badly.
What they're saying is that you can take a JPEG compressed image, decompress to raw pixels, and then recompress with JPEG more efficiently (if you're careful, no specifics on how this is done), and you save space.
That's why they mention that they're doing it very carefully, because you've got to make sure that when you decompress the new optimized image that it pixel for pixel matches the original decompressed image.
My standout is the battery case they released a few years ago. The design of that case is just unspeakably hideous. They need somebody with a Jobsian level of ruthlessness, attention to detail and unified vision to steer the ship back in the right direction. Another example here would be the fact (mentioned in this article) that they effectively copied the rest of the market by providing a larger phone. The Apple of old didn't do this. They didn't really follow market trends, they started them. And then to be flummoxed by demand when people responded so positively to smaller phones is baffling to me.
I wouldn't be surprised if we see some C level leadership changes some time this year.
Without fuzzing, it's going to be pretty difficult to come up with enough test cases to thoroughly test a regex.
Why not wait until the game was much more polished and had many more traditional Pokemon features before release?
Nobody will be playing this in a month unless Niantic are really really fast with the content updates. Like, one per week fast, until it's much more deep than it currently is.
EDIT: Now it's saying somewhere in North America
Linux support was reasonably good, though with bizarre quirks and changes of tooling between libbluetooth versions. OSX was a total nightmare.
The project is currently stalled because three days before I had to head off (I was doing all of the programming and troubleshooting on the software side) my collaborators decided to inform me that they would be using a different laptop to what they'd been using for the rest of the project, and when we tried our software with that version of OSX and hardware, it refused to work nicely. We eventually came up with a bizarre pairing ritual that involved removing devices, then quickly adding them, and in a specific order, and then that mysteriously stopped working and now I don't have access to hardware to fix it.
Knowing what I now know, if I'd had my time again I would have recommended ESP8266 based boards instead of the LightBlue Beans we were using. Even though one of our requirements was low power usage (which we certainly got through Bluetooth 4), it probably would have been less hassle to just make the WiFi modem sleep for a period and then transmit in bursts.
a) somebody in the group buy has the technical skills to do a proper drawing, or b) you can spend a tiny amount of money to get proper drawings made.
I mean, it worked out in the end. But it seems like a giant case of Dunning-Kruger to think "Well I don't know how to make technical drawings, therefore photoshopping an existing drawing shouldn't present any problems".
At first I used a boilerplate (in fact I think it was a previous version of this one), but it felt like I was jumping in the deep end. I didn't know what anything was, I didn't understand the configuration or the setup, and nothing was making sense.
So instead I decided "I'll start from scratch, introduce dependencies as I need them, and I'll actually understand what's happening". But then as I started to try and introduce dependencies and pieces of the toolchain and stack (Babel, GraphQL/Relay etc.) and that was a whole different type of confusing. I found it really hard to follow tutorials unless they were written for EXACTLY the stack I was using, because small changes seemed to radically change how I had to go about things.
How do you start? Both situations seem perilous. Bottom up is really difficult unless you follow a tutorial that exactly matches your stack. Starting with boilerplate means that if anything breaks you have no idea how to fix it or how anything works.