I'm a child of the '80s, and as much as I still enjoy some of the animated cartoons (Voltron, Transformers, G.I. Joe, Masters of the Universe, Mighty Orbots, Blackstar, etc.) and other kids' shows (Pee-wee's Playhouse, Mister Rogers Neighborhood, Sesame Street) of that era, I have to say that newer shows are generally good, and in some cases better than some of the stuff that we watched "back in the day."
3D-printing action figures is something that I've wanted to do for a while.
In case anyone with knowledge or expertise in printing action figures happens to read this, I'd like (1) to scan an existing, articulated action figure... somehow, perhaps using 123dapp Catch (123dapp.com), (2) to modify the resulting mesh using 3D modeling software such as Blender and (3) to make articulated 3D prints of the modified action figure.
Please share any advice, recommendations or links that might be useful. Thanks in advance!
Atmosphereum writes: I have a decade of experience as a Java developer. Lately I've noticed that most software developer openings in my area want.NET rather than Java experience. Is this a common trend? I'd rather not relocate, so to boost my employability in this region, should I consider jumping onto the local.NET bandwagon? Has anyone else here made the leap from Java to.NET? How would you recommend doing this?
Atmosphereum writes: At numerous organizations I've noticed that software releases often involve lengthy downtime windows — sometimes hours in length — because of schema changes in production databases. The schema changes often seem to be fairly simple, like adding a few fields to each of a few tables. At the risk of making De Forest Kelley roll over in his grave, I'm a software developer, not a DBA. What techniques are often used to minimize production database downtime during schema changes?