ossm1db

9 ms·

1. 61.▲
   by ossm1db 3y ago

   int relationship(double effort) { return -1; }
2. 62.▲
   by ossm1db 3y ago

   Lies, damn lies, and statistics.
3. 63.▲
   by ossm1db 3y ago

   The Blue-Ridge Mountains vs a concrete jungle? That's a no-brainer.
4. 64.▲
   by ossm1db 3y ago

   Thank you. As an ACM member myself, this is indeed welcome news.
5. 65.▲
   by ossm1db 3y ago

   I used a free redis instance. There are all sorts of free database and storage services out there. Cloudflare has some really cool free stuff.
6. 66.▲
   by ossm1db 4y ago

   I like the idea. It has promise but needs some work: no explanation of what reputation does; dice always reduce reputation, not sure why that is desirable; buying first campus sets money to negative cost of campus (-$10000 for first one); s
7. 67.▲
   by ossm1db 4y ago

   If you aren't familiar with the Actor Model, it's worth investigating. It avoids a lot of problems you will experience with other paradigms. https://www.brianstorti.com/the-actor-model/
8. 68.▲
   by ossm1db 4y ago

   In my opinion, TF is for cloud infrastructure up to and including the creation of the kubernetes cluster. Use the Kubernetes API with kubectl, kustomize, helm, skaffold, k14s, etc. to deploy applications and resources on the kubernetes clus
9. 69.▲
   by ossm1db 4y ago

   once AMD releases their 'c' cores, one might argue that SMT is no longer worth the additional complexity.
10. 70.▲
    by ossm1db 4y ago

    The movie "Phase IV" is the perfect movie to accompany this research.
11. 71.▲
    by ossm1db 5y ago

    I developed a rule of thumb for my kids (boy/girl): one individual sport/activity, one team sport, and (boy/girl) scouting. Some parents do even more, but we feared either they or we would get overwhelmed. The individual acti
12. 72.▲
    by ossm1db 5y ago

    Even no-code requires that you be able to break a problem down to solve it, and that involves knowledge, skills and experience. Programmers will adapt, not disappear.
13. 73.▲
    by ossm1db 5y ago

    "Never gonna give, never gonna give (Give you up)"
14. 74.▲
    by ossm1db 5y ago

    I'm not just buying a six-piece, I'm getting six lottery tickets.
15. 75.▲
    by ossm1db 5y ago

    It's on the journal's web site: https://www.nature.com/articles/s41467-021-22592-4
16. 76.▲
    by ossm1db 7y ago

    How did they deal with all of those typewriters in the 50s with an open floor plan? They didn't.
17. 77.▲
    by ossm1db 7y ago

    Or blocking a turn lane. My thoughts exactly.
18. 78.▲
    by ossm1db 7y ago

    and every time it is posted, the "TCP over TCP is a bad idea" link is brought up (once by myself). Each time, the poster/supporters downplay TCP Meltdown. Solutions for VPN over TCP 80/443 already exist. It makes a great
19. 79.▲
    by ossm1db 7y ago

    I understand, but you are still susceptible to TCP meltdown. You need to alert users to the risks.
20. 80.▲
    by ossm1db 7y ago

    Why TCP Over TCP Is A Bad Idea http://sites.inka.de/bigred/devel/tcp-tcp.html
21. 81.▲
    by ossm1db 7y ago

    What about the other 11 months?
22. 82.▲
    by ossm1db 8y ago

    This looks like a wheel sieve: https://programmingpraxis.com/2012/01/06/pritchards-wheel-si...
23. 83.▲
    by ossm1db 8y ago

    Run the websocket proxy yourself and get much better performance: https://github.com/benjamincburns/websockproxy From the FAQ: "net_url sets the URL of the websocket VPN." I did this and it works great.
24. 84.▲
    by ossm1db 8y ago

    I guess I should consider myself very fortunate. It works out very well for me. I've worked under an unlimited PTO policy for several years now (at two different companies). It does not "depend on management approval." Approv
25. 85.▲
    by ossm1db 8y ago

    SOA is _not_ ESB
26. 86.▲
    by ossm1db 8y ago

    http://tinycorelinux.net
27. 87.▲
    by ossm1db 9y ago

    If Gitlab could deploy to a play-with-k8s temporary cluster with four hours to test and evaluate, that would be pretty cool.
28. 88.▲
    by ossm1db 9y ago

    I learned first-hand that migrations are difficult. Do not go to production with Swarm if you are thinking of migrating to k8s. Use it for experimentation and learning.
29. 89.▲
    by ossm1db 9y ago

    I also recommend starting with Swarm (not necessarily going to production) and then learning k8s next. This is the path I am taking. Kubernetes is different in surprising ways, but it helps to already have the basic concepts down by learnin
30. 90.▲
    by ossm1db 9y ago

    You may be able to refute their recommendations with this video where Raymond Hettinger sympathizes. https://www.youtube.com/watch?v=wf-BqAjZb8M