u/After-Condition4007

Had about $280k split between VYM and VTI in my taxable brokerage. Kept buying VYM because quarterly deposits felt like income, even though I should've known better. My wife pointed out I check the dividend calendar more than our grocery list.

Exported my statements, threw them in a spreadsheet and MuleRun to compare after tax returns. Over the past 5 years VTI beat VYM by roughly 7 points annualized. VYM cost me ~$4,500 this year between federal at 15% and California at 9.3%. At 7% growth that annual drag compounds to roughly $62k over a decade. Tried to tax loss harvest the VYM lots but half are still green, so that plan went nowhere. I'll probably just redirect new contributions and let the rest sit.

There are enough balcony solar + storage systems on the european market now that the spec sheets start to blur together. Having spent the last two months actually living with one (and helping a coworker buy a different one), i want to share what ended up mattering more than the headline watt numbers.

First, why MPPT count matters at all. Each tracker independently finds the maximum power point of whatever's connected to it. If you have one tracker and two panels in series, partial shade on one panel can pull down more of the array than you expect. With more independent trackers, the loss is easier to isolate. On a balcony where you might have a south rail with two panels and a west wall with two more, that matters more than the clean showroom watt number.

The usual balcony storage suspects i looked at were from Jackery, Anker, Zendure, EcoFlow, and Marstek. Specs change fast and firmware changes even faster, so i wouldn't treat this as a buyer's guide. My actual takeaway was simpler: count the independent trackers, check how they behave under shade, and don't assume four input plugs means four fully independent MPPTs.

Things i would actually compare if i were buying again, in rough order of importance.

How does the system behave when one tracker sees zero input for hours. Some inverters seem to wake idle channels periodically, which can cost you a few watt hours. On my SolarVault 3 Pro i haven't seen obvious idle channel wakeups yet, but that is one unit on one firmware, not a lab result. This is exactly the kind of thing reviews rarely catch because you need a boring shaded day and a long log to notice it.

What's the minimum battery cycle depth the firmware enforces. LiFePO4 chemistry tolerates deep cycles fine but most of these systems reserve 5 to 15 percent at the bottom for safety. That's fair but it changes your usable capacity by a meaningful margin and it's almost never on the spec sheet.

Is there a real time API or just an app. For anyone wanting home assistant or grafana integration, "we have an app" is not the same as "we have an API". This is where the field varies a lot more than people expect, and where i think the next 12 months will see the biggest shakeout.

Honest unknowns. I haven't personally tested the EcoFlow Stream Pro under heavy shading, only on a clean south array. And the Anker firmware updates fast enough that anything i wrote about it three months ago is already out of date.

If anyone has long term shading comparison data across two of these systems running side by side on the same balcony, i'd genuinely like to see it. That's the comparison i can never quite get from reviews.

Im the head of marketing at a small outdoor gear brand. Every monday morning used to start with 3 to 4 hours of manual trend research. TikTok hashtag pages, IG creator performance, 6 competitor blogs via rss, all dumped into a doc the rest of the team would only half read because by the time it landed it was already tuesday.

Spent 2 weekends last month rebuilding this and ended up with a 4 agent setup that runs at 6am every monday so the team has something readable before standup at 9. Sharing because the build process took me through more tools than expected.

Make and n8n. Gonna group these because i hit the same wall with both. Beautiful for stitching apis i actually have. Painful for "open this page in a browser, scroll, grab the top posts." The tiktok and instagram parts were the problem. Both platforms want clean apis, and the public data on those is mostly behind login walls or rate limited. I know there are community nodes for some of this but i didnt want to maintain someone elses code when it breaks. If your data sources are all api friendly, either of these will serve you well. Mine werent.

Bardeen. Browser native, exactly what i needed for the scrape parts. Setup was genuinely easy, just point at what you want and go. But scheduled runs are limited on my plan and i couldnt chain it into a single output the way i wanted. Also the outputs lived in different places which meant i was still manually stitching things together. Closer but not quite.

MuleRun. Set up a multi agent workflow that runs every monday 6am. Agent A opens 5 hashtag pages on tiktok and pulls top 50 posts. Agent B logs into my IG via a browser extension that uses my existing session and grabs top performing creator posts. Agent C pulls 8 competitor blog rss. Agent D compiles the digest into a shareable page my team opens at 9am. Before this i spent 3 to 4 hours every monday morning and still missed niche trends. Now its 10 min to skim the auto digest. Drawback worth flagging, when an algorithm changes (eg tiktok hides hashtag view counts for certain regions) i have to retune which signals matter or the digest gets noisy. Happened once already and i lost half a morning fixing it.

Final stack is mulerun for the full monday digest, n8n for the longer term campaign reporting that hits clean apis, and a shared drive that both write into.

What actually mattered in the build, in case youre rebuilding something similar.

1. Define the output before defining the agents. I wasted a week trying to design the perfect pipeline and only after did i realize my team needed bullet points by category not a 6 tab spreadsheet. Output first, agents second.
2. Login state matters more than scraping power. Half the data i needed required being logged in. Tools that drive your actual browser session avoid the whole captcha and bot detection mess.
3. Schedule + recovery + diff. Schedule is obvious. Recovery means what does the system do if one agent fails. Diff means tell me whats new vs last week, not just whats there. Without diff its just noise.
4. One shareable page. The team isnt opening a notion db. The team is opening 1 link. Make sure the final output lives at 1 url.

Considering adding a 5th agent for influencer outreach next, if a few of the trending creators line up with our brand. Havent committed.