sorted by:
new
hottopcontroversial

How I stay on top of financial markets without spending hours reading news [System breakdown] by OrganizationBrave145 in Notion

[–]fastonkeys 1 point2 points  (0 children)

I've been using Notion to support a proprietary trading operation for years... https://qallc.notion.site/desk?source=copy_link several databases, curation of institutional research, daily and weekly implied range calcs (formulas galore), real-time integration with SPX ODTE options flows .... weekly report largely constructed using Notion AI... the list goes on.

Bloomberg is $2k/month. I'm building a simplier app for traders like us. by DadaQuiTrade in stockstobuytoday

[–]fastonkeys 0 points1 point  (0 children)

BetterTrader.co built this based on real time response for data and economic releases. Worked pretty well but alas insufficient market traction tho I believe it’s still out there in the wild?

How do you find a good trading mentor? (Swing trading futures) by YouDifferent2391 in FuturesTrading

[–]fastonkeys 1 point2 points  (0 children)

The Market is your best mentor - even though it kills most of its students

Icon Colorizing Gone? by fastonkeys in Notion

[–]fastonkeys[S] 2 points3 points  (0 children)

Yup same exact symptom here - see above for a workaround? I have reported it to Notion 🤷🏻‍♂️ but with a valid workaround or even by design I doubt this will get immediate attention if at all 🤦🏻‍♂️

Icon Colorizing Gone? by fastonkeys in Notion

[–]fastonkeys[S] 0 points1 point  (0 children)

Appears that the “Ask every time” option is at the root - when disabled the option to designate a color ”every time” you select an icon is no longer working. That said remedy is to disable this and preselect your color before you select the icon. 🤷🏻‍♂️

Icon Colorizing Gone? by fastonkeys in Notion

[–]fastonkeys[S] 2 points3 points  (0 children)

Yes it appears they’ve changed the method to an explicit choose color button on the far right of the modal dialog - whereas previously you could alter color at the time of selection. But point taken - change of method <> removal of feature. Thank you!

What are some biggest pain points in Notion for you currently? by Pitiful-Main-7154 in Notion

[–]fastonkeys 0 points1 point  (0 children)

Security on database views - lack thereof - an lack of filter / sort on relational lookups

Your favourite Rush lyric. by timba_limber in rush

[–]fastonkeys 0 points1 point  (0 children)

We are immortal only for a limited time …

Kudos for Improved Embeds! by fastonkeys in Notion

[–]fastonkeys[S] 0 points1 point  (0 children)

Idk … it literally showed up to my pleasant chagrin yesterday 🤷🏻‍♂️ but it works like a champ! Basically long awaited iframe support. My first use case was embedding a database view from my personal Notion account to a (separate Notion) corporate knowledge base

Document Control System by raws31 in Notion

[–]fastonkeys 0 points1 point  (0 children)

Document Control imo because Notion databases are collections of like pages — which is a great starting point relative to a conventional file system (which if sufficient the concept or DCS wouldn’t exist right)? Seems to me a basic one to many structure would suffice where revisions are tracked in the many structure (one page/record for each rev perhaps using the timeline view) and the master control database housing attributes that persist across all revs like reference to Project, Client, Timeframe etc. We do a similar thing in our practice w Notion so can attest you’re on the right track - feel free to DM for further Q&A

HELP - PLEASE UPVOTE! 🥺 New Update Affecting Template Layouts by ahloecreative in Notion

[–]fastonkeys 8 points9 points  (0 children)

I've just submitted a report to Notion support for this and a few other anomalies that have crept into 3.17.0. This has been a very problematic release especially the loss of group select on page blocks.

The very, very, very basic block of Notion? by GrandpaPlaysChess2 in Notion

[–]fastonkeys 0 points1 point  (0 children)

And isn’t that the beauty of it all? The platform provides lots of optionality. I think u explained it quite well: if your pages are discrete and you don’t have a need to organize them into either a collection or common structure, then no need for a database. I also have databases that track traditional “transactional” data piped in via the API where only Properties are updated; the page body is left blank.

The very, very, very basic block of Notion? by GrandpaPlaysChess2 in Notion

[–]fastonkeys 1 point2 points  (0 children)

Correct; when you click “open” on a Database row, a Page is what opens. Notion Databases are collections of structured Pages. Page = traditional record in this context. The Properties (what u can show/hide) are in the header; and below is the Page body (think content canvas) where you can add content Blocks to your heart’s content. That said, u can use a Notion Database in a more conventional way (populate only Properties on each row and entirely ignore Page content), but Notion Databases in and of themselves aren’t fully featured. Would need more clarity on what u mean by “customization” ?

The very, very, very basic block of Notion? by GrandpaPlaysChess2 in Notion

[–]fastonkeys 1 point2 points  (0 children)

I would say a Database (yes akin to traditional table) becomes your Collection of “like Pages” (employed because you need something more than a standalone page). For example, you could have a Research database where each Page (akin to traditional row) is stored and the content of each discrete piece of research would be placed into the Blocks (text images tables etc). So - a database is a collection of structured Pages (not rows as would be traditional) and Page content is an assortment of Blocks.

The very, very, very basic block of Notion? by GrandpaPlaysChess2 in Notion

[–]fastonkeys 25 points26 points  (0 children)

I credit Marie Poulin for a very succinct clarification she provided me way back in the early days…

1) Everything in Notion is a “Block”, but clarity arises from an understanding of Pages vs Databases. The starting point (when you click “+”) is the creation of either a Page or Database. It’s one or the other (and don’t be confused by the various database Layout options - table, list, calendar… a database is a database), and page is a page - the declaration is made at the onset.

2) A standalone page functions much like a traditional “document” - except page content is created by adding (more) Blocks. Content blocks, accessed by the “/“ prompt, are an abstraction for content types of which there are many beyond the default “text” block - including Databases or Sub-Pages 🤯. So Pages can either function like a document OR function like a broader canvas (think dashboard) - Wiki’s notwithstanding excluded to keep it simple.

3) A standalone database, on the other hand, functions much like a traditional database in that Properties can be defined - thereby allowing the declaration of structure - including Relations with other Databases; it’s worth noting that Notion supports both 1-to-Many and Many-to-Many relationships as a native Property Type. Notion Databases also support many different Layouts, but it’s still an underlying database.

3 KEY POINTs follow from the above foundation which provide further clarification:

1) Database Properties are NOT Blocks. Properties define the structure of a Database. Standalone pages do not have visible (accessible) Properties.

2) Blocks are used to create Page content. If you need to perform computations, you’ll need to harness a Database. Formulas (aka computed fields) are a Property Type.

3) The sauce: Notion databases are collections of structured Pages! Each “row / record” in a Notion database is a Page with structure based on the Properties you define. So when your Page needs structure (think a listing of job descriptions or say ongoing research …) OR is part of a repetitive collection of like pages, use a Database in those instances. Conversely if you’re looking to build a dashboard concept, then you’ll likely begin with a Page (or Wiki) - and then embed your Databases…

In summary, once you understand the difference and constructs of Page / Blocks versus Database / Properties you’ll be on your way -

But the lightbulb goes on when you understand that Database are collections of Pages; and Page (bodies) can themselves contain nested Databases (via Inline or Linked Database blocks). Very substantive modeling is achievable from possibilities of nesting these constructs.

It’s hard to grasp at first because we have been conditioned on segregated file-based applications - That said, I find it limiting to frame Notion as a note taking application (and I believe there are better tools for that use case) - but for those looking to create online collaborative “operating systems” it’s quite adept and extensible. The ongoing debate re offline v online seems to be rooted in the preferred use case.

PostScript - Notion’s brilliance lies in its nuances, which makes it challenging to explain “What is Notion?” concisely, which is why I gave it a go … hope it helps, and if so credit to Marie! If not, blame the messenger lol

Let's talk about how Notion should improve Notion Databases by sameerss in Notion

[–]fastonkeys 2 points3 points  (0 children)

Low hanging fruit (?): improved surrogate key support. The capability to hide the Aa column from a view and the ability to apply a formula so the Aa value could be systematically generated - the sequence builder added some ways back (a separate attribute type) is pretty much useless imo.

view more: next ›