2,444 karma · joined November 30, 2010
I totally understand the limits that had to be set on the low bar for quality content. In those early days though, it seemed to me that when people asked questions about managing mobile phones for instance, because it was only newly related to being a sys admin, they'd get closed as not related.
Granted, in those early days, there weren't as many process "rules" in place to guide users to ask better questions and perhaps that's still so. However, a quick perusal of the site indicate this has gotten better and more friendly towards new people.
There was also a general lack of compassion on the part of many, many users. I get that the sites strive to be full of "high quality" content, but there were a lot of legitimate questions asked, in broken English, that got closed immediately, or got closed because it seemed like it as academic exercise they were asking. IT has a reputation for lacking in people skills (deservedly so) and in SO's and SF's early days, that certainly stood out as a major turnoff of the sites. Admittedly, I have no idea if it's gotten any better.
That will teach me to make comments before the caffeine has kicked in.
You could potentially have to hand your personal device over to lawyers where they can then put your personal device through an e-discovery process should your employer be sued .
People need to really think hard before they relinquish that kind of control of a device that you own.
In either situation, the corp has the ability to remotely wipe the device and enforce other policies on said device.
This should be abundantly clear to anyone who works in Tech.
I mean I used to have to commute through downtown Portland, Oregon at rush hour. Just being able to leave that out of EVERY day has tremendously improved my quality of life.
I'm trying to figure out if you've actually worked remotely or not. It does take a much more concerted effort on everyone's part to be more inclusive of remote workers, especially if only a handful of devs are remote and the rest share an office.
Meetings aren't usually a problem. We primarily rely on Skype for Business and all meetings are generally held online. We've even managed to move scheduled meetings (which I loathe) into Microsoft Teams channels. The written words manage to keep everyone on the same page, much better than just hearing it.
Microsoft Teams and Slack facilitates the sharing of cubicle conversations and informal ideas but it takes effort to get everyone onboard with using these as their primary ways of sharing convos.
I mean, I don't get interrupted very often. I can be as out of site/out of mind as I want and need. And I'm way more productive working from home, than I am where I can be interrupted constantly. I don't know about you, but it usually takes me about two hours to recover from an interruption to get back to where I was. Not always, but usually.
All of the above is pertinent to being a mixed bag of remote and office sharers. I would imagine that an all remote team, would have an even easier time with communications and inclusivity.
The other thing that gets me, is not listing what the expected pay is upfront (and whether or not it's remote) on the job posting. We all work for pay and we all have a pretty good idea of what income it takes to live in your current (and future) circumstances. If your pay is nowhere near that expected range, why should I waste your time and why should you waste my time?
I got hit up on StackOverflow to apply for a company. After looking at their job listing, it said (limited remote with approval), making it sound like you had to negotiate for remote work. This is what I responded with, "I currently work remotely and have no intentions on moving. I have a proven track history of performance and productivity working remotely for over 7 years and it's not something I'm willing to give up or negotiate. So I can save us a lot of time by being upfront with you about that."
I didn't apply and didn't receive a response...
But on a serious note, I really don't understand why they couldn't have written you back and asked if you could make it compile on Linux and send it back.
Honestly it's stuff like this, that has me contemplating giving up this career path because there's just no more room for people in their 50s with 25 years of experience in information technology, who aren't willing to sleep at the office, drink your "insert trendy microbrew here" on tap, and suffer through a ludicrous ask like "we want you to work for three days for absolutely nothing to see if you're a good fit".
From one of the OP's comments, "Oracle support told him, step by step, to encrypt the database, which happened ages ago and is the root of all of this."
That wallet is the responsibility of whomever created it. Just because it's empty now, doesn't mean it's always been empty. In addition to that, what if the person who initially encrypted everything with TDE, used a local only wallet? This would explain why the ewallet.p12 file is empty. Oracle recommends that you store your master key in the ewallet.p12 file and not the cwallet.sso file, which is the auto-open file, but only on the workstation it was created on.
There could have been multiple failures here with multiple parties and not just Oracle.
I mean laughing and experiencing schadenfreude over someone planting a hidden and previously unknown microphone in ones home, is just weird man.
It's one thing to be able to "answer questions". It's an entirely other thing to have access rights to actually solve a problem and the authority to do so.
The only issue (and it's a very slight one at that) is the weight of this pillow. I think the shipment said it was just shy of 10lbs. The best way I can think of to describe this pillow is that it's like a sack full of ass fat.
The lack of choice was just irritating. There are only so many ways you can use garlic whistles.