u/kayanokoji02

I want to share something I see constantly because I think it would save a lot of small business owners a significant amount of money and stress if they knew about it before it became a problem

I am a freelance bookkeeper, been doing this for about six years, work mostly with small service businesses, consultants, a few ecommerce stores. Over the past three years I have onboarded roughly 40 new clients, most of them coming to me after some kind of financial wake up call, either a messy tax season or a cash flow crisis or a loan application that surfaced problems they did not know existed

Here is what I find in almost every single set of books I inherit

The chart of accounts is a disaster and nobody has touched it since the business owner set up QuickBooks on day one

I do not mean slightly disorganized. I mean expenses that should be cost of goods are sitting in operating expenses. Owner draws that are categorized as regular expenses. Revenue from completely different service lines all lumped into one generic income account. Assets that were expensed immediately instead of depreciated. Loan repayments hitting expense accounts instead of liability accounts

None of this triggers an error in QuickBooks. The books balance. Reports generate. Everything looks functional. And yet the P&L these business owners have been reading every month bears only a loose resemblance to the actual financial reality of their business

The reason this matters so much is that every single business decision gets made off those numbers. Pricing decisions. Hiring decisions. Whether to take on debt. Whether the business can afford a new piece of equipment. All of it is being made off a P&L that is structured incorrectly at the foundation

I had a client last year who had been running her consulting business for four years and was convinced she had about a 35 percent profit margin based on her monthly reports. When I rebuilt her chart of accounts correctly and reclassified her transactions properly her actual margin was closer to 19 percent. She had been underpricing her services for four years because her books were making her think she had more room than she did

She was not being careless. She had set up QuickBooks using the default template, added a few accounts over the years as she thought of them, and trusted that the system was categorizing things correctly. Nobody had ever told her that the default chart of accounts is built for a generic business that does not exist and that getting it right for your specific business requires actual thought and setup

The fix is not complicated but it does require someone who understands both accounting and your specific business to sit down and rebuild it properly. For most small businesses that is a one time project that takes a few hours and then the monthly work becomes dramatically more accurate and useful

If you set up QuickBooks yourself more than a year ago and have never had an accountant review your chart of accounts structure, that is worth doing before your next major business decision. The numbers you are looking at might be telling you a story that is structurally different from what is actually happening.

every tech blog talks about shifting left but nobody talks about the maintenance nightmare that comes with it.

for the last two years my team was forced to write end to end tests for every new feature before it merged. we ended up with a massive appium suite for our mobile apps. sounds great on paper right.

the reality was our pipeline was taking almost an hour to run and failing constantly. developers stopped trusting the pipeline. they would just hit rerun jobs because they knew the failure was probably just a stale xpath or a button that a frontend dev moved 10 pixels to the left.

we had turned our safety net into an administrative tollbooth that everyone hated.

we finally audited everything and realized tying our tests to the underlying code was the actual root cause. visual ui changes should not break a test if the app still works for the end user.

we ended up ditching code based locators entirely and moved our mobile flows over to drizz recently and as I know it uses vision ai so you just write tap checkout in plain text and it visually finds it on the screen. if marketing changes the button color or layout the test still passes.

we cut our ui test suite down to just the core revenue paths and moved everything else to the api level. our pipeline is insanely fast now and when it fails devs actually look at the logs because it means something is actually broken.

stop bragging about having a massive automated ui test suite. if your team spends half the week maintaining locators those tests are a liability not an asset.

i have been doing manual testing for about four years mostly on mobile apps. my company is pushing really hard for 100 percent automation this year and honestly i am panicking a little bit.

last year management bought this expensive codeless automation tool that was supposed to make it super easy for manual qa to just record our screens and generate tests. it was complete garbage. the second we hit a native pop up or a complex login flow the tool would freeze and we would have to beg the developers to write a custom script for us anyway. they eventually cancelled the contract.

now leadership is saying we all need to learn java and appium if we want to stay relevant. i am trying my best to learn it after hours but the learning curve is insane. half the time i cannot even get the appium inspector to launch on my machine without throwing some random environment error. getting the actual element locators feels like a full time job.

is there a realistic path forward for manual testers right now or do i basically need to become a junior software engineer just to keep my job. are there any tools out there that actually work for manual folks without needing a comp sci degree or is the whole codeless thing just a scam.

Consider this a warning to anyone setting up a new E2E suite.

Stage 1: False Hope You build a beautiful suite of 150 critical user journey tests. They run perfectly in your local environment. You feel like a god.

Stage 2: The Ambush Your marketing team decides they want to run a weekend promo. They inject a massive newsletter popup via GTM that loads asynchronously, usually about 3 seconds after the page renders.

Stage 3: The Slot Machine Pipeline Your tests now randomly pass or fail based on server speed. If the script clicks the checkout button in 2.5 seconds, it passes. If the server is slow and the popup loads first, it intercepts the click and the pipeline crashes.

I don't want to wrap every single .click() command in my entire framework in a massive try/catch block just to look for a random modal. Why is it so incredibly hard to get a test framework to just act like a normal human being and dismiss an overlay if it sees one? How do you guys handle unexpected third-party scripts without writing incredibly ugly test code?

We had our sprint planning yesterday and I actually had to tell my product manager that I cannot take on any new functional testing this sprint because I need two full weeks just to fix the tests we already have.

We built this massive comprehensive UI automation suite over the last two years and management was thrilled with the coverage numbers but our application has been evolving fast and the tech debt of that test suite just finally crushed us.

Every time a dev switches out a component library or renames a class or shifts a table structure we get like 30 tests failing which means my team isn't doing quality assurance anymore but we are just full time locator mechanics literally just updating XPaths all day long so the pipeline stays green.

I was looking at the board yesterday and realized that over half of our total QA capacity is just repairing brittle scripts that broke because of minor UI updates.

It feels like a massive wake up call because tying our test logic to the underlying code structure instead of the visual outcome is a losing game at scale so I am wondering if anyone has actually managed to dig their way out of this maintenance hole once the suite gets this bloated because right now deleting half the repo feels like the only logical solution.