sping @ sping @lemmy.sdf.org

Posts

0

Comments

243

Joined

2 yr. ago

But use type annotations everywhere and make sure your code is always checker clean (with checkin or PR CI hooks). And don't turn off any lint checks through laziness, e.g. docstring checks. Even for a solo dev it's always worth having everything typed, checker clean, and docstrings (even if they only effectively say "this thing really is what you'd assume"). It all saves time and effort in the long and even medium term.

I've worked on serious large scale Python projects and frankly it's been very pleasant and productive, but only with the above conditions.

Black/white as bad/good is a clear case where there is a clear logical reason to change IMO. That perpetuates unconscious bias.

And yet there's a big push to rename git "master" branches, which have no slave connotations and are more analogous to master recordings.

Its not like I'll fight it, but it's stupid.

You do? Because I don't. There is nothing racist about the concept of master. Is a masterpiece racist? Are master tapes, Are post-graduate degrees racist? We may as well declare "work" insensitive because slaves had to work.

Don't get me wrong, there are many terms we should adjust. I just can't see how "master" is one of them.

1g prerolls are actually the only round-number metric sale I see.

They work better than cars do. Not long ago on my bike commute in a blizzard I had to keep getting off to help get stuck cars moving again, then if happily ride off...

And handling the cold is easier when riding than walking to and waiting for trains and buses because you generate your own heat. People ski in those conditions. It's just a matter of the right clothes and equipment and not being soft as fuck.

It's also been UK law for a long time.

Yes, there is one now! And if you squint really hard the coffee one brushes against the question.

It was about doing something seemingly unrelated and simple that helped to learn something more profound. Not seeing it in most (any?) of the answers.

I didn't understand the question so came to read the replies out of curiosity but couldn't work it out so searched the web for what wax-on-wax-off meant. Now I think nobody else understood the question either.

Shush! Lennart might hear you!

Many political questions are reasonable to disagree on but many others are also ethical ones with gaps that cannot be bridged.

I'm just an emacs ... enjoyer (...?) and I just don't understand the post. I'm pretty sure buffers here refer to something different from emacs buffers as they're completely unrelated to clipboards. Then from a quick scan of the plug-in mentioned it seems to mimic the clipboard ring emacs has had for many decades (always?).

Basically I have no idea what's going on here.

Well lvm makes a shit filesystem and btrfs is useless at volume management.

For paid service I like the simple "of course" recognizing that is what I'm here for and it's normal. No faux generosity nor implication of a tolerated imposition.

You owe me

So by saying you are welcome to their action, people are actually saying the opposite? That you are not welcome to it at all? You're saying it's ironic?

It varies regionally. While "you're welcome" is not at all unusual in the UK, it's nowhere near as expected and standard as it is in the US.

I often hear "not at all" as a response, just like "de nada". It's also common in the UK not to respond at all, as the thanks are expected.

Huh, to me, YW is much more gracious and positive that you're happy to do it, while NP is more like "it was a tolerable burden".

Though for paid service I don't like expected faux enthusiasm. I think "of course" is classy and not demeaning then, meaning "it's what I'm here for".

That was the point they were making. GitHub is to git as the snap store is to snap, albeit there are existing alternatives to GitHub.

So when you said sucrose you really meant various sugars. Because sucrose is a molecule and all the same, and what it comes with is what makes the difference, as per OP's question.