hotBacteria

5 ms·

1.
by hotBacteria 3y ago
I don't have much hope regarding this issue. Researchers work a lot on their own time, so the millions mentionned in the article don't directly impact the institutions employing them. They are alone in this fight. The petition ( h
2.
by hotBacteria 4y ago
What is demonstrated here is that if you understand well the different parts of some code, you can recombine them in more efficient ways. This is something very good to have in mind, but it must be applied strategically. Avoiding "clea
3.
Airshifumi: Play rock paper scissor using your webcam, with WebGL and TensorFlow(airshifumi.hands.agency)
1 points by hotBacteria 6y ago|1 comments
4.
by hotBacteria 6y ago
This twitter thread from the author provides insight about how it was made: https://twitter.com/LodsDorian/status/1349291334759288832
5.
by hotBacteria 7y ago
I like the shapes problem because I actually encountered it and it made me think. I'm not sure about the switch approach described in the post: function area(shape) switch shape.type case "square": return shape.
6.
by hotBacteria 7y ago
Two points not mentionned: 1- The question of access: A theorical exhaustive map of the brain would be easier to access than an actual brain. 2- Tools: A map is not a piece of paper anymore. A 1:1 map of Earth doesn't seem absurd, as l
7.
by hotBacteria 7y ago
You can write it without resorting to one-line conditionals: if(cond1){ myVar = 1; } else if(cond2 && cond3){ myVar = 10; } else if(cond2 && !cond3){ myVar = 100; } else { myVar = 4; } But
8.
by hotBacteria 10y ago
Just to add a bit of context, this article was written more than six years ago: http://thecleancoder.blogspot.fr/2010/08/why-clojure.html
9.
by hotBacteria 11y ago
I found this document : https://github.com/kriskowal/q/tree/v1/design very helpful to understand how promises work behind the scene Also liked being able to access the author's reasoning and the mot
10.
Does JavaScript Software Embrace Classes? [pdf](aserg-ufmg.github.io)
6 points by hotBacteria 12y ago|3 comments
11.
by hotBacteria 12y ago
Don't be stupid, be slow [1] We take shortcuts when we feel the proper solution takes too long to implement If you purposely take a shortcut, write why you take it, how you take it and how to turn back in case of troubles. Slowing down
12.
by hotBacteria 12y ago
The story ends well because the project was actually simpler than what it looked at first. Unfortunately, more than often, things happen to be a lot harder than expected What happens when, after 2 months of scribbling and playing space in
13.
Whois on any .fr domain displays “je suis charlie”(twitter.com)
130 points by hotBacteria 12y ago|14 comments