TootSweet

joined 1 year ago
[–] [email protected] 25 points 1 year ago* (last edited 1 year ago)

Where I work in software development, we were about to undertake writing a pretty large application from scratch. Mostly, the company was a Java plus Spring shop with a few exceptions. One team wrote almost exclusively Python, for instance. But as far as I knew, there wasn't any specific policy requiring the use of any particular language.

So as a team, we pushed to write our new project in Python. It was originally my idea, but my team got on board with it pretty quickly. Plus there was precedent for Python projects and Python was definitely appropriate for our use case.

The managers took it up the chain. The chain hemmed and hawed for months, but eventually made a more official policy that we had to use Java (and Spring).

[–] [email protected] 9 points 1 year ago (1 children)

That's interesting. I'd be a little concerned that widespread use of that might create more legal issues for Archive.org that wouldn't be problems if it never caught on much. On that basis, I'd probably not use it.

But I'd imagine ideological opposition to such a thing wouldn't be enough to keep it from catching on either.

[–] [email protected] 1 points 1 year ago

Good call. "Let's burn all blockchains in a fire" is actually a great idea.

[–] [email protected] 6 points 1 year ago (1 children)

It depends on your specific case, of course. That 0.4mm is indeed a good rule of thumb. But also, assuming you're dealing with FFF-printed parts, generally if the two parts slide together along the layer lines, it'll feel just a little looser than if they slide together perpendicular to layer lines. That's just due to the ribbed texture inherent to FFF printing. Though printing at smaller layer heights will reduce that effect and also make the parts fit just a little looser over all.

Aside from that, probably the best advice I can give is:

  1. Measure/calibrate for dimensional accuracy. [Here]'s a random article on the topic that looks pretty good to me.
  2. Prototype. Print once, if it doesn't fit right, adjust the model(s) and print again. Filament is pretty cheap, really. Also, depending on your situation, you might benefit from doing quick test prints just to see how well it fits. If the whole print is going to take 8 hours but by spending 30 minutes printing just part of the final product you can prove you've got the dimensions right, it's probably worth it to do the 30 minute print.
  3. Use elasticity to your advantage. Make latches or attachments that snap into place. That's useful whether the parts are meant to go together once and never come apart or connect and disconnect repeatedly. Another use for elasticity is if you need two arms of one piece to friction-grip another rectangulat piece, angle the arms inward just a degree or two. One word of caution, though. It can be really easy to overestimate the flexibility of PLA. I've ended up once or twice with some pretty hard to open latches.
[–] [email protected] 76 points 1 year ago* (last edited 1 year ago) (9 children)

Step 1: Print a photo of your dad.

Step 2: Hold it up to the camera.

Step 3: Play Resident Evil 7.

[–] [email protected] 8 points 1 year ago (1 children)

The factory grows.

[–] [email protected] 16 points 1 year ago (2 children)

The correct answer to every suggestion that contains the word "blockchain" is "that's a terrible fucking idea."

[–] [email protected] 16 points 1 year ago* (last edited 1 year ago) (9 children)

Look, I right-clicked $1.2 million.

Chromie Squiggle #1468 - an NFT

(Full disclosure, it took a little more than right-clicking to download that image. OpenSea apparently purposefully makes it hard to download images. Not terribly hard, though. Only took me a couple of minutes to figure out.)

[–] [email protected] 5 points 1 year ago

"I"

"could"

"stop"

"any"

"time"

"I"

"want."

Did you really say that with a straight face? I thought that was just what people said to mock people who were clearly addicted.

[–] [email protected] 35 points 1 year ago

I don't think the lemmy.ml admins have been coy about it.

If you go to the lemmy.ml home page, at the bottom of the right column is a list of admins.

The first admin's profile banner is a picture of Mao. And the second's profile pic is a photo of Fidel Castro. The other two don't have profile pics that are explicitly authoritarian communist and I haven't had the patience to look through a whole lot of their posts or anything.

Just a couple of Reddit threads (via libreddit.hu) on the topic: one and two. Unfortunately what they link do doesn't appear to be in the wayback machine as far as I've been able to tell.

[–] [email protected] 24 points 1 year ago (9 children)

Cigarettes aren't good for you and it sounds like you're not ready to hear this, but you are addicted.

1
submitted 1 year ago* (last edited 1 year ago) by [email protected] to c/[email protected]
 

I didn't know that was something a website could do. But on the main page (that is, '/'), I can't seem to refresh. The refresh button in Firefox doesn't work. Ctrl+r, ctrl+shift+r, and f5 all do not work. Selecting the url and hitting enter doesn't work. I haven't tried in any other browsers. Is this supposed to be a feature?

I'm guessing some folks are going to wonder why I'd ever want or need to refresh. Sometimes, one server or community seems to get "stuck". I'll load my main page (I default to "subscribed/new"), scroll for a bit, and then suddenly the one community gets "unstuck" and starts flooding my feed with (all?) posts from that one community. When it does that, it makes the feed basically unusable. I can't expand out images during that time (and even the thumbnails usually go away on posts for some reason.) The posts move down the page fast enough that I can't read titles or click comment links. It's... a problem.

If I could refresh, I'd have an easy workaround. But right now, the best workaround I've found is to copy the url, open a new tab, paste the url into the new tab, and close the original malfunctioning tab. (Ctrl+l, ctrl+c, ctrl+n, ctrl+v, enter, ctrl+pageup, ctrl+w.)

And, yes, if the issue I describe above would be resolved, that would go a long way toward making it less necessary to allow refreshing. But it's the principle of the thing, you know? Is a web app breaking basic browser functionality considered acceptable? Is being unable to refresh the main page intended?

Now, the instance I'm on is still on an older version. (Specifically 0.17.4.) If any of this is addressed in later versions, that would be awesome news.

Edit: In retrospect, it seems I should have done more experimentation before posting this. Now that I'm trying things, refreshing is working. It takes a second or three to start refreshing, though. I guess my theory at this point is that when I'm experiencing the issue mentioned above, that few seconds turns into a much longer amount of time. (Minutes, I think.) And I just never waited long enough to see that refresh eventually does work. I guess that kindof invalidates much of what I said here, but in case others have insight, I'll leave this post up.

1
Top 5 quotes (latte.isnot.coffee)
 
  1. "Perfection is achieved, not when there is nothing more to add, but when there is nothing left to take away." - Antoine de Saint-Exupéry
  2. "All secrets become deep. All secrets become dark. That's in the nature of secrets." - Cory Doctorow, Someone Comes to Town, Someone Leaves Town
  3. "No man ever steps in the same river twice, for it's not the same river and he's not the same man." - Heraclitus
  4. "Property is theft!" - Pierre-Joseph Proudhon
  5. "One of my most productive days was throwing away 1000 lines of code." - Ken Thompson

That last one makes it clear what I do for a living, but in software engineering, it's a good one to keep in mind.

view more: next ›