bobm_db | 6 years ago | on: If the Moon Were Only 1 Pixel (2014)
bobm_db's comments
bobm_db | 6 years ago | on: Pika – A JavaScript package registry for the modern web
I like to do some Javascript coding with my son on his Chromebook, and having a development environment is a hard problem for us to solve for some reason.
Having a webpage that just spins up VSCode and allows us to publish and test in a registry might be just what we need, no?
bobm_db | 6 years ago | on: Tesla Cybertruck
_Everyone_ is going to see this, have an opinion on it, and want to know what everyone else's opinion on it is.
bobm_db | 6 years ago | on: Giant Molecules Exist in Two Places at Once in Quantum Experiment
Then the two realities interfere with each other to form the probabilistic pattern at the detector. So, according to MWI, reality has "merged" again?
If we accept the mulitiverse idea of MWI, doesn't that mean at some point particles aren't able to marge with their branched-reality versions?
bobm_db | 6 years ago | on: In 2027, at least 7 out of the top Tiobe languages will be Tree Languages
Isn't Python a tree language? Whitespace is significant...
How about YAML?
bobm_db | 6 years ago | on: No Silver Bullet (1986) [pdf]
bobm_db | 6 years ago | on: Coding Bets
The big one seems like some massive accumulator bet, which is really unlikely to pay off, whereas one of the smaller parts may just have an impact on it's own...
bobm_db | 6 years ago | on: Things I learnt the hard way in thirty years of software development
> Documentation is a love letter to your future self
This seems like a brilliant way of transcending what feels like a drudge-job, making it into something really meaningful.
bobm_db | 6 years ago | on: Consuming Hacker News
That way I could dive into specific comments on topics that interest me, and also decide which comment branches to follow.
I have no idea how this might be implemented though.
bobm_db | 6 years ago | on: Consuming Hacker News
bobm_db | 6 years ago | on: Consuming Hacker News
bobm_db | 6 years ago | on: How fair do you think time estimate within 30% is? Plus/minus 20% if over 3 days
Problem is, time is just _one_ variable. It's possible to hit every estimate spot-on, if you allow the other variables to change wildly (number of bugs, completeness of features etc). It's kind of like in quantum mechanics, where by knowing one property of a particle, you have to let go of all the others (maybe).
Anyway, I blogged about this a lot here, if it is any use: https://riskfirst.org/Estimates
It seems wrong-headed to be insisting on this, so maybe education is the answer?
Which, it turns out is really, really slow. Big revelation to me!