Funny coincidence. Around 2000, I worked for a company that coined the term "Norway problem" for a different software problem.
Their product used an MVCC database (I think ObjectStore). One of their customers in Norway had a problem where updates to the database seemed to not show up. IIRC the problem was a bug in this company's software that caused MVCC to show an older version of the database content than expected.
> So the only means to have a situation where you don't risk bigco for a single department is not making it a department. Make it a Ltd. in a holding or something.
I was thinking that as well. Can anyone explain why this isn't common practice?
> I feel like this article gave up way too fast on gdb's tui mode, especially given that gdb works and tui didn't crash like half the debuggers in the list, other than "the command tui disable crashes gdb." which I can't reproduce.
I've had the same conundrum for a various categories of development tools on Linux:
For a particular category (e.g., remote debugging, Vim C++ autocomplete system, etc.), an initial search uncovers 3-10 software combinations that people have documented as working.
And when I work through the list, trying to find one that works for me, I often hit problem after problem. It's hard to know if (a) that particular recipe is no longer workable, (b) there's something about my particular setup that will forever damn that approach, or (c) I just need to keep working through the problems until I finally get things working.
So it's hard to know how long to bang away at a particular recipe to determine if it's (a), (b), or (c).
The unfortunate result is I often run out of time for the investigation, and fall back to using Vim + gdb + ctags for developing on remote servers.
Mostly I'm just surprised that Visual Studio in 1999 gave me a better debugging experience than I've been able to cobble together on Linux in 2020.
> Is banning discussion of religion in the workplace a political/religious stance?
(Please forgive any flawed logic below - I assure you it's an oversight. I'm posting this in good faith.)
I'd say yes, but basically in the same way Coinbase's band on political speech in the office is a stance.
Consider religious people whose theology holds that they should attempt to convert everybody in their circles, even their professional circles.
It seems to me that banning that is tantamount to saying either (a) their theology is wrong, or (b) it's not wrong but the employer is resisting it regardless, or (c) the business has no place for employees holding those beliefs.
Another possibility that occurs to me is that some employees are very conscientious, but have value systems that are looked down upon in mainstream Silicon Valley culture.
I could imagine such employees being more willing to stay with Coinbase when that potential source of strife is removed.
Their product used an MVCC database (I think ObjectStore). One of their customers in Norway had a problem where updates to the database seemed to not show up. IIRC the problem was a bug in this company's software that caused MVCC to show an older version of the database content than expected.