AliasVortex @ AliasVortex @lemmy.world

Posts

0

Comments

121

Joined

2 yr. ago

I wanted to echo this by saying that my lab stated as 4 bay Qnap NAS and evolved into repurposed consumer hardware as my interests and needs changed. My current server is an Optiplex that I bought for being small, quiet, and hanging lots of cores and my NAS is just my old gaming PC build with an HBA card (for extra SATA lanes) stuffed into a fancy case. A server is any computer that you say is a server (ideally one with functional network connectivity).

Boost's ads are mostly there to support the developer, but a one time purchase ($5 irrc) absolutely makes them go away.

That is why one must also consider the relative dimensions in space when constructing a time machine...

Actually, now that you mention it, Worm is this to a tee. Worm is still probably one of my favorite reads to date; highly recommend (it's like a The Boys with less evil corporations and more X-Men)!

Only for the first 6 books or so, was listening to Persepolis a few weeks ago and had to do a double take when the reader finally pronounced it with the hard g ("gim ball").

I figured it couldn't be any worse than the Black Prism reader absolutely butchering javelina (ordinarily the J makes an H sound) a few books in

Also a 2.4 owner, I bought the 350 LDO kit from Fabreeko and it was delivered back in August. Getting it assembled and dialed in was certainly a process, but aside from that it's been an absolute workhorse (I think I've got something like 200+ hours of print time in; completely blows my Thessian Ender out of the water in terms of both speed and reliability). You certainly can tinker with it and make it a project printer, but they print really well stock. The only mod I'd say is anywhere near required is swapping out the magnetic bed meshing sensor, only because the sensor readings tend to drift as the sensor gets hot. You can totally work around it, by waiting for the printer to warm all the way up or cool down to ambient before printing, but I'm impatient plus the mouse switch mod (Klicky) tends to be more reliable and accurate (plus it's temperature agnostic).

Don't get me wrong I've totally modded mine: swapped out some of the plastic parts for metal ones, added a brush to clean the nozzle before my print (makes for more consistent Z heights), replaced the panel clips with snap latches, but none of it was required to make the printer print better (mostly just to make maintenance easier and partly because it looks cool).

The new hotness in the open source MMU space is ArmoredTurtle's BoxTurtle project, which seeks to be an open source equivalent of the Bambu AMS. I'm still working on the parts for mine, but from everything I've seen the build is way less fiddly (and as a result more reliable) than the ERCF.

Seconding kit Vorons. While they certainly aren't the cheapest option, they aren't that much more expensive than other higher end core XY machines. Fabreeko has the 250/300mm Trident kit at 1.2k and 350mm 2.4 at 1.4k + an extra $150 or so for printed parts. Compared to the new Core One at between 950 - 1.2k or the X1C also at 1.2k you're looking at an extra $150 to 350, but that also comes with build volume increases (both the Prusa and Bambu are at roughly 250 mm³). Definitely wouldn't recommend them as a first printer, but Vorons are shining examples of what's possible with open source (and they're absolute workhorses too).

Highly recommend them with glowing praise for being all around fantastic (they also run sales on the regular, though kit deals are usually reserved for special occasions like black Friday, or Clee day)

That's awesome! Wishing you both the best!

Lol, it actually kind of is: https://en.wikipedia.org/wiki/Max_Steel

E3D makes pretty decent stuff and is based out of the UK- it's just annoying and expensive to get ahold of everywhere else (insert generic grumbles about Revo nozzles). Otherwise, I've had good luck with Phaetus nozzles, but I'm not sure that pricing/ availability looks like in the UK.

Lemon it's January.

Why do you print like you're running out of time?

Not the original poster, but it's on the British Museum's channel: https://youtube.com/watch?v=WZskjLq040I

Correct. ASL is fascinating because of how visual it is and just how much you can convey by taking the same sign moving it differently (for example you can describe a rough flight by making the sign for airplane and then bouncing it up and down).

I might also add that in addition to your facial expressions form grammar structures, body language (of which facial expressions are a part) also conveys tone/emphasis. For some concrete examples of how this provides context: the sign for thin becomes anorexic if you suck in your cheeks/ stomach while you make it. Similarly, fat can become obese if you puff out your cheeks and slouch a bit while you make it. Or on a more topical note, the sign for fire is made by wiggling your fingers in an upward motion in front of your chest (visual), the size of your sign sort of describes the size of the fire your talking about, small slow movements might describe the dying embers of a campfire, while larger (pushing towards of out of the area you normally sign in) more frantic movements would be used to describe a miles high inferno.

Well that might explain some things.

Not to throw shade at your company but that process is so backwards that it's no wonder the engineers are sparse on the details. I saw another comment likening software development to a crossword puzzle, which is a pretty good analogy. To further it, changing software once it's done is like trying to swap out a clue/ word once the rest of the puzzle is built. It's theoretically possible, but depending on how the puzzle is designed, it can range from an absurd amount of work to nearly impossible. Given the way you've described the state of things, your engineers are probably low on goodwill to boot.

I've worked on cobbled-together crunch-time hell-projects and the last thing I'd want after getting free would be a random BA coming to me about details that more than likely packed with the project PTSD and would very much like to forget. Doubly so if it's issues that I bought up early in the design/ development process (when they would have been comparatively easy to fix) and was dismissed by the powers that be. I can only speak for myself, but I can only take so much "that's not a priority", "we don't have time for that"/ "we'll see if that becomes a problem in the future and deal with it then" before I throw in the towel, stop keeping track of everything that's wrong, and just bin the entire project as dumper fire run by people who would rather check boxes than make things better.

This is excellent advice! I want to underscore that Engineers are very often much driven by the how's and the why's of things. I'll admit to judging people based on how they answer those sorts of questions. From a project perspective, I'm far less interested in doing something if the why of it can't be adequately explained to me. Similarly, I'm far more willing to take a "you know, I'm not actually sure", than a "we do it this way, because that's the way we've always done it" (the latter is probably the fastest way to tank any respect I might have had).

Was trying to compose a similar statement on that lack of details. Like, my background is scrum/ agile software development and if a random BA called me up out of the blue for project details, my first response is going to be "I'm busy, talk to my scrum master and/or manager" and failing that it's likely going to be the minimum amount of information required to get said BA to leave me alone so that I can get back to work. Plus, unless I know that my audience has the technical capacity for low level details, I tend to leave them out (I don't mind answering questions, but I also don't have time in my life to spout information that's going to go in one ear and out the other).

There's some community history, but the short version is that the US patent office issued Slice a patent for surgical tube in hot ends which Slice has then used to litigate away competition. As a result, Slice's actions have not sat particularly well with the parts of the 3d printing community that value open source and community innovation.

there's some debate as to the validity of that patent as there's evidence that this idea dates back to the early reprap movement. Source.

Additional commentary