u/booowser

My 10-month-old has accumulated so many toys that our living room was starting to look like a daycare that had lost a fight.

The weird part was that she barely played with any of them. She would touch one toy for about 20 seconds, move to the next, and then crawl away to investigate the laundry basket.

Last Sunday, I put almost everything into two storage bins. I left out one board book, a ball, a soft block, a set of stacking cups, and one crinkle toy.

I fully expected her to get bored and complain. Instead, she spent ages dumping the cups, putting them inside each other, knocking over the tower, and trying to fit the ball into the biggest cup. I actually finished my coffee while it was still warm, which felt suspiciously luxurious.

Now I’m wondering whether toy rotation actually works or whether she was simply overwhelmed by having too many choices.

How many toys do you leave out at one time? Do the favorites stay permanently, or does everything eventually go back into rotation?

I’m still learning how to QC properly, and sometimes I’m not sure which flaws are actually important versus minor details that aren’t noticeable in real life.

Would anyone be willing to share their personal QC checklist or tips? What do you always check first before giving a GL?

I think a simple guide or PSA could be really helpful for newer members too.

Saw InfiMaker K1 pushing their InfiStudio software, apparently it can generate toolpaths from images or text. Supposed to flatten the CAM learning curve quite a bit. Speaking as someone who's suffered through more Fusion 360 CAM tutorials than I'd like to admit, color me intrigued but skeptical. Sounds great on paper. But I'm not sure how far something like that can really go once you get into actual machining decisions — workholding, stepover, feeds and speeds, tool selection, all of it.
Fine for simple geometry maybe. But once you're into irregular parts with angled faces and multiple setups, that's where most systems fall apart. CAM isn't just drawing toolpaths — it's sequencing, judgment calls, knowing when to break a rule. And I've seen what happens when someone runs a machine without really understanding what's going on under the hood. Doesn't take much to end up with a broken tool or a ruined part.
Anyone actually used InfiStudio or anything similar on a real job yet?

I don’t think my main problem is not caring about studying. It’s that I sit down, open my materials, and then somehow waste 40 minutes deciding what to do first.

Pomodoro helps sometimes, but only if I already know what I’m reviewing. Vocab apps help sometimes, but only if I actually come back to them. Cheat sheets help before exams, but making one from messy notes takes forever.

Has anyone found a simple study routine that makes it easier to start? Like timer first, then vocab/review, then a short summary sheet or practice questions?

I’m trying to make studying feel less like opening ten tabs and more like entering one focused mode.

We all know windows laptops take a major performance hit when unplugged, even on the best performance mode. I remember reading a post arguing that because windows laptops use x86/x64 compatible CPUs for backwards compatibility reasons and that makes them less efficient. This forces aggressive power throttling on battery just to keep the device alive for a few hours. But here’s what puzzles me, a upcoming laptop geekbook m16 claims its "dynamic tuning technology" allows the laptop to sustain a full 55W TDP even on battery when it matters most.

But if the underlying architecture itself is the efficiency bottleneck, how are they bypassing this? Really looking forward to seeing some reviews and benchmarks once this drops. What do you guys think?

I've been so busy lately I almost forgot to confirm prices with two suppliers. One provided samples, and the other had a very low price but a minimum order quantity. However, while the suppliers were negotiating prices with us, acciowork purchasing agent proactively followed up, using the product requirements I had previously provided, and secured the most cost-effective minimum order quantities for each supplier. I can hardly believe I'd managed to negotiate prices with two suppliers without even realizing it!
Would you trust an agent to handle this kind of workflow? Is manually reviewing each supplier's information really the most reliable method?

Been thinking about this a bit after my last project didn't really work out.

I spent around 4 months on a custom kitchenware product. Research, design, sampling, launch. At the time it felt like a decent idea. Similar products were getting mixed reviews, and I took that as a sign there was space to improve something.

It launched in November. By January I had sold 34 units and ended up sitting on unsold stock.

Looking back, nothing really broke. It was more that I misunderstood the space completely. I assumed mixed reviews meant opportunity, but in reality it was already a pretty crowded category with established brands and price pressure I didn't really factor in.

Most of my early thinking was pretty loose. A mix of browsing reviews, looking at competitors, and just going off gut feeling.

After that I didn't jump into another product right away. I just spent more time trying to understand what I was actually missing the first time.

Before committing again, I slowed down a bit and looked at demand more carefully. Not just search volume, but things like pricing ranges, trend direction, margin after MOQ, and how the top listings were actually performing over time.

I used Jungle Scout for basic volume checks, Keepa for price history, and accio work here and there just to pull demand signals, pricing ranges, and trend info into one place so I wasn't switching between a bunch of tabs all the time. Mostly just for getting a clearer overview, not anything fancy.

What stood out was that I had been looking at products too early without really understanding where the market pressure was already strong.

The next direction I looked at wasn't completely different, just more adjacent and with fewer strong players already sitting on it. Also a clearer gap in terms of features people kept complaining about.

Still early days, nothing dramatic. But the process felt different this time. Less guessing, more structured reading of what was already there.

I think the main thing I missed before wasn't effort, just enough clarity on demand before starting to build.