The Lounge is rated Safe For Work. If you're about to post something inappropriate for a shared office environment, then don't post it. No ads, no abuse, and no programming questions. Trolling, (political, climate, religious or whatever) will result in your account being removed.
I have mentioned in the past I have had Jira landed on me, the general response from the learned crowd was 'Kill it, Kill it with Fire'. I didn't really follow that view as I used to have manage tests and documentation using a combo of Access, Excel & Word (fun times), Jira appeared to have it all in one place. However one thing struck me as weird is the 'prefered' way to get to tests is using the menu's Project -> Test -> Plan Test Cycle and then select from the appropriate tests down the side. Fine a little illogical but I can deal with it. This works if you have the 'frame' open, also if you execute a ticket with the Execute button you can execute a test outside of a test cycle, which will cause my Boss to meltdown...
It seems like it has been added to by different people, at different time, to do different things.
Now it can do various things some of which it was never meant to and it seems to be touted by people for various uses it can be be put to, like a Swiss Army Pen Knife, not the ideal tool but better than nothing.
Jira is a tool which is powerful and extensible.
That said, like any tool, it all depends on how you integrate it into your company, and how good the configured workflows match the real-life processes. If they do not match, as with any tool, you'll end up butthurt and crying - But that's not Jiras fault, but someone higherup ind the command chain not understanding how tools are supposed to help employees get work done effective and efficient rather than self-inflating a boss' ego about doing things the way he wants them done.
I only have a signature in order to let @DalekDave follow my posts.
I've ranted a bit before about Microsoft's pathetic excuse for an operating system. Window's only achievement is through marketing and "it's good enough." My customers do not and will not tolerate their machines crashing for inexplicable reasons... my assessment of Windows 10 on a good day is marginal, on an average day pathetic, and on a bad day - criminal. I'm being generous. For 25 years I've put up with "it must be a driver" bullchips, and as a professional by now MS should have fixed their exposure to this issue - practice safe drivers. Anyway, I rant and I want peace on earth and free healthcare for all....
Google "BSOD diagnosis" and you will get a pant load of sites that are nothing more than shills for "magic" s/w that does absolutely nothing. The next major category is anything beginning with "answers.microsoft... " I actually can hope that most of the posts are AI driven, but I'm not sure.
So for those of you who get into the muck to solve or at least accurately identify Windows 10 system issues - what are your preferred sites? What sites eat raw bits and crap ammo when they are done? tomshardware can have some traction from time to time.... crap, I feel an article forming.
There is nothing "free" in life. If you believe this, you believe in theft.
At any rate I was pleasantly surprised when they said the .NET Core 3 rc2 installer (or rc3? or some other number!) and forward will uninstall previous (pre-release) versions, when installed.
And I checked it, it was true!
I'd like to bounce some code-in-the-grammar ideas off of you at some point. I have an idea that may allow for associated code without it having to be in the grammar, using attributes and a "codebehind" class but i'd like a 2nd opinion. Just whenever.
When I was growin' up, I was the smartest kid I knew. Maybe that was just because I didn't know that many kids. All I know is now I feel the opposite.
Unless dealing with faulty hardware or bad drivers, it's literally been years I've seen a BSOD that the OS could be blamed for. Dare I say, these days I don't see Windows outright crashing/freezing any more frequently than some Linux distributions...
+1 to the no BSOD club here. I haven't had any at all in Win10, and I code in VS2019 Pro (Knocking on some serious wood here). 2 years ago, I did have a workstation class motherboard die on me. Likely was around then was the last time I've seen a BSOD in Win7. Drivers can cause this as well. But I tend to buy quality hardware that seldom suffer those issues.
Two of my users regularly still get BSODs.
I do know exactly why though for these two machines.
Whenever M$ update their handling of graphic devices, the vendor provided drivers for the graphic devices on these two (out of 20 odd physical machines) shut down and bang BSOD.
Of course, what we see on the screen gives absolutely no clue that this is the reason, just learnt the hard way.
Management asked me if we could invoice M$ for the several hundred hours of research I had to do to find the issue and document it sufficiently that someone else can recover these machines if I am not on-site. I suggested that this would only cause amusement in the the house of small soft things.