+1 to this. I built a few deb packages at a previous company. It was a solid packaging suite but good lord was it a pain to work through

I see you had no real interest in good faith discussion. I change my recommendation,jus do whatever the rest of your mod staff decides.

People like you are why leaving reddit was a wonderful idea.

Ahh I see.

How about your shove your prank up your ass, bro?

And that’s where this conversation stops.

I don’t need you guessing my age and I very much don’t need you acting like some kind of familial figure giving me a lecture about something I know full well how and why I fucked up on and owned up to.

Good day to you.

It was the way in which you personally stated it and now continue. If that wasn’t your intent then I apologize for saying it was. Nonetheless, I have nothing more to say to you given this clarification.

This feels oddly aggressive. Given I merely wanted to give my answer and cover some uncertainties I had regarding the situation and have done so with op, I’m going to disengage now as I neither feel up to nor deserve to feel attacked.

1. that’s why both parties must be interviewed separately of course. That will give you both perspectives allowing for an informed decision to be made.

2. For this specific situation I would say 2 is sufficient if it’s clearly an accident according to both parties. 1 is sufficient if it seems to be intentional based on review.

3. that’s why I addressed if the rule was stated. If it’s not there, you’ll need to weigh in on the situation and make the judgment call. Then the rules have to be addressed to show the club’s stance on the matter and the consequences. After that, whatever consequences are stated by the rule are how each incident is handled no exceptions.

4. Up to you and the mod staff, but were I a mod I’m aware of no situation in which a racial slur is used as an actual prank. To drive home a point though, I am very well aware of situations where I’ve make a joke that didn’t land well. I intended it to be funny, but it came across as weird and creepy. I apologized and it was an accident. Fortunately, that was taken into account when the situation was reviewed.

I would disagree.

Having that rule written out allows for people to have a no mercy policy in rule enforcement. It’s easy enough for us to say “no sexual harassment is common sense” but by having it, there are absolutely no uncertain terms regarding the club’s stance and how they will rule on any incident.

People are dumb, while I would prefer to fix that to date the only working solution I’ve found is to make it clear what expectations are instead of relying on uncommon sense.

That’s a fair point, but in the business world you’re a cog. They don’t care about you they care about what you add to the company. Basing anything off of business is hardly a reasonable thing to consider.

That being said, I did update my response in a separate thread, (og left for posterity) i broke it down based on if the rule was established or not and then based on independent discussion with both parties to try to determine intent. Accidents happen and the response should take that into account.

Without knowing your ruleset, I can see two ways of handling it.

Situation one, the rules did not call it out. If this is the case, it feels a little (like 5% if you can quantify feelings) bad to immediately ban someone for violating a non-exist rule. Particularly if it could have been an accident.

Situation two, the rules called it out. It could be worth talking with both people separately to determine intent. If it seems that the harassment was intentional, bannable offense. If it seems like he was not trying to harass her, strict talking to with a strike. Accidents do happen and a nuke option for an accident could lose a loss of other members out of fear.

Guy chiming in but

Gut reaction says yellow flag, pull him aside tell them the behavior is not acceptable as warning and that a second incident will be cause for a ban from all club activities.

Gut also says, defer to the lady mods if they have a preferred method of handling it.

Ahhh gotcha gotcha. I was doing this by default in my python testing, glad I was doing things right

You get it!

Fully agreed things need to get shipped but that’s why I’m a fan of test driven development. You’ll always have your tests written with your feature.

Then again even if someone does it after as long as you write a test every time you write a feature you’ll eventually have the code base covered.

Input coverage is new to me, mind linking me some info so I can learn? (Yes google exists but if someone has the low down on a good source I’d prefer that)

Wrong.

Try “Security focused DevOps Engineer” and try making better tests.

That’s why test coverage exists and needs to be a mandated item.

I have absolutely no patience for developers unwilling to make good code. I don’t give a shit if it takes a while, bad code means vulnerabilities means another fucking data breach. If you as a developer don’t want to do what it takes to make good code, then quit and find a new fucking career.

Really need a okbuddymoron sublem

Won’t lie I’m getting sold on this via this discussion

I mean, security is an unintended outcome of it. Any kind of isolation of packages provides a level of security.

All of these points are completely correct and paint an accurate picture of the inherent issues with both technologies.

My intent with my earlier comment was to show how flatpaks and appimages were different from traditional package managers at a high level so I could ask what made nixpkgs different from something I felt and still kinda feel is a more accurate comparison which are traditional package managers like apt etc.

The big selling point to me now is that nixpkgs seem to work similarly to virtualenvs from Python which is cool.

So it sounds like nixpkgs is more akin to virtualenvs in Python rather than a traditional package manager. Is that an accurate statement?

If so, I’d recommend that be your selling point because that’s some powerful security.