Even though the day seems lost. The week, far gone. "Take what the defense gives you" What can I do now? The simple things. The low-hanging fruit. Play for tomorrow; maybe things will be different then. Our work is a practice. One bad day us nothing to
Was on leave most of this week so updates were bleak Primary KPI - Weeks until launch Actual = 4 , Goal = 4 - Nov 5th I think I had accounted for this so we still should be good for Nov 5th. Secondary KPI - Number of users talked to. Actual = 0 , Goal = 0 Biggest
Was reflecting on our discussion last week and you were right MRR is not the best metric pre launch.(addressed to accountability partner) I did some "research"(ie watching a yt video lol - from the YC Startup School playlist) They said the pre-launch weekly metrics should be
Scrappy notes based on YC talk. KPIs(Key performance indicators or North Star Metric) Pre launch Example: Weeks until launch or Number of users talked to. Post launch Identify Top KPI - MRR or some revenue-based metric for most startups Identify major bottlenecks or biggest problem. System to move your
Its far too easy to push bullshit features. We no longer have constraints. So we build everything. Stop, think, build by hand sometimes. Dont run from the decision. "The ability to let that which does not matter truly slide" (not my quote)
QA Monk
We first started with an excel sheet for test cases(version 1) Version 2 was the tracker + element IDs + Excel sheet output + Claude. So this is version 3. Problem: New features break old features. Old features are too complex to test off the top of my head. (complex meaning some
btw I could be wrong; open to suggestions and alternate methods. One of Bubble's biggest flaws is handling concurrency. Say for example you have to display reporting data for sales. Current sales: $100. When 2 simultaneous orders are placed, both read 100 and update it at the same
QA Monk
Not a bad week. I thought I scheduled too less. Apparently that was not the case, and I just about finished the task. What was your Primary KPI - Actual vs Goal? Goal was 15$. Actual was 0$. What a surprise. Biggest Obstacle to growth? Umm. Not having a good enough
QA Monk
Extracted the events. There still seems to be an issue. Some of the events are missing their values. I generated the flows file below. arkhitect-observed-flows_1arkhitect-observed-flows_1.csv19 KBdownload-circle It seems to have covered all the events. Even though the chat with the agent was
QA Monk
One of the biggest benefit that I cant wait to have is to run regression tests during development. While using no code tools like bubble.io, we are majorly deprived of this. Ive heard that in TDD(test-driven development) you write out the cases first. Then as you experiment
QA Monk
Today Claudius Maximus told me that there were some issues with the tracker. Issues with session management. Who even asked for session management, mate? I am realising the easiest way to solve problems is to first look at why we are doing it in the first place. Most complexity will
Finalising the mvp/feature set. Saying mvp makes me cringe now. Writing the solution again has given me more clarity. As definitions keep evolving. The first customer profile is a simple Bubble.io application that needs testing. This will help me iterate the high-level solution faster. In the past,