pfhorge

This is called the "interference effect", and it seems like it's increasingly thought to be mostly a non-issue: https://www.strongerbyscience.com/research-spotlight-interfe...

I have no evidence, but I suspect that's likely to get the best outcome, as far as the factory's quality level is concerned. They're pretty heavily optimized for a particular set of processes, and anything that departs from that happy path seems likely to increase risk.

We had a frank conversation with the builder about costs, as well as what was and wasn't worth fighting over. Some items were able to be repaired without impacting the budget by subcontractors that were already coming in to do other things. Other things we didn't care enough about to make a fuss over (like the roof line not matching up right on the back side of the house, where no one will ever notice). Some things we asked her to fix at her expense.

We were very aware that big projects, be they software or home construction, don't ever go perfectly, so we made a conscious effort to stay calm and solution-oriented through the entire multi-year process. We came in very slightly under budget, and things that need to get addressed are getting addressed, whereas a lawsuit would have turned things adversarial very quickly.

I built my current house recently, and our builder used a prefab factory in the region for some of the construction. I would _never_ do it again. The process has all the pitfalls of the waterfall software development model, but at the end you have to live in the failed project!

It took months for the factory to do their pre-build engineering, and that's after they started the process using plans from my architect. The companies building these modules tend to sell mostly from their own catalog of floorplans and modules, so they don't have a strong incentive to hire skilled architects for the relatively small amount of custom work that comes in (I fell into this category). I'm led to believe that they hire draftsmen instead of architects.

They built one of the modules a foot too long, so it hangs over the edge of the foundation. They also messed up the roof line, so some guttering and geometry had to be changed for the garage that was stick-built onsite. They did all of the drywall wraps around the windows incorrectly. Every single door was hung incorrectly, some with chunks taken out from bad routing. The vinyl plank flooring has bubbles because they didn't float it correctly. They omitted electrical features that were on their own drawings. They ordered a few wrong windows, so they charged me anyway and just laid them on the floor when they shipped the module.

It'll all be fine at the end of the day, but the parts that were built onsite are all so much better. No cheaper, mind you, but faster and with much less drama. Maybe there are some parts of the industry that do a lot better, but I kind of wish I'd listened to my dad when he said "the pioneers take the arrows".

Somebody in my organization got very interested in Dgraph in its 0.7 or 0.8 days. The version was marked as "production ready", but it was an absolute trainwreck.

We were modelling individuals and contacts between them, and the cluster would constantly break with dataset sizes that should have been easily managed. There was clearly something wrong in the storage engine, because we saw insane disk space usage. Dgraph consumed 10s of TB for something that should have taken < 100 GB.

We were one of the largest installations at the time, and were working with the core development team, but they were never able to resolve the issues.

We eventually had to tell management that there was no way we'd be able to operate the thing given its disk space consumption rate, so we had to delay project delivery to rip out Dgraph and replace it with Postgres.

Surely it's better today, but I'll never use it again by choice.

Just my two cents, but if I was your coworker and you told me the situation, I can virtually guarantee that my annoyance would instantly transmute into some degree of sympathy and tolerance. It goes a long way to know that you're aware of the problem and feeling some stress yourself. Suddenly it isn't something you're inflicting on me because you're oblivious.

AndroGel made my skin start to peel. Injectable testosterone cypionate is far less danger to those around me, less fuss overall, and so much cheaper.

When I was a kid, I got to take some Logo programming classes at Purdue. I can't imagine how much more intuitive and visceral it would have been if we'd had Minecraft instead of blank white screens.

I happen to play Minecraft now, and I just finished writing a 3D Perlin noise generator in Lua so that my turtles can build structures with some randomization. I'll be adding code to pixellate my smooth, mathematical paths into minecraft blocks using Bresenham's line algorithm. I've also written programs to do highly efficient mining with minimal effort on my part. I've seen programs written by other people that control a fleet of turtles from a central computer, and programs that run complex farming operations. There's so much breadth of possibility with something like Minecraft and ComputerCraft.

If Minecraft is like playing with Legos online with your friends, ComputerCraft is like Mindstorms. I envy the kids who start out on this stuff.