He is. I'm trying to do things that will reduce the amount of time it takes to manually review test results. Since that's 90% of his job, his repeated reaction is that he'll get laid off. Keep talking like that, sure. Or maybe you could realize that reviewing test results is mostly a waste of a human and that there's better usage for a salaried employee.Sounds like that dude is just low energy as fuck.
Well, the other company I was going to work for in Rhode Island... we acquired.Every time you complain about your job I just can't imagine what the fuck you're even doing. There's negative unemployment in several sectors of IT.
Yeah, I have done shit that needs to be done, of course. But it's always comped in some way. Which, you know, that's the game.I've only ever stayed late/come in night/weekends when mission critical shit has gone down. I was compensated/comped hours though. I feel like it's always devs/programmers that get stuck in this work for free (oh it's crunch time lol) scam. Weird.
Less stress, more productivity: working fewer hours is good for you and your boss | Hacker News
^Discussion related
My last job was flexible. Their hours were "get your work done" and the work from home policy was "get your work done" so I worked from home a lot, and often I did work shorter weeks. I always felt bad though.Eh, I like working more of a "flex" type schedule. I send emails on Friday night/Saturdays/Sundays/Weekday-nights because I will take time during the day for non-work activities.
I had a previous supervisor who said it best: If you feel like you're fucking the company with time you take, you probably are.
On the other hand, the company never feels bad about trying to work me to the bone, so I'm going to do ~45 hours/week at most (on average, for the year). Will there be 80 hour weeks, yes; will there be 30 hour weeks, for sure.
Information Security Architect (lol)What made you leave that job, then? And those of you that work 40 hour weeks (doing overtime as needed), what do you do? What would be a good starting point for someone looking to start a job like that? I literally have zero background. No college. Blank slate, and all that.
Information Security Architect (lol)
I have a BA (stress the A, there is no S) in CompSci, and I learned by myself or on the job (Ok Google, how do I do X). I was doing Linux work before getting a job, but learned everything related to Windows through my job(s).
I started doing BSD sys-admin and desktop support out of college for a small company for a few years, then moved to a large enterprise doing desktop support, moved to linux system engineering, moved to incident and forensics, move to infrastructure security, then moved to my current job.
I took calc twice in college, once as an AM with a teacher who was terrible (got a solid D+), then again and got a B+. I still barely understand it. It's not useful for Computer Science (at least the shit I do).Never excelled at College the first attempt many, many years ago as I learned everything on the job. Eventually ended getting a couple of certs and went back to school (Bus Adm AS). Started back up within the last couple of years for the IS BS, but just real tired of hitting the math wall (not even made it to Calc I). I just don't get it.
Career-wise, is just any stupid B.A. helpful; provided you keep learning/acquiring certs?
Or do you really just have to buckle down and trudge through Calculus?