There's a bit more to it than "allowing subdomain creation". You will need control over the DNS records, or ability arbitrarily change the page (essentially).
1,867 karma · joined March 12, 2013
There's a bit more to it than "allowing subdomain creation". You will need control over the DNS records, or ability arbitrarily change the page (essentially).
A little anecdotal story backing this up...
My wife started as a paraeducator (teacher's helper) at a school after graduating from high school. A few years later she started working at another school, helping homeless & migrant children. She eventually left that job to work with migrant/bilingual daycares. This process took 8 years.
She then pursued a degree in psychology. Why? Because her next advancement required the state to check a little box on her form that says: "Applicant has a B.S. in social studies or similar". Where did she go for the degree? The cheapest, online college she could find.
The degree didn't matter for 8 years. The place the degree came from didn't matter at all. The price of the degree mattered only to us. She would have gained nothing by pursuing the degree immediately, and racking up any sizable debt from this degree would've just been silly.
If you haven't given up in a month, you're cut out for it. Persistence and a willingness to constantly learn are more important than your ability to do mental gymnastics.
Conversely, adding lines of code but NOT adding functionality isn't worth a cent.
There was a different problem with the two-day rest break:
> Must include two periods from 1 a.m. to 5 a.m. home terminal time.
Because obviously the trucking industry shouldn't be working graveyard. That's the part that was suspended. It screws with scheduling. 1 a.m. to 5 a.m. is arbitrary.
http://www.fmcsa.dot.gov/regulations/hours-service/summary-h...
> discouraged the Federal Motor Carrier Safety Administration from investing in wireless technology designed to improve the monitoring of drivers and their vehicles;
Either this is VERY recent news or just misleading. This is happening as far as everyone can tell. The mandate for electronic logging devices in all vehicles should be coming down late September, with a deadline of October 2017.
http://www.ccjdigital.com/e-log-mandate-advances-fmcsa-sends...
http://www.overdriveonline.com/eld-mandate-poised-to-begin-t...
This 20-point checklist is only a guideline; it does not guarantee that a person is correctly classified. Most agencies and courts typically look to the totality of the circumstances and balance the factors to determine whether a worker is an employee.
The point I'm trying to make isn't that you should go ahead and put your SSN in to random websites, but you need to realize your SSN goes a lot of places. Within the last hour I happened to find my parents' names, signatures, DoB, address, and SSNs in public documents from a county website. Keep track of your credit and watch for identity theft. Knowing that you are careful won't help as much as you think. Who knows who will end up using Checkr?
I'm not saying the fear is unwarranted, but do you know where your employer is inputting your SSN and where they keep it? How safe do you think your personal data is?
I built an employment application 'web app' for a job not too long ago. It was terrible, and against all my objections, we ended up asking for the applicants SSN. It certainly wasn't secure by any stretch of the imagination, and I cringe a little every time I see an application come in. I'm sure this sort of thing happens daily.
Anyway, I went ahead and put my SSN in to Checkr. It came up with an address I've never lived at, next to 3 addresses I actually have lived at. Not sure what that's about.
Server Fault is a question and answer site for professional system and network administrators.
Contrast this with...
Stack Overflow is a question and answer site for professional and enthusiast programmers.
What happened to cartooning? Do you do it at all anymore? As much as you might love what you're doing, you can't have just one thing in your life.
I managed to burn myself out on programming/hacking at 15 years old. It had been my only obsession since I first got my hands on a computer. One day I realized I was sick of it. My eyes were always bloodshot. I wasn't sleeping. I had no friends. I didn't even go to school.
I did my best not to look at a computer screen for six years. I picked up a guitar and played obsessively. I explored new career paths when it came time for college. I almost went in to the medical field. I exhausted my options, and finally came back to tech.
Everything was new and amazing. I felt so inspired. I had never seen a SATA connector before. I had never played with virtualization. It was like living in the future. It pained me a little to know I'd missed so much development, but I caught up quickly.
Now I have two things in my life: tech and music. When feelings of failure, inadequacy, and burnout arise, I pick up my guitar and go do an open mic night. It's my ego's failover.
Go back to cartooning. Switch your obsession for a while. It's still okay to obsess, just do it over something else. Become confident in your skills and sell drawings on the street for $5; do anything to boost your ego a little. You'll come back to hacking. There's time.
Wouldn't a backplane be more analogous to a SATA card than a single connector? In which case, 40 drives will go down on failure.
Neat stuff though. Would be fun to build one.
Will your accounts department stump up for a fancy new handset just so you can listen to Eminem on your way to a business meeting?
At the time? Of course not! Today? Standard equipment.
Despite that, I'd be very leery about purchasing this, as Google doesn't have a reputation for stellar support, or even _reachable_ support.
The 'reality of the situation' is that you're no longer retaining any young talent in your company, because you're stuck writing COBOL. The Frankenstein-of-an intranet program you've stitched together is now too big and too complex to work with; only the guys who built it in the first place have the guts to stick their fingers in the code.
Sometime around 5 to 10 years ago, you stopped building software and started slapping a bunch of dirty hacks together to get things to 'just work'. The technical debt is insurmountable, and it's only getting worse. The software is 20 years old. What will happen in the next 10 years? Maybe then the company will be able to afford a rewrite...
Except now the technical debt has crept in to the workflow of your users. People are doing things that computers should be doing. Every process involves some hacky workaround to get your ancient system to play nice. You're printing on dot-matrix printers and scanning it back in. Other companies don't know how to hand you data. CSV files over FTP transfer? Maybe we can just email you the files every week so your mail server can gobble it up and hand it to your ancient application? Other companies are scaling. Your bottom line is hurting.
Now we're 30 years in, and the guys who built it in the first place are looking to retire. There's nobody you can 'pass the torch' because none of the new employees over the last decade have lasted more than two years; they all went on to play with silly 'kid' languages like 'Ruby' and that funny 'Cloud' fad. You'll have to find someone with talent, years of experience in your antique system, and yet isn't thinking about retirement within the next decade. Time to post a job opening for a COBOL ninja-rockstar!