schneems

49 ms·

1. 571.▲
   by schneems 11y ago

   This is by far the best talk I've ever seen on the topic "Negotiations for Hackers" https://www.youtube.com/watch?v=icuSn3k9Euk
2. 572.▲
   by schneems 11y ago

   > A more prominent and successful company would have jettisoned him as soon as it found a qualified and, in all probability, more loyal applicant. Even a successful company needs good engineers. They don't fire people just because
3. 573.▲
   by schneems 11y ago

   I really hope no one is ever doing `rails >= 4.0` in their Gemfile.
4. 574.▲
   by schneems 11y ago

   > There is actually a lot of complexity to hashes in Ruby. I agree here > So if you construct a valid hash, then call three functions passing them the hash, you have no idea if the hash is still valid for the second and third function
5. 575.▲
   by schneems 11y ago

   I was introduced to http://hypirion.com/musings/understanding-persistent-vector-... not too long ago on HN. I don't use clojure so I was paraphrasing my somewhat limited understanding. Thanks for the clarification
6. 576.▲
   by schneems 11y ago

   I think you nailed my original intent quite well, thanks for the post.
7. 577.▲
   by schneems 11y ago

   Excellent point, I honestly hadn't considered that. I've spent more time dealing with functional programming than in actual languages with immutable structures. Thanks for pointing that out. I think my other point still stands, th
8. 578.▲
   by schneems 11y ago

   I was at this talk and I disagree with his fundamental statement that simple + simple = simple. I program in Ruby one of the biggest problems beginners make is not creating complex data structures where they are needed. Instead they pass ar
9. 579.▲
   by schneems 11y ago

   Your client a spin. Looks interesting. On a side note I built something like throttlehq back in 2009. I even made one of those zany animated how-it-works videos that were popular at the time. https://youtu.be/SLJHPMxgAWU?t=1
10. 580.▲
    by schneems 11y ago

    I'm still hanging on to mailbox. I'm giving them another iteration cycle or two to fix stuff. So far their product and support has been very underwhelming. I still like their iphone app.
11. 581.▲
    by schneems 11y ago

    I loved sparrow, bought sparrow. It got acquired and went away. I loved mailbox, used mailbox. It got acquired and is more and more unusable with every "update". I would love to love this, but I've been hurt before.
12. 582.▲
    by schneems 11y ago

    Came here to say the same. It makes sense that older companies are locked into their database as migrating would be too difficult like Facebook. I though Pinterest was a relatively young company and I'm surprised it chose mysql. Instag
13. 583.▲
    by schneems 11y ago

    That's cool, In Ruby Hash merges are really expensive. I played around with a non-mutating data structure that uses references two two hashes and behaves as if it had been merged instead of allocating. It was a fun thought experiment b
14. 584.▲
    by schneems 11y ago

    Allocating things on the stack is still allocating things? It's faster to mutate than to allocate?
15. 585.▲
    by schneems 11y ago

    > if your GC is smart Can you say more? I don't know how C++ uses destructor positioning? Seems to me if it gets to GC it's too late, you already made an allocation which is the expensive part.
16. 586.▲
    by schneems 11y ago

    Immutable data structures give you easy parallelism, however there's a hidden runtime cost: you have to allocate way more objects. For example, I was able to save a ton of object allocations here: https://github.com/mim
17. 587.▲
    by schneems 11y ago

    I appreciated the tone of the article. I found it very easy to read. Though I agree the "likes" were a bit over the top. There were several times he used "like" and I mentally paused as if it were a comma only to realize
18. 588.▲
    by schneems 11y ago

    > Puma is great if you have a Ruby implementation without a GIL Puma is also great if you have blocking IO like database queries or file uploads which most ruby/rails apps do. The GIL is released when Ruby does IO so it can context
19. 589.▲
    by schneems 11y ago

    Whooops responded with old account. If you run `$ env RAILS_ENV=production rake middleware` you'll see that your final app that gets mounted is actually the "routes" of your app. run CodeTriage::Application.routes E
20. 590.▲
    by schneems 11y ago

    This is merged into master which is targeted for Rails 5.0.
21. 591.▲
    by schneems 11y ago

    > I've been impressed with the performance work you've been doing across the board Thanks! For all the tests I used MRI Ruby 2.2.2. Unless otherwise noted, I almost exclusively use the most recently released MRI Ruby version fo
22. 592.▲
    by schneems 11y ago

    Mutable strings are a double edged sword from a performance perspective. It sucks to have a bunch of un-needed string allocations due to string literals that are only used for one method. Sometimes though, mutating and re-using strings when
23. 593.▲
    by schneems 11y ago

    Thanks, fixed :)
24. 594.▲
    by schneems 11y ago

    > where to you think there are hot places where is easy to go and improve? I tried to write some fancy libs to pull out easy optimizations https://github.com/schneems/let_it_go . It wasn't dramatic but it did fi
25. 595.▲
    by schneems 11y ago

    I wrote the patch and the article, do you have any questions related to either?