dave_ops

6 ms·

1.
by dave_ops 11y ago
Having had several offers to relocate to the Bay Area all I can really say is that almost nobody pays well enough to make it worthwhile. You can make $150k-200k in Seattle, Portland, Denver, Austin, etc. and work on some really interesting
2.
by dave_ops 11y ago
I'm extremely drawn to funny women. I like that they play around mentally with cultural taboos and find creative ways of walking the line between making themselves laugh and making other people uncomfortable.
3.
by dave_ops 11y ago
You can now do this in a sanctioned way in Erlang as of v18. They're including merl as part of the standard distribution now.
4.
by dave_ops 11y ago
Seems reasonable to me... except I don't see the point of having foo/1 and foo1/1. The author could just have easily done: foo(bar) -> void; foo(X) -> undefined. without the need for the proxy function: fo
5.
by dave_ops 11y ago
Your first paragraph is an expectations management problem on both sides. That doesn't depend on the "technical" part of "technical leadership".
6.
by dave_ops 11y ago
So "Elite Firms" basically have horrible hiring processes?
7.
by dave_ops 11y ago
When I internalized this trend ~3 years ago, it's what spurred my interest in distributed storage systems across machines, racks, and datacenters, that are only memory backed.
8.
by dave_ops 11y ago
The first versions of Objective-C were most definitely implemented as pre-processors to C compilation.
9.
by dave_ops 11y ago
I'm a functional programmer (Lisp, OCaml, Erlang), and I only touch C++ when I have to wrap it in something to interface with a higher-level language. Most of the cases where I run into this problem and end up feeling like I didn'
10.
by dave_ops 11y ago
This has been my problems with Rust for the last 10-12 months. Lifetime elision seems thoroughly broken or extremely limited in functionality, and now when I'm writing (sometimes seemingly trivial) solutions in Rust I'm spending a
11.
by dave_ops 11y ago
I realize they called this out in the article as "snark", but it really is just a blog engine, and its monthly web traffic is a small fraction of what wordpress.com gets (which is being served on one of the most craptacular platfo
12.
by dave_ops 11y ago
That's a terrible Faustian Bargain. The choice between someone who doesn't want to learn new things and someone for whom everything is new.
13.
by dave_ops 11y ago
This is actually a good idea I think. Salesforce Chatter is a thing, and it sells well, and it's also terrible. An on-prem corporate twitter would actually be useful.
14.
by dave_ops 11y ago
But it's a SPoF and an extra remote or local service that has to be configured, maintained, etc. The thing that's coming online has to publish a message to redis anyway, so why not just maintain the service map inside the Rust ap
15.
by dave_ops 11y ago
This has a redis service dependency? That is weird.
16.
by dave_ops 11y ago
Fast start times are a valuable thing for a service component. Stick about 10GB of small entries in it (should be enough to create all the levels) and then see what happens. Also, you could reserve the persisted [H|T] for controlled shutdow
17.
by dave_ops 11y ago
TCP would guarantee delivery, but you're right in that you wouldn't know if the consumer actually did anything with the message. It could have crashed on parsing or something. But moving the concern to the consumer to track the c
18.
by dave_ops 11y ago
Also, you have to be paying one hell of a compaction penalty if this isn't a grow-only dataset. By ordering your keys you're at least minimizing the overhead of compaction on write by utilizing the happy-path for how LevelDB moves
19.
by dave_ops 11y ago
Why don't you just store the head and tail as K/V entries? You have a durable K/V store at your disposal.
20.
by dave_ops 11y ago
If you wanted the consumers to be stateless, assuming they otherwise had a deterministic identity, then you could have the queue operate like a journal internally, but present a unified queue API to consumers. So the queue keeps track of th
21.
by dave_ops 11y ago
LWPs and OTP patterns are a "parallelization framework". You have to try pretty hard to design an OTP application that can't be trivially parallelized, and that includes parallelization across machines, not just cores.
22.
by dave_ops 11y ago
So you reinvented the vnode from riak_core?
23.
by dave_ops 11y ago
This is one of the things I love about the Erlang ecosystem (Erlang, Elixir, Lisp-flavored Erlang). Since the whole thing was designed to be an OS unto itself, it has the concept of "Applications" and "Releases" that com
24.
by dave_ops 11y ago
I don't really understand what the heavy emphasis on "real-time" here. I mean it's log/event aggregation for ops insight. Unless the whole system is some tightly coupled feedback loop into an unsupervised machine l
25.
by dave_ops 11y ago
I take it out for dinner and drinks. Spend some time getting know about it and where it comes from and what it does for a living. Then after we're a few cocktails in we get all philosophical. Really start asking the hard questions l
26.
by dave_ops 11y ago
lol, this reads like the way the world ended up with MongoDB. There are some things you have to do right from the beginning or you're never going to get them right.
27.
by dave_ops 11y ago
I'd say my problem with the whole massive containerization hype circus is less that I'm a curmudgeon who hates anything new, and more of a practicioner who hates marketing and social hype promoting a half solution to a narrow prob
28.
by dave_ops 11y ago
Because I already got burned once paying for TextMate and having the development basically die. The same pattern seems to be happening with Sublime Text. So I finally just started using Emacs instead. Setup my keybindings so they're