Interested as well if anyone has an answer to provide
HN user
etiennebch
Less clunky in my opinion if you use it for software development because you can link it to issues / PRs and automate based on that
You don’t need a stock market for equity to appreciate. A private business that delivers value makes owning a piece of the business valuable regardless of whether the shares are publicly traded
Yep. Currently, I only parse their RSS feed. Later, I want to extract and organize information in a way that's easy to search, look at and save.
Thank you, great insight, I'll give it a thought. I want to have a focused, narrow scope for the MVP, but I think finding and digging (public!) financial information is a mess currently, even with all the apps, blogs, yahoo finance and the likes out there
SEC filings browser. Currently just a prototype: displays the most recent filings as they occur
Ah thanks for the clarification !
Not sure if this is what you are looking for but I found this paper useful on architecting databases. I read it as a complement to the CMU videos. https://dsf.berkeley.edu/papers/fntdb07-architecture.pdf
Otherwise there is surprisingly a lack of information about architecting databases online and you have to go to the source code of SQLite and PostgreSQL. I suspect this is because databases are some of the most complex systems in computer science and involve many trade secrets.
I use them for cursor based pagination. You can use rank and a where clause to apply the limit. You can also compute max rank to determine whether there are more data to fetch after limit. Finally, if you do left joins where you may have multiple rows per objet, you use dense rank instead of rank
I have been using Flask for a while now (to code rest apis). The circular import issue can be a pain. I blame most tutorials and examples out there for this. As the article mentions, putting code in init.py can lead to issues because the file is read when importing modules in the directory it is declared. Better to keep it empty. Also tutorials rarely mention how to use the factory pattern effectively which prevents most of the issue. This is how flask extensions are implemented by the way, with init_app function doing the initialization. Often instead, you see app = Flask() declared at the top of the init.py Not to mention using the app.url_rule decorator on views (which leads to importing the global object) instead of using blueprints to register views and registering blueprints in the app factory
Hash functions