you can build it and simply use it in your own office? There is no need to shout about it if the cost of writing software goes to zero (but the value remains non-zero!).
i agree; but perhaps also it is the difference between managers and SWE? The former (SWE team leaders included) can see that engineers aren't perfect. The latter are often highly focused on determinism (this works/doesn't) and struggle with conflicting goals.
Through a career SWEs start rigid and overly focused on the immediate problem and become flexible/error-tolerant[1] as they become system (mechanical or meat) managers. this maps to an observation that managers like AI solutions - because they compare favourably to the new hire - and because they have the context to make this observation.
i used to do lots of graphics, and love these bugs. They give an enjoyable insight to the development process and algorithms as the progress through a project!
My old supervisor wrote a book on computational socialism back in 93. I rather like some of the ideas (can a participatory centrally planned economy work now that we have internet/cybernetics?), but suspect it wouldn't work in practice.
fantastic book. Made me consider the question of whether consciousness exists at all or if it is just some hack by evolution to allow introspection.
I haven't found a definition of consciousness which is quantifiable or stands up to serious rigour. If it can't be measured and isn't necessary for intelligence, perhaps there is no magic cut-off between the likes of Dall-E and human intelligence. Perhaps the Chinese-room is as conscious as a human (and a brick)?
Other causes include the pressure to publish quickly in ML (while your approach is en vogue), with small teams, before your funding runs out, while hitting conference deadlines.
In these situations, I have suggested releasing anonymous implementations after the paper is accepted just to get the code out there. I am not certain this is the right thing to do!
Academics are judged by the publications not their implementations, so the system favours over-sold manuscripts and it-ran-once implementations. Until funding is conditional-on (and provided for) robust well maintained code it will remain challenging to get reproducibility.
Frequently the PIs (bosses) will not even glance at the repositories written by junior members, probably can't read code anyway, and certainly won't allocate time for their maintenance. Even worse, most academics who do publish code have never been exposed to real world software engineers, their techniques, or tools.
Look awesome - I've been looking for some hackable code like this to present my photos from google drive. Cheap photo hosting from google + minimal load on my server...
a counter point: when cycling in London you have to be aware that 30% of the time there will be be a vehicle stopped the protected bike zone in front of the lights...
I guess I was thinking that a good way to simplify many video UIs would be to remove these buttons. Perhaps the browser-esque way of providing this functionality would be to use bookmarks instead?
Goal was to create a platform for sharing user video that would otherwise be too awful to watch. By dropping length, but increasing variety, it's easier to create something like to watch...
It's always slightly surreal to see your employer on the front page of hn, even more so when you find you find your colleague making the second comment.
It's easy to imagine EC2 expanding beyond 1U servers and databases to GPGPUs, FGPAs or quantum cores. There's a lot of potential for a gpu cloud - from quick rendering (xtraNormal/nVidia Gelato) to scientific computing (Larrabee?).
I do believe in intelligence (which is measured against a particular task) and ego (which inflates the self over the other).