I’m trying to animate the iQ logo:
I’ve got this part down:
I’m relating what I learn here, to what I am applying to iQ. Here I’m reiterating some key terms; follows by a definition, an IR Book example, and an iQ example.
I use Git for personal projects. I got frustrated with the Git UI clients. I would get myself into tree conflicts (or other problems I still don’t fully understand), and the UI couldn’t get me out. Plus I’ve been compelled to learn more about console programming. So I started using Git Bash — the Linux-like console. And I learned a lot.
Good code is self-documenting code.
That’s why I’m getting into the habit of using Python Docstrings.
Here is a summary:
I’m spending some time on iQ today.
I’m trying to stay mindful of performance impacts.
iQ is document-based. It’s not supposed to handle database-sized quantities of data. But I don’t want to be short-sighted.
I wanted to apply what I’ve learned recently about document.querySelectorAll.
The results are enlightening!
I’m working on a new language. It’s called iQ.
iQ stands for “iXBRL Query”, where “iXBRL” stands for “inline XBRL”, and “XBRL” stands for “eXtensible Business Reporting Language”
With iQ, you can easily locate values and identify patterns in financial data. The goal: freely enable anyone with an interest in finance to make meaningful stories out of financial data… Continue reading
Paul Warren recently revisited the popular discussion of negative values in XBRL . Many experts consider negative values the biggest quality/comparability issue in XBRL. If it’s that important, I want to chime in! This post is hopefully the first of a few on the subject. This post will focus on my experience in creating XBRL and the rationale I apply to the problem of “negative values”. Continue reading