njd

3 ms·

1. 1.▲
   by njd 10y ago

   I'm a retired data architect and C developer with 36 years of professional experience. In my opinion, this is not how you find an appropriate candidate. It would be better to ask substantive questions that are related to the thing yo
2. 2.▲
   by njd 10y ago

   Yes, especially with early cleansing and transformation. When source semantics are dynamic, try to build recognizers rather than expect sources to obey some semantic agreement. They won't. Cast what you can recognize into an interme
3. 3.▲
   by njd 10y ago

   It is possible, but there are a lot of caveats. For example, how do you detect when a source's semantics change? This will break any cleansing or transforms done in the stream platform. Until it gets fixed, data may be missing, wrong,
4. 4.▲
   by njd 10y ago

   Yes. But, the trie implementation would need to somehow allocate mmap file address space. Depending on supported size of the trie, may require multiple mmap files. The addressing scheme would need to consider that. If you want the trie
5. 5.▲
   by njd 10y ago

   Interesting. How would you use one of these implementations to persist a large trie beyond what physical memory can support?
6. 6.▲
   by njd 10y ago

   Thanks for pointing that out. Instead of the endless cascade, just cascade once off of the first link. That way, there would never be more than two references to resolve and you still get the temporal benefit. > ln -s ../fluffy.jp
7. 7.▲
   by njd 10y ago

   Instead of renaming the file, TagSpaces could create a symbolic link and preserve the original file name. All such links could be managed in a TagSpaces folder. > ln -s ../fluffy.jpg "fluffy [cat].jpg" Tags could be added
8. 8.▲
   by njd 10y ago

   I enjoyed reading your story about building a DBMS. In it, you mention the importance of performance. So, I'm curious as to why you chose 'go' versus 'C'. Was the choice of 'go' a convenience to get som
9. 9.▲
   by njd 10y ago

   - The challenge for an organization is to recognize that there is a significant difference between the 'data engineer' working on a vertical project and the 'data engineer' responsible for integrating data across the ent
10. 10.▲
    by njd 10y ago

    I'm developing a distributed temporal KV store in C. My motivation for developing the TKV is my interest in such questions as 'why' data changes and the effect it has on the 'system' in general. I chose to develop