https://militaryreadinglists.com/
Always looking for new material if someone spots one I'm missing...
406 karma · joined August 4, 2010
https://militaryreadinglists.com/
Always looking for new material if someone spots one I'm missing...
https://angrystaffofficer.com/category/star-wars/
One of my favorites is "Skywalker on Trial":
https://angrystaffofficer.com/2016/07/11/skywalker-on-trial-...
http://confreaks.tv/videos/goruco2014-what-we-can-learn-from...
So far the hardest part has been finding videos appropriate for the companion site - http://hitorerror.com/. I can't seem to hit upon appropriate search terms; I've tried "almost made the play up the middle" and whatnot.
In which case that start-up succeeding mostly by
not giving a shit about any actual business problem
and just hiring a group of excellent engineers.
But I think the acquisition amount in these cases will be small; maybe 2x? Anyhow, just enough to pay off obligations, give the founder a little money, and cover the costs of folding the acquired company.http://thomasleecopeland.com/2016/06/26/basicobject-is-a-ran...
I'm surprised that I haven't seen anything about that respond_to? change in the blogs; maybe I've just missed it. I might blog this, although I hate ending a post with "gosh I don't know about this one". Makes me feel like I haven't done all my homework.
The case I ran into was in a Rails 4.1 app where ActiveSupport::Duration (which subclassed BasicObject) was used like this: "rand(10.minutes)". That raised an exception in 2.3.0 but worked fine in 2.2.3. The fix was simple - "rand(10.minutes.to_i)". But still, I don't understand it.
$ ./ruby -e "puts RUBY_DESCRIPTION ; rand(BasicObject.new)"
ruby 2.3.0p0 (2015-12-25 revision 53290) [x86_64-darwin14]
-e:1:in `rand': undefined method `begin' for #<BasicObject:0x007fe0be4cb548> (NoMethodError)
from -e:1:in `<main>'
In 2.2.3 you get this, which I'd expect: $ ./ruby -e "puts RUBY_DESCRIPTION ; rand(BasicObject.new)"
ruby 2.2.3p173 (2015-08-18 revision 51636) [x86_64-darwin14]
-e:1:in `rand': undefined method `respond_to?' for #<BasicObject:0x007fa2d719bf78> (NoMethodError)
from -e:1:in `<main>'
It's as if rb_obj_respond_to changed... I don't understand it.The real beauty of it is that I don't bring a mifi card or anything like that, so I can't get online and read HN or whatever. Instead, if I run into an issue, I have to read the code of whatever I'm working on and experiment in the REPL to figure it out. So it's been really productive in a couple ways.
I wouldn't want to do it every day, since it makes for long days - but a few times a week it's not bad at all.
I recommend that book; lots of interesting anecdotes and some good explanations of the underlying materials.
http://news.slashdot.org/comments.pl?sid=7754987&cid=5019893...
Perhaps GitHub will be able to resist "change for change's sake".
This topic has been knocked around in Ruby-land for a while; I remember seeing Michael Edgar's LASER (https://github.com/michaeledgar/laser) static analysis tool including some work around optional type annotations, but seems like development there has stopped.
Right on. I see this at $DAY_JOB too; after a certain amount of cleanup and dead code deletion and whatnot suddenly things start getting implemented faster, small bugs are fixed more easily, TODOs and FIXMEs start disappearing from the codebase, etc. Good stuff!
Right on. I've seen discussions about feature toggles which suggested not using them because they led to an explosion of code paths. But that won't happen if you delete the toggle (and the toggled-off code) once the a/b test ends or the feature is rolled out or whatever. It takes discipline and a culture that encourages that by being willing to review / deploy those changes, though.
That said, I'm protesting too much; you're right and I won't submit any more links to there.
That book made it into four different reading lists from various branches of the military (USMC, USAF, Army, and a chair of the House Armed Svcs Committee). That's encouraging in that at least they're aware that his ideas/approaches were productive.
http://emsa.europa.eu/marine-casualties-a-incidents.html
Grim reading, but gives you a feel for what can go wrong.
http://www.amazon.com/Linkers-Kaufmann-Software-Engineering-...
He's been the moderator of comp.compilers since 1986, so he's got a lot of practical Q&A experience to draw on.