I have this app where we store numbers. Don't we all? Unfortunately, this app stores numbers without context. So, I don't know whether the number will be an integer or represent numbers throughout the real number space. Compounding this situation, I stand to gain particular advantage if I can store all these numbers in a fixed width datatype (each number consume the same number of bits of storage space). On current computer systems, there are two native types to each do some of what we want: the 64bit IEEE floating point type "
I’ve been writing docs for Reconnoiter. I selected DocBook for two reasons. First, I hoped that number of polished documents I’ve seen written in DocBook would mean that if this manual grows in size and usefulness we might be able to achieve some polish “on the cheap.” Second, our open-source site has a really nice automated systems for auto-publishing project documentation… if it is in DocBook. That said, DocBook is a complete pain in the ass.
At no point in the history of OmniTI has it "shrunk" in size. It’s a beast now and it continues to grow in fantastic ways. As such, we’re are hiring.
I’m looking for a junior developer. However, I’m looking for a good junior developer. I’ve been so frustrated in the past with the various definitions of junior and mid-level and senior. Constantly I see an entry-level programmer come in with delusions of being an enterprise architect or a senior-level web application program because they made their own website.
I've been a long time user of Spread. I would say that I have a decent understanding of how it works and how it runs. I was, after all, in the lab (during graduate school) with all of its creators and even managed to contribute some code.
When I left academia, I did quite a bit of software building and analysis. This led to architectural design of enterprise systems. And a division of my company has a very strong focus on enterprise software development and release management.
So, I was implementing this thing… It seems that all my discussions start like this. Sigh. So, I was implementing this caching systems for file signatures. I needed a hashing algorithm with excellent distribution and low calculation cost. My first assumption was that MD5 didn’t meet my needs due to its computational costs… I was surprised.
I found a great exploratory article on hashing that assisted my search for the perfect[-enough], cheap[-enough] hash.
