jsdwarf
Joined 8 years ago
Joined 8 years ago
* pptx-grep - find text across multiple powerpoints, yield file/slide no and text excerpt of match
* pptx-dump - dumps extended info about a powerpoint, such as number of slides, applied master slides, used fonts etc.
* pptx-lint - allows to define validation rules for pptx based on content and/or formatting. E.g. presentation must not contain word "TBD", all text must be formatted in Arial etc.
But i will use the money to hire cleaning ladies or baby sitters -> more spare time than control group.
I've found it easier to use a spreadsheet. Sheet 1 contains the csv export to which i constantly append, sheet 2 the hierarchical acoount structure: an account name like "expenses: groceries:walmart" is followed by a regex that matches the expense description on sheet 1 for that account (walmart). On sheet 1 I have an "detected Account" column, into which a formula outputs the detected account based in the regexes.
Sumif formulas sum up the totals per account. Since no compilation step is necessary, rule changes are picked up much faster
Same purchase from amazon? Difficult, because you have two layers of indirection: checking account > credit card > amazon > it equipment.
Currently testing a new spreadsheet approach to deal with such scenarios, but not easy.
It starts with the lack of a common terminology. For tool A a "booking" might be a reservation e.g. of a dock at a warehouse. For tool B the same word means a movement of goods between two accounts.
In terms of data integration things have gotten A LOT worse since EDIFACT is de facto deprecated. Every carrier in the parcel business is cooking their own API, but with insufficient means. I've come across things like Polish endpoint names/error messages or country organisations of big Parcel couriers using different APIs.
IMHO the EU has to step in here because integration costs skyrocket. They forced cellphone manufacturers to use USB-Cs for charging, why can't they force carriers to use a common API?