[-] [email protected] 4 points 9 hours ago

This isn't a car

[-] [email protected] 9 points 2 days ago

So....your face or mine?

[-] [email protected] 141 points 3 days ago

I don't think that will work, but hopefully they raise income taxes so I at least take home a bit more cash each month.

[-] [email protected] 245 points 4 days ago

This is my headcanon when I see a simple but long lasting bug like this at a large company.

To you or I, it seems simple. Clearly things are not working as intended and the fix is trivial. Raise a bug in the tracking system if you really have to, then just fix it, right?

Here's the thing. That code was written completely according to the specification. The path there was clearly there in the requirements. So what? So...that means it's not a bug, it's a feature change. And if it's not a bug, that means we can't officially use our allocated (but always shrinking) bugfix time to work on it.

If we want to fix it, we need to put in a feature change request. That means we have to articulate the value to the business in changing this feature and explain why we think the original specification is wrong. We can't get confirmation from the spec author because they are no longer with the company. That means we have to prove that it was written incorrectly.

If...and that's a big if, we can articulate that there's business value in doing this and that the original specification was likely incorrect, then we get to the really fun part. Prioritisation.

You see, the team that built that feature doesn't exist anymore. Once the bulk of the features were done, they got disbanded and the engineers moved to other teams. Technically there should be a single team responsible for every feature so it gets maintained, but in practice it doesn't really work that way. The people on the official team that's responsible haven't touched any of that code. They're not too keen on starting either because they have their own priorities.

So after all that, the task sits in the backlog of that team, neglected. Eventually in some distanct sprint planning session it will be flagged as an old ticket. You, who raised it, would have left the company and nobody in the meeting has context about why the task was created. Isn't that miscategorised, shouldn't it be a bug? Why is it with our team, is it even worth doing? Then it will be pruned from the backlog. The sad task that was fought for so valiantly, only to die sadly in the cutting room floor of a backlog grooming session.

Then one day, the bug will annoy a newcomer so much, they'll just sneak the change in under another ticket and the bug will finally be fixed. Months before the product gets scrapped for a worse replacement. What are the specifications of the replacement software based on? That's right, the original specs of the old system to ensure backwards compatibility.

[-] [email protected] 55 points 5 days ago

Well, we each have our talents.

[-] [email protected] 12 points 5 days ago

Make sure to hold on tight with both cheeks

[-] [email protected] 22 points 5 days ago

The enemy is both strong and weak

1
submitted 1 month ago by [email protected] to c/[email protected]

Been out for a week or so but didn't see it posted. This is a great guide for mining in 4.1 for my fellow rock breakers, targeted at beginners but there is a lot of good info and it's broken up into chapters.

1
Citizencon 2954 Schedule (robertsspaceindustries.com)
submitted 7 months ago by [email protected] to c/[email protected]
[-] [email protected] 276 points 9 months ago* (last edited 9 months ago)

Step 1: offer sanctuary

Step 2: offer citizenship

Step 3: conscript

[-] [email protected] 257 points 10 months ago

It's time for Russia to concede territory and end the war for the sake of all Russians.

18
submitted 10 months ago* (last edited 10 months ago) by [email protected] to c/[email protected]

Introduction

Firstly, although the tone of this post may be somewhat critical I want to say that I do appreciate the thought behind creating the bot and the work that has gone into it. The idea of being more aware of media bias in the news we consume is a good one and I commend the folks who actively took a step to try and advance that cause. However, I believe that unfortunately the current solution might have the opposite effect.

Suggestion

My suggestion is to keep the factuality and trustworthiness ratings of the bot as while they are still somewhat problematic, they can at least be more objectively assessed and sourced. The bias rating, however, has two pretty major problems as far as I can see.

Reason One - Inconsistent Definitions

Left and right do not have consistent definitions to everyone, particularly in different regions. Something considered left in the US for example might be considered centre or right in other parts of the world. This means that people's read of the bias rating of the bot may be inaccurate.

Reason Two - Opaque and Contradictory Bias Analysis

Secondly and the major issue I have, is that the bias rating does not seem to have a consistent methodology and I have seen troubling inconsistencies in the justification given for certain ratings. That means we are potentially being misinformed and having the opposite than intended effect of trying to accurately account for potential bias in the sources of our news.

Example - BBC

The example that I looked into was the bias rating for the BBC, which the bot describes as centre left. However, if we look at the justification for this rating it seems contradictory, with most evidence pointing to it leaning right:

According to New Statesman's research, examining the impartiality of the BBC's reporting shows that they lean right certain areas, such as business, immigration, and religion...

...

When reporting general news, the BBC always sources its information and uses minimal loaded words in headlines...

Sounds like the BBC should be rated as centre right based on this analysis. However, the media bias folks go on to say this:

When it comes to reporting on the USA and, in particular, former President Donald Trump, there is a negative tone directed at Trump and his policies.

This point, referencing a single article which is debatably overly negative, seems to be sufficient justification for them to rate the whole source as left leaning.

If you check the reasoning for the rating, however, it mentions nothing about this anti Trump bias at all, instead stating:

Overall, we rate the BBC Left-Center biased based on story selection that slightly favors the left.

This assertion is not justified in any way in the analysis they have provided.

Conclusion

I understand that disagreeing with one particular rating isn't necessarily worthy of action in it's own right, but I think this example highlights a more fundamental problem with the rating system as a whole. If there is not a reasonable and consistent methodology followed, then the rating system itself is highly subject to individual biases. Therefore, I believe that by including this rating in all the news posts, we are lending credibility to an organisation which unfortunately does not seem to have earned it.

Thanks for taking the time to read my suggestion and I hope nobody takes this as an attack of any kind. This is a difficult problem and I appreciate any effort to solve it, I actually was feeling quite positive about the bot until I looked into how the ratings were actually done.

EDIT: Also, I hope this is the right community to provide this feedback. It seems the bot has blocked me so I'm not able to check the support link that it provides.

[-] [email protected] 261 points 10 months ago* (last edited 10 months ago)

Fuck the reactionaries, fuck this far-right, fuck all of those who would like to lock us into a war of all against all.

Uncensored for your reading pleasure. Seems pretty badass to me and brought a smile to my face.

19
submitted 10 months ago* (last edited 10 months ago) by [email protected] to c/[email protected]

Back in the day, you had to be willing to do it yourself.

[-] [email protected] 259 points 11 months ago

An employee asked me if he can WORK from HOME permanently. Here is what I told him... ...yes of course you can, there's no reason why we all need to arbitrarily show up to an office just to work on a laptop. Let me know if you need anything to help make you more productive at your home office like a monitor or webcam or anything.

[-] [email protected] 309 points 2 years ago

Firefox.

Just thought I'd get that one out of the way early.

16
submitted 2 years ago by [email protected] to c/[email protected]

I thought this was a nice 10 minute recap of what the replication layer stuff is, the plans we know about from way back and where we're at now.

view more: next ›

Aurenkin

0 post score
0 comment score
joined 2 years ago