@retoor Nah - you're right.

I wouldn't trust them w/ my data, especially when self-hosting.

@retoor Gotta love the good ol'

no munny from you == no support 4U.

So basically when you just want to try out the software, perhaps see some potential in it, but there is an issue, you can't say

'Fix it && I will purchase the license.'

because as a /* currently */ non-paying user you are ineligible for any support.

...or so is my understanding.

@BordedDev Having read the 1st sentence, a picture is being formed in my mind...

...an unflattering one.

@BordedDev Perfectly reasonable thing to do.

After all, you need to be awake for stuff.

/jk

...The wifey might've been thinking it was a genuine advice.

Either that or she's one of those people who think that there are things you can joke about && there are those that you shouldn't.

That probably explains why the link's been down for me for a few days, now.

Also, I wish I could be as honest in my communication w/ co-workers.

Got reprimanded for doing just that a number of times.

Apparently, honesty is unwanted.

They want 'Yes'-men.

Hell.

@Ragnar We're all for tools that help us do our tasks easier, but this holds absolutely no value for us, yeah?

Had to merriam-webster the thing over here.

Site: 'Your device sucks'.

Me: 'I still appreciate you, my trusty PC. I'll buy you more RAM to cheer you up.'

#5 'Potato power' looks like a winner to me.

But the manual is full of gems.

@jestdotty I guess it depends on the point of view.

I'd say that if a person closes a report, then they accept the current state of things.

If the report is marked as resolved w/ a resolution 'fixed', then it should be logical that the closing of such a report means the problem has indeed been fixed.

Digging through the comments isn't something done by default.

But again - it makes no sense to leave a comment saying it's a won't fix, but mark the resolution as fixed.

If he truly wanted to cover his ass, he should've bounced the report to a decision-maker from the get go, avoiding all the subsequent problems that followed ensued.

Hmm...

Sounds similarly to the well known fact that everyone in Germany had been on vacation between 1939-1945.

/jk

Source:

https://youtube.com/watch/...

@jestdotty No, !really.

Can't remember what the issue was about but it was fixable, although the pool of affected users might've been limited.

For whatever reason he didn't want to fix it, so left a comment stating that this wouldn't get fixed, but the report's status clearly contradicted that.

When !sticking to proper procedure, i.e. like he wanted to mark the report as fixed, it's a pain to find reports like that.

Also, let's say at a later time another person encounters this same issue.

They would search for it in the bug tracker && if they found the report closed w/ status 'fixed', any possible blame would be put on the one who closed it as such.

Anyway, there was much simpler option - he should've bounced the report to PM or someone else who deals w/ decisions, like his lead.

Let that person take the responsibility.

Eventually he did that, but !before he was presented w/ that option.

@Ragnar Mortar systems, huh?

Come, weigh in on the topic, will you?

@retoor Yup. We have such system.

Just many stupid testers.

I've also seen many people fail miserably working w/ simple workflows, though.

At previous job, I had this fight in a report w/ one of the programmers, who chose to do this stupid thing:

P: * Adds comment along the lines of 'Won't fix.' *

P: * Marks the report as 'Resolved' w/ Resolution 'Fixed' *

Me: * Reopen the issue adding comment '!Fixed' *.

Reason? He was unwilling to mark something as 'Won't fix' because he was afraid of getting blamed for it.

Fuck logic.

@retoor I would argue that bug reports are a form of communication between at least two parties.

0. There's a problem so a bug report gets created.

1. Person on the other end checks the report, makes an assessment:

- legit bug,

- !a bug - as designed,

- no time / too trivial - won't fix.

&& takes an action:

- report gets closed,

- or assigned.

2. If legit bug, the assignee fixes the problem, marks issue as resolved.

3. Report gets verified by the tester:

- if fixed - report gets closed,

- else - reopen, goto 2.

If there's no communication, then that's a problem.

If a report looks like no one's worked on it, then blindly rechecking it is a waste of time.

In rare situations - yes, the issue might be fixed, but it is almost always the case that somebody had been working on the affected area or an area adjacent to it.

If there is no info akin to 'we're working on x, so recheck everything related to the feature' we're once again dealing w/ lack of communication.

@jestdotty Makes sense.

@Grumm Both.

@Ragnar You're !interested in any limos or other crap like that, correct?

@Ragnar I know you're always looking for more lands && wealth, but I'm sure you're good on the amount of accounts you own, yeah?

No. If I haven't done it, I'm !becoming someone else's scapegoat.

Actually had a situation touching on this very recently.

A person had fucked up - I called out the responsible one saying what he did && how he actually should've handled it.

What is interesting is how often people above you just shrug off their responsibility when they fuck up, though.

Source:

https://monkeyuser.com/2018/...

@Ragnar You probably speak Vietnamese, right?

Can you decipher this?

All this time travel talk reminded me of the movie 'The One'.

...will have to re-watch it, now.

@Ragnar Come, take a look at this.

For me, it was having a good friend in need.

He was making a game && needed some help w/ it, so he reached out to me.

@Ragnar Lucky day. Time to test your improvements!

@retoor Poor thing. Your life-like camel is missing a portion of its legs.

Or so it would appear from where I sit.

...will be back in the evening, one my work is ended.

Just in case:

Console output for newer *.py:

Just in case:

Console output for older *.py:

@retoor Have been having weird results.

/* What else is new? */

The up-to-date versions of the

- plot.py

- merge.py

somehow fail to produce the

- graphs.html

but manage to produce a meaningful graph of keyboard events

- per day

...the older ones produce empty graphs, but do generate the *.html.