# Some Performance Announcements **URL:** \ **Category:** News from Superhuman\ **Created:** [June 19, 2019, 9:51pm UTC](https://connect.superhuman.com/t/some-performance-announcements/8670 "2019-06-19T21:51:00Z")\ **Posts on this page:** 1\ **Showing post:** 42
**Author:** ![Paul\_Danyliuk](https://yyz1.discourse-cdn.com/coda1/user_avatar/connect.superhuman.com/paul_danyliuk/32/27228_2.png) [@Paul\_Danyliuk](https://connect.superhuman.com/u/Paul_Danyliuk)\ **Post date:** [February 10, 2020, 9:35pm UTC](https://connect.superhuman.com/t/some-performance-announcements/8670/42 "2020-02-10T21:35:29Z")
My 5c regarding performance. For non-trivial use cases, no wonder it would take non-trivial skills to make them right. For docs that are more like apps, having software engineering skills and thinking would be very helpful. E.g. just a recent example of optimizing an “endlessly recalculating” doc: > [@PSA: Replace Now() with a lower-resolution real time clock for heavy formulas](https://connect.superhuman.com/t/psa-replace-now-with-a-lower-resolution-real-time-clock-for-heavy-formulas/13759): > > UPD: For anyone finding this trick in 2023 and beyond — don’t use it anymore! Use Now() with precision, e.g. Now("minute") or Now("hour"). For the record, there are two hidden functions, NowInMinutes() and NowInHours() but the officially supported one is Now() with an argument. Sometimes you need to calculate things based on current time (e.g. conditionally format tasks that are due, or show different text values for when the time is in the past or in the future). And sometimes those calcula… And just a few days ago I optimized a very complex calculator I built for another client: I managed to reduce time required to add a set of rows from ~30 minutes down to ~3 minutes. In both cases I just analyzed heavy formulas / unnecessary recalculations, and thought of how to bypass those. E.g., in the 30 min → 3 min case I streamlined the dependency flow (i.e. so that table B depends on table A, but nothing from table A depends on table B) and replaced a fair share of “live formulas” with inputs that could be populated just once with a button. FYI this was a table where rows were dependent on other rows from the same table (think recreating Excel cells where each cell is a Coda row), so adding a row would’ve triggered recalculations over the whole table. This reply would’ve been a shameless plug because I’m doing Coda consulting for a living and optimizing perf is just one of the things that puts food on my table. But I’m insanely overworked already, so not a shameless plug this time 🙃 --- _[View the full topic](https://connect.superhuman.com/t/some-performance-announcements/8670)._