211–220 of 267 posts
If you've installed and use Linux then 90% your interests are in IT / software / hardware design.
So you know concept of a bug. And it is a good chance you've produced and fixed those by your own too.
The best person to report a bug is a programmer really.
Yep we find a variant of this with our python open source data science users who normal businesses would hate: - Across all Python envs (Jupyter, streamlit/plotly, flask/Django, ...), they report way more bugs, and often from our free tiers, which sounds low ROI.. but our community caught all but ~2 significant bugs we fixed this year that our internal automated testing missed and would have otherwise gone to our Ent…
Earlier quoted context omitted.
I think the title was intentionally a little clickbaity but I'm not exactly bothered by it. Clickbaity is a negative when the bait-and-switch robs you of the pay-off. In this case, I think it was overall a more interesting story and so for me subverting my expectations was actually a pleasant experience.
OTOH, it could have a negative effect if people only read the title and not the actual content.
Earlier quoted context omitted.
>"we have all seen bug reports like: “it crashes for me after a few hours" Here is a gem from my collection of user "bug reports". The email with this exact words and nothing else - "something is wrong, what do I do?". I was biting my fingers trying not to reply with the first thing that came into my head.
"We are sorry to read that. Please clearly describe your problem to us so we can help you. Feel free to call us on this phone number: XXX-XXX-XXX" People don't always understand our perspective, we should guide them into doing the right thing and everybody will be happy. Save your generic answer so you don't waste your time doing so, but being pedagogical should be part of our work in my opinion.
What makes you think I do not do those things?
Earlier quoted context omitted.
In a similar vein, I think the biggest value-add that Arch has over other distros is that it turns out having the filter of "can follow well written instructions through mildly tricky commands well enough to result in a bootable system" results in a community with a base level of competence, care, and patience that puts it at least two standard deviations above the other distros and at least four (I know how small th…
> Why would anyone accept Amex and its higher fees? Because they bring you higher value customers, sometimes dramatically higher value. Why are Amex customers higher value? Is it because they're typically business cards rather than personal?
That's probably a part of it, but the real answer is because an Amex is a charge card, not a credit card, which means that whatever is spent on it MUST be paid off in full at the next billing cycle. The net effect of this, is that if your customers are shopping with an Amex, they're people who /have/ money, or in the case of business cards they are acting on behalf of an organization that has money. Without writing an expository essay, it seems to be simply true that those who are more affluent also have networks and can bring people by word of mouth if you meet their expectations.
Earlier quoted context omitted.
I think the title was intentionally a little clickbaity but I'm not exactly bothered by it. Clickbaity is a negative when the bait-and-switch robs you of the pay-off. In this case, I think it was overall a more interesting story and so for me subverting my expectations was actually a pleasant experience.
OTOH, it could have a negative effect if people only read the title and not the actual content.
Earlier quoted context omitted.
Which is why I've stopped reporting LibreOffice bugs. I have had literally hundreds of bugs filed, with test files and reproducibility instructions. Then they changed bug trackers - twice - and all that is lost. With KDE and Mozilla, I'm still seeing bugs fixed a decade after I stopped reporting them. So I might be inclined to file egregious bugs to those two projects, if I feel inclined at the moment to wait a decad…
> Then they changed bug trackers - twice - and all that is lost. When precisely did this happen?
Earlier quoted context omitted.
Or have proper analytics. If a user emails you and says "It crashes after a few hours" rather than feeling bad for them, you ask them what their steam/game id is and you look them up in the crash reporter system and see exactly what happens rather than relying on a few programmer consumers doing the work for you.
But not analytics that are too good, or certain people will write a lot of inflammatory articles about how your software is nothing but evil spyware. Seriously, though, having a robust and automatic crash reporting system very much helps track down bugs you're never going to get a good report on or be able to directly reproduce.
Earlier quoted context omitted.
> Why would anyone accept Amex and its higher fees? Because they bring you higher value customers, sometimes dramatically higher value. Why are Amex customers higher value? Is it because they're typically business cards rather than personal?
> Why are Amex customers higher value? Is it because they're typically business cards rather than personal? That's probably a part of it, but the real answer is because an Amex is a charge card, not a credit card, which means that whatever is spent on it MUST be paid off in full at the next billing cycle. The net effect of this, is that if your customers are shopping with an Amex, they're people who /have/ money, or…
The primary reason Amex customers are more valuable is because most Amex cards carry an annual fee, which only more affluent folks can afford.
Earlier quoted context omitted.
>Any way the main benefit of Arch is that it's close to stable upstream repose, instead of sometimes lacking not just month but even years behind wrt. the version of libraries they ship. There is a downside that most Arch users omit intentionally, when you get latest GNOME/App with the cool new bug fixes and cool new features you also get the new not cool bugs and the new redesign/feature removal. This can cause the…
I've been using Arch since ~8 years and at least for me updates breaking stuff is rare, and every time it happens there was a simple easy work around the problem (like downgrading for a day or two at which point the bug was fixed). Through without question a major reason why the (few) problems I did ran into haven't been a problem was due to my understanding of Linux. The is the misconception that Arch is bleeding ed…
I bet that a vanilla LTS where you only update for security reason is more stable and risk free.