Tweet
Day 69. Finally resolved the db problems. To kickstart marketing I need a landing page. Though Im mostly a backend dev, I'll try next js. I want to also have a dashboard for managing the user's companies, API keys etc. @100dayscode #API #Bookkeeping #buildinpublic #indiehackers
Day 68. My first snag. I'd chosen @supabase for db, but while I'm only in beta a whole schema is just gone from the FE! Support would likely be great if I was paying, but this error is a bit egregious for me. Back to shopping I guess @100dayscode #API #Bookkeeping #buildinpublic
Day 67. After spending some time attempting to get some beta testers, I realized that an API without a landing page just won't cut it. So that's what I'm working on now. @100dayscode #API #Bookkeeping #buildinpublic
Day 66. Finally done with all the logging setup. Now gearing up to getting some beta testers to give the app a spin. Really hoping to get enough engagement to determine some product-market fit if any :) @100dayscode #API #Bookkeeping #buildinpublic
Day 65. Finished the setup for warning loglevel, worked on emailing for error loglevel exceptions. Hoping to finish this tomorrow. @100dayscode #API #Bookkeeping #buildinpublic
Day 64. Spent the day setting up Exceptions logs with log levels: handled Ex-> Warning, unhandled Ex -> Error, system Ex -> critical. Warnings go to papertrail, errors are emailed and criticals go to slack. Thus managing info overload @100dayscode #API #Bookkeeping #buildinpublic
Day 63. The docs were taking too many of my 100 days, so I took a hiatus to finish them. Now that's done, I'm looking for logging storage options before for looking for beta testers. So far @papertrailapp is looking pretty good @100dayscode #API #Bookkeeping #buildinpublic
Day 62. All done with the Categories cookbook. As I write about what the app currently does, I keep getting ideas on what else it could do and its a real struggle not to ditch the docs and extend it. Anyone else had this problem? @100dayscode #API #Bookkeeping #buildinpublic
Day 61. Completed the Balances cookbook. Tomorrow I'll start working on the Categories section.
@100dayscode
#API #Bookkeeping #buildinpublic
Day 60. Completed the Accounts cookbook. Mostly covering the most straightforward scenarios, I expect to add more based on feedback from beta testers. Tomorrow I'll start working on the Balances cookbook.
@100dayscode
#API #Bookkeeping #buildinpublic
Day 59. Spent the day setting up the structure of the cookbooks. Decided to go with a Problem ⇒ Solution model. I'll begin adding some actual scenarios next week, starting with Accounts @100dayscode #API #Bookkeeping #buildinpublic
Day 59. Finalized updating the API reference documentation with the missing endpoints. Now I can start writing specific scenarios in the cookbook section of the docs. @100dayscode #API #Bookkeeping #buildinpublic
Day 58. With the Transaction Assignments, the basic documentation is finished. I was about to start on the cookbook section when I realized some areas are missing from the API reference itself. So I spent the day filling these gaps. @100dayscode #API #Bookkeeping #buildinpublic
Day 57. Didn't actually get too much done today, but at least I finished the documentation for Transaction Assignments. Perhaps I'll get more done tomorrow @100dayscode #API #Bookkeeping #buildinpublic
Day 56. Finished the documentation on Taxes Discounts. These two Resources are not only similar in structure but also intimately related. They will therefore also feature prominently in the cookbook section. @100dayscode #API #Bookkeeping #buildinpublic
Day 55. Worked on and completed the Line Items docs. Like Transactions, Line Items are a key part of how the system functions so I'll add more details and examples in the cookbook section. @100dayscode #API #Bookkeeping #buildinpublic
Day 54. Finally completed Transaction docs. Tried to keep to the basics and only describe the functionality of the endpoints, I'll add more details and exotic scenarios in the How-To guides. @100dayscode #API #Bookkeeping #buildinpublic
Day 53. While working on some scenarios with the Transactions, I decided to add short descriptions of each type for non-accounting devs. While at it, I added descriptions of the Account resource types as well @100dayscode #API #Bookkeeping #buildinpublic
Day 52. Halfway done with the Transactions docs. Struggled a bit deciding how much detail to include since this Resource is one of the more vital parts of the whole system. Looking forward to feedback from devs during the beta test @100dayscode #API #Bookkeeping #buildinpublic
Day 51. Wow, already past the halfway point, time really does fly. Today I got done with Account Categories, and that's the end of the easy part of the docs. Tomorrow I'll start on the first of the complex stuff, Transactions @100dayscode #API #Bookkeeping #buildinpublic