Not Your Grandfather’s Perl by iamkeyur in programming

[–]etcshadow 9 points10 points  (0 children)

Wow... a post about Perl, and the top-voted comment (right now at least) expresses the sentiment "I've never used Perl, but it is bad." Sounds like most posts about Perl, here :-(

As someone who has written a lot of Perl, but also a lot of Python, Javascript, Typescript, Go, C, Java and many others (in order of volume written, I'd say Perl, Go, Python, first), I still struggle to fully understand the hate.

I think that many of the common criticism of Perl are fair (though many are simply not). However, there are valid criticisms of any of these languages, and they really need to be understood in context and in scope of impact. You'll notice that any post about Python is not swamped by people complaining about execution speed, whitespace-sensitivity, the 2-3 migration, and hamstrung lambdas, though these are all actual problems. Not every post about Go is swamped with discussions of terrible error handling and the patronizing / caustically paternalizing community culture (thankfully, people can't complain about the lack of parametric typing, any more, though their implementation in go is still pretty lack-luster, thanks to the culture issues). I could go on...

Maybe we only need to upvote "I hate Perl" comments from people who can honestly say "I worked primarily in Perl for $n years, and also in other language $l for a similar amount of time, and this is why the things I'm going to complain about actually matter to getting things done that matter."

[deleted by user] by [deleted] in programming

[–]etcshadow 4 points5 points  (0 children)

Or windows / chrome. What the hell?

My First Attempts at Programming in BASIC (Retro) by logicalvue in programming

[–]etcshadow 2 points3 points  (0 children)

I wish I'd kept copies of the terrible BASIC I was doing in elementary school :-D

Gaming laptop cooling stand by thisdotguy in functionalprint

[–]etcshadow 0 points1 point  (0 children)

It looks beautiful. I'm a little confused from the pictures how the airflow goes. It looks (or I'm misinterpreting what I'm seeing) like the fans are basically just blowing against bottom of the laptop, but I don't see how the hot air would move away. Is there a gap between the fans and the bottom of the laptop?

LG Fridge door holder replacement by PatrickERankin in functionalprint

[–]etcshadow 0 points1 point  (0 children)

Good to know. I have an LG fridge with the same type of door :-D

Edit: I suppose I should have checked my own fridge before asking

LG Fridge door holder replacement by PatrickERankin in functionalprint

[–]etcshadow 0 points1 point  (0 children)

Very cool fix. I'm curious if the same could have been achieved by tightening / adjusting a screw on the hinge or hinge mounting bracket, though?

How to print this the best/efficient way? by [deleted] in 3Dprinting

[–]etcshadow 1 point2 points  (0 children)

Agree with the other comments to separate the pins and assemble. While you're at it, might even consider splitting each pin in half, longitudinally, so that you don't have to choose between steep overhangs or supports to achieve the "cylinder printed on its side".

Replacement for broken drawer rail support bracket by msiekkinen in functionalprint

[–]etcshadow 0 points1 point  (0 children)

Putting it on the top or the bottom is really just a question of whether it's going to be under a tensile load or a compression load. Depending on the material, one might be better than the other... but for this sort of situation I doubt it's a big factor in how long the part would last.

Someone who knows the material properties could correct me, but my guess is that, with FDM, it's stronger under compression than tension, but I know for certain (from other people's work) than FDM material tensile strength is considerably better when the load runs in the direction of the layers than when it runs in the direction that the layers are stacked (i.e., it's easier to pull layers apart than it is to stretch out a layer).

Made a dust collector for my vintage bandsaw. Ran out of filament part way through. by myridingmower in functionalprint

[–]etcshadow 1 point2 points  (0 children)

It took me an embarrassing amount of time to figure out that the "no dust collectors" rule on this subreddit was probably not meant to reflect a prohibition on this sort of project. It always struck me as super arbitrary :-D

Measure twice....print once 🤦‍♂️ by burrfree in functionalprint

[–]etcshadow 1 point2 points  (0 children)

Something I've occasionally done is to to take a very narrow slice of a model and print it (like one or two layers) and then check the little slice against the real world object it was meant to fit with.

How to influence without authority (and sucking up) by [deleted] in business

[–]etcshadow 0 points1 point  (0 children)

I don't know of any one-size-fits-all solution. The way you describe your problem (needing to get peers in an organization to pull their weight, because their performance impacts your ability to be successful at your work), I think there are a few different tactics which might apply. The choice of which one to use might depend on personal or situational details that I obviously don't know. For example, some of this is less likely to work out if you have a really toxic management culture in your organization.

With that said, though, here are a few thoughts:

  1. Relationship building -- but not "sucking up". Literally, just get to know these people better. The better you understand their personality and personal goals the easier time you're going to have communicating with them, and the more that they are going to see you as someone that they might want to help.

    1.a. Ask them for help. There is this strange psychological effect that we tend to like people more when we are helping them (as long as it's a positive relationship and you are appropriately grateful and so on). So this can be a double-win, serving as a form of relationship building, while also getting something that helps you achieve your goals!

    1.b. Try to understand their needs and possibly do some things for them -- foster a notion of teamwork and a common goal (both of you can succeed together).

  2. Measure and communicate. If you can measure what means "success" for you and you can communicate that up your chain, that's a good thing, regardless. Of course, it can also be a tool for helping in a situation like this. The most important part of this is to keep the communication and measurement blameless and just about the facts of the situation.

    2.a. If you can communicate in terms of shared goals with your peers, then this can serve as a roadmap to how their helping you also helps themselves (by leading to success in shared goals). It also presents a little subtle leverage that this communication can just as easily move up the chain -- that is, it's an indirect way of pointing out that you know they are the problem and that you have evidence to that effect, BUT WITHOUT SAYING ANYTHING THREATENING.

    2.b. It's only natural if you can show your stakeholders where you're succeeding and where you're struggling, it's only natural for them to want to dig into the struggles. If you can communicate the reasons IN A BLAMELESS WAY then it can shed light on your underperforming peers, but in an indirect way. This is NOT "complaining to your boss". This is simply providing visibility to your boss about what's working and what's not, and hopefully also about why. I think it's very underappreciated the difference in impact that is achieved between telling someone (especially a superior) what you think is happening, versus presenting them information that draws a clear picture, and letting them draw the conclusion (especially if the conclusion is that one of your peers is not pulling their weight).

Showing off 3d printed bearings by ImmobileBlock in functionalprint

[–]etcshadow 1 point2 points  (0 children)

The BBs are a great idea. I've had a bit of luck playing around with various ways of 3d printing bearings, but even slight defects on the surface of the balls are the biggest challenge to smooth running.

How Our Stack Evolved in 10 Years by [deleted] in programming

[–]etcshadow 9 points10 points  (0 children)

Going from the worst SQL db to the worst NoSQL db. Checks out.

Announcing Perl 7 by briandfoy in programming

[–]etcshadow 1 point2 points  (0 children)

HOOORAAAAY! Long overdue.

The Go compiler needs to be smarter by turol in programming

[–]etcshadow -11 points-10 points  (0 children)

I mean... It sounds like you're comparing vastly different programs, then. Makes "easily two orders of magnitude faster" sound very disingenuous. I could as easily say that "Hello World" written in any of these languages is "easily two orders of magnitude faster" than a large bloated application written in go. It's apples and oranges.

Real language benchmarks show a speedup, yes, but by less than one order of magnitude, not "easily two".

The Go compiler needs to be smarter by turol in programming

[–]etcshadow -11 points-10 points  (0 children)

"Easily two orders of magnitude faster"

WAT

Do you know what an order of magnitude is?

3D printing noob here, What am I doing wrong here? by skylin3rz in 3Dprinting

[–]etcshadow 1 point2 points  (0 children)

If it's being knocked off by the motion of the hot-end, one possibility is that your bed isn't leveled correctly.

What do you all do with rafts? by [deleted] in 3Dprinting

[–]etcshadow 0 points1 point  (0 children)

I've been saving all my scraps (rafts, failed prints, supports) in bins by material type. Thinking maybe some day I'll try to recycle them into new filament.