mmacedo_en

6 ms·

1.
by mmacedo_en 6y ago
It's mobile first to input expenses and view spending limits anytime anywhere. I usually input expenses right after paying for them. I'm using Flutter, which also builds apps for Web, Windows and Linux using the same codebase. My
2.
by mmacedo_en 6y ago
I've been working on Pleke for the last 18 months and using it daily for the last 6 months. Would love some feedback!
3.
Show HN: Pleke – free personal finance app for Android and iOS(pleke.com)
6 points by mmacedo_en 6y ago|4 comments
4.
by mmacedo_en 6y ago
For twenty years I tried to build products and sell them to others, to no avail. "Marketing is the problem" - I always told myself about my failures. I still have one product up from those days. FileSculptor is a file converter us
5.
by mmacedo_en 6y ago
Hey everybody, I've been working on Pleke for the last 18 months and using it daily for the last 6 months. It is based on cashflow, so the budget is affected when money enters or leaves the accounts. Credit card purchases affect the bu
6.
Show HN: Pleke is a budgeting and expense tracking app based on cashflow(pleke.com)
1 points by mmacedo_en 6y ago|1 comments
7.
by mmacedo_en 6y ago
Did it already :-) Good idea putting twitter link on your profile
8.
by mmacedo_en 6y ago
I'm referring to parent's point "Sometimes you just have to do joins across large tables.". Indexes and query hints can make a world of difference once you profile how the query is being executed. Another option is to cr
9.
by mmacedo_en 6y ago
HN is missing an user follow and user tagging button :-)
10.
by mmacedo_en 6y ago
I've seen queries running for 1 minute 2 minutes raising user complaints. Then we looked at it, and with a few changes in indexes and query hints brought it down to sub-second execution. Before thinking about distributed systems, there
11.
by mmacedo_en 6y ago
I'm building an app using Postgres for the first time. Naturally I was a bit worried about performance and scaling if the not launched yet app becomes a major success. I began simulating a heavy use scenario. 100k users creating 10 rec