|
mattfl posted:The leaks are coming from multiple sites where you may have used your gmail address to sign up, not necessarily from gmail itself. Appears to be correct. I did a Ctrl+F for "+" and saw quite a few "xtube," "eharmony," and spammy/free cash sites.
|
#
¿
Sep 11, 2014 01:18
|
|
|
|
| # ¿ May 29, 2024 23:40 |
|
|
Inspector_666 posted:I tried using it, but apparently I have to guess correctly 100 times in a row to see my own estimate, which seems dumb since if I knew what a title was worth I wouldn't be on the site to begin with. People use the site to see their own salary. If you don't want to spend 20 minutes rating other people, you should try to guess what other people have guessed as those are worth more. The site's accuracy is skewed thanks to game theory. Here's 100 points in 2 minutes: Helpdesk 55k Non-senior sysadmin/network engineer 70k Senior sysadmin/network engineer 85k Of course, everyone else is doing this too, so you can save yourself the trouble of signing up and just apply the above numbers to your own position. Edit: Apparently a CCNA is worth almost six figures these days. Thanks Salary Fairy! Contingency fucked around with this message at 02:30 on Sep 27, 2014 |
|
#
¿
Sep 27, 2014 02:26
|
|
|
joe944 posted:Due to conflict at my employer, it looks like I'm going to officially be the most senior member of my very short-staffed team. I'm not willing to say exactly what happened yet as the final outcome has not been reached, but let's just say that "ninja moves" and police were involved. My company was bought out, and our senior admin fled immediately. I took over the network side of operations; they didn't offer me his position, and to be honest, I'd much rather have a second voice to help fight the good fight. What happened? Management decided they were doing just fine without a senior guy and eliminated the position. Now I'm stuck with double the work at non-senior pay, and our UNIX guy has been on call since 2013. Don't be us. I would get management to confirm that there will be an opening for his position, and definitely let them know that you're interested in filling it. If you are passed over, that's a vote of no confidence, and looking elsewhere is a much more reasonable alternative to waiting for things to improve.
|
|
#
¿
Nov 1, 2014 21:39
|
|
|
joe944 posted:We aren't short staffed to the point of only being 1 or 2 people, but there are many issues that either myself or one of a short list of developers has to step in and troubleshoot/fix. I really can't complain much because things are running quite smoothly, I just don't have the manpower to accomplish the big project work that I want done in a timely manner. For over a year now I've been migrating chunks of our infrastructure that hadn't been touched in 5-7 years over to our puppet environment, so I have quite a few things that I'd like to see completed for reputation's sake and pride. Definitely going to be keeping my eyes open for better opportunities though. There's Tier I work, and there's senior work. I've been doing for a year what you're planning to do (even have a list of all the things I set out to fix), and quickly found that not being in a senior role means I can't grow as much because the bulk of my day is still spent doing Tier I/day-to-day tasks. Don't be me. It sounds like your options are 1) senior work + senior pay, 2) senior work without the pay, 3) the status quo, 4) worse than the status quo. If you have the option to push for #1, even something like a team lead and not a full manager, I'd do it. I settled with #2, and pending a frank discussion with management at the upcoming employee reviews, it may take leaving to improve the situation. Contingency fucked around with this message at 22:48 on Nov 1, 2014 |
|
#
¿
Nov 1, 2014 22:37
|
|
|
Tab8715 posted:On the same subject... First one to HR wins. You were physically intimidated by Bob, and although you don't want to make a big deal of it, you'd like it to be documented so it doesn't continue to be a problem.
|
|
#
¿
Nov 1, 2014 22:47
|
|
|
Tab8715 posted:If I go to HR, it's my word against his - right? Right. It's also about control of the narrative. If there will be a discussion, it would be in your favor to have it be why he felt it necessary to bring in physicality more so than it would be about you participating in a heated discussion. You casting it as a problem that you're not demanding disciplinary action over lowers the odds anything will come of it, and thus require less investigation into both sides of the story.
|
|
#
¿
Nov 1, 2014 23:01
|
|
|
I got burned once because I didn't bring wallet cards to an interview, but that was probably a special case of stupid.
|
|
#
¿
Nov 30, 2014 22:57
|
|
|
Sickening posted:How could that burn you? Did the interviewer not want to take the few moments it would take to look yours up? The way the interview went was: "You said you were certified. Did you bring your cards?" "No, but I sent your company a link to my MCP transcript earlier." "Cards are important. You should have brought them." Misogynist posted:That work environment does sound like a special kind of stupid. Car dealership.
|
|
#
¿
Dec 1, 2014 00:59
|
|
|
Tab8715 posted:I don't know if there's a way to share it directly but search for SA IT Mentoring Group. https://www.linkedin.com/groups?home=&gid=6535747
|
|
#
¿
Dec 1, 2014 06:44
|
|
|
Raise negotiations: So my company got bought out a year and half ago. I stuck around and took over for our outgoing senior admin, who wasn't replaced. Employee reviews were finally conducted, and I got a run of the mill 3% increase. I tell my boss that I'm doing the job of two people right now, and that senior work warrants senior pay, so I ask for a 30% raise. He's going to get back to me next week. From what I've seen, the new company has trouble acquiring talent, and I suspect the reason is because they're not willing to pay for it. I can make a strong case for a pay adjustment, but 30% is not likely to be rubber stamped. Has anyone had success doing more than accepting the counteroffer while sending out resumes?
|
|
#
¿
Dec 13, 2014 08:03
|
|
|
Tab8715 posted:Sounds like you want to stay at your current gig but considering they're only offering 3% I'd bounce. Maybe they'll cough it up when you put in your notice maybe not. To their credit, 3% was the annual increase. The funding for an adjustment for responsibilities would had to have come from a separate source. Misogynist posted:30% is a really tall order unless you were already at the wrong payscale before taking over for your senior admin. I know it is. The way I see it, if you need an average 45 hours of network engineer a week with occasional 50-55 hour stints, it's tough to justify hiring 2x40 hours worth. If they need more than 40 from me, it shouldn't be unreasonable to expect compensation to reflect it. Dark Helmut posted:Devil's advocate question: Is your skill set strong enough to be earning 30% more on the open market in your town? If so, you can certainly make a move or use that as leverage. If not, then maybe look at settling for a smaller raise while you use this job as an opportunity to really solidify your standing as that senior admin, and then make your move when your stock value is truly improved. Just my 2 cents... It isn't, but it's not terribly above market wage. The company is a carousel. Some people hopped off immediately, some were flung off, and others are clinging on for dear life. Plan B is exactly what you suggest--picking the appropriate time to step off the carousel. Odds are my next employer is going to ask two questions: what is your job title, and what is your current salary? It would certainly be worthwhile to stick around for an improvement on either front, but you also don't want to wait too long before finally cutting your losses. I could wait another six months and make a stronger case for 30%, but if all they were going to do all along is 15%, I'd have been better off rushing the next level cert and hightailing it.
|
|
#
¿
Dec 14, 2014 08:22
|
|
|
flosofl posted:You realize there's nothing stopping you from throwing out any number you want, correct? I don't think that's how it works. A company is allowed to say anything provided it is true or an honest opinion. Matters of opinion could wind up in court on the basis that it is untrue, so many companies have a policy of limiting what is said about an employee. Many companies is not the same as all companies. Lying to an employer doesn't seem to be worth the risk. evol262 posted:The way your employer sees it, you're already in an exempt position with a formal job description which says so, with appropriate compensation. I'm pretty sure "salary-exempt" is not code for "we own your life." Compensation is an agreement between the employer and employee. The amount agreed upon was for 40 hours and occasional overtime. Since staff were cut, overtime is now frequent. If the company now asks for more, it's only fair that I ask for more as well. If they want to own me, I expect them to pay me a fair rate for it. I may have to, for 30%. I'd at least give them a chance to keep me, as once I receive an offer letter, my policy is not to accept counter offers. We're past what better time management can fix. I may get 50 hours of work in a week, and I pick the 40 that get done that week. Due to lackluster project management, my availability is rarely considered in planning. Frequently that 40 becomes 45 to avoid a highly visible failure, and if something unrelated breaks (I handle both new service and support of existing clients), it's a 50 hour week. Losing a customer to teach another department how to plan better is a career limiting event. When you had a three person team, odds are someone was in a lull and could absorb the surge. With only one person, the only outlet is overtime.
|
|
#
¿
Dec 14, 2014 21:27
|
|
|
Contingency posted:Raise negotiations Asked for 30%. Got 20% and a modest title adjustment. Not quite what I asked for, but it's market wages. The plan now is to knock out some certs and ask about that title increase in a year.
|
|
#
¿
Jan 6, 2015 06:24
|
|
|
evol262 posted:Title doesn't matter unless your company ties pay scales to it Titles certainly do matter--if you are applying for a III position, it's less of an uphill battle to be a II/III applying than a I. It's also important to keep pace with others in your company, lest your overinflated peer over in ABC Division one day becomes the underqualified boss in yours.
|
|
#
¿
Jan 6, 2015 15:42
|
|
|
MJP posted:We just got the word that our main office - around 40 people - will be moving a few floors down. The space is brand new, around 15,000 square feet. We're going to have brand new everything built up - we're wiring for CAT6 (currently we're only running 100mbps just fine, but the option wouldn't hurt), doing a custom conference room buildout with better automation, etc. If the goal is future-proofing, don't do Cat6, do Cat6a--Cat6 won't do the full distance of 10GBaseT. If 10Gbps will never happen, Cat5e is just as good and may save on labor expenses as it is easier to terminate. Rack management: Don't be like my company and add switches piecemeal. 100BaseT is fine for many users, but what happens is many is not the same as all. Billy Bob wants Gigabit, and Timmy needs PoE. Your nice clean patch panels won't stay that way as you are constantly repatching users into switches with different capabilities. Get some gigabit+PoE 2960-Xs or equivalent, patch everything once, and label/dress/bundle everything. Threaten bodily harm to anyone who favors zipties over velcro, or suggests a patch panel is not necessary.
|
|
#
¿
Jan 17, 2015 02:03
|
|
|
Many phones have a switch port for a PC. If you have two drops per cube, loops are not uncommon as people plug both cables into their phone.
|
|
#
¿
Mar 1, 2015 00:33
|
|
|
The fast food places I've worked at, inspections are typically handled by an "all hands on deck" approach. Everyone gets more hours (and some regulars a lot more hours) to get everything ready. If something is overlooked, it's just a ding on the final score. If inspections occur frequently enough (not just health, but also district manager walkthroughs), things don't languish enough to warrant a health department shutdown. At many levels, IT involves project work. There are plenty of other occupations that don't do that. Show up, clock your eight, and go home. As a "benefit" of that increased responsibility, IT workers tend to be classified as FLSA-exempt, so you don't qualify for overtime pay.
|
|
#
¿
Mar 15, 2015 17:53
|
|
|
I don't know if this approach is universal, but my department was given a number like 4% in raises across the board. Assuming you have $1 million in salaries to start with, that's $40k to dole out. The general plan is to give everyone a 2.5% increase as a baseline, and high performers and individuals that started off on the wrong end of the payscale can be adjusted upwards. There's a bit of spread between earners, so that 1.5% of wiggle room can result in a not-so-minor increase for entry-level employees. The concern though is that using annual increases for merit raises hurts the rest of your department--every extra dollar that Billy Bob gets comes at the expense of everyone else. It's difficult for a manager to justify funding a significant raise from that pool.
|
|
#
¿
Mar 20, 2015 06:01
|
|
|
siggy2021 posted:Tonight is our big Internet cut over from our poo poo ISP and a 50 Meg line to a 100 and from a VPN between sites to an MPLS network. Is the DHCP server at HQ? If not, you may have IP helper set up and pointing to the old WAN IP or device.
|
|
#
¿
Jul 18, 2015 02:58
|
|
|
Methanar posted:I finally got to upgrade my asa5505 from 8.2 to 8.3 ( the major nat overhaul). If they can authenticate successfully, I'd check split-tunneling and a NoNAT statement for the RAVPN client pool.
|
|
#
¿
Jul 31, 2015 06:06
|
|
|
Docjowles posted:Haha you managed to hit my two big sysadmin pet peeves. Especially DNS. Most of the time you're hired into an environment where someone else set up DNS ages ago and it Just Works so you can get by without really knowing much about it. But if something related to DNS breaks, suddenly absolutely everything is down, and god help you if you don't know how to fix it. My boss likes to ask DNS questions as part of his phone screens. Nothing scary, I'm talking like "name all of the types of DNS records you can think of off the top of your head and what they're used for" or "describe in as much depth as you can the process that happens when you perform a DNS lookup for lolwut.com" or "what is the difference between a forward and reverse lookup?". The number of Senior Sysadmin candidates who respond with "uhhhh well you give it a name and it like, returns an IP, or something... I think there are like, A records? uh huh huh huh There's a saying I read, possibly here, that "everyone is a network engineer until something breaks." I believe it.
|
|
#
¿
Sep 10, 2015 03:04
|
|
" is pretty horrifying.
|
MC Fruit Stripe posted:Only two answers? Cowards, the lot of you. Once upon a time, I was in the Army. I was stoplossed, bitter about it, and almost out the door, so I was given a couple flunkies with the same attitude. We were an extremely productive team, mainly because I was competent and did the heavy lifting. If I needed help, I asked them, but if I was the best person to do it, I did it. When performance reviews were conducted, I was chastised for being a ineffective leader. At the time, I thought it was BS because the mission is what mattered, and in that respect I was a top performer. Fast forward 8 years, I'm a junior engineer. I have almost no access to our infrastructure. Company was bought out, my manager flees, the company cuts the senior role, and I'm now filling my manager's shoes. Overnight I have double the workload, and I'm starting with no institutional knowledge because documentation and setting up limited access accounts was too much of a hassle for my manager. We survived, but the company would have been better off if I had been more involved in operations. The messes left when he departed? I could have been entrusted with knocking that stuff out long before he left. As much as I like the guy, I believe he squandered his talent while at our company. He largely fell into the same trap I did. I don't believe your job is to train your replacement, but I look at it this way: in January, your company has an employee worth 40k. With the right tasks and responsibilities, that employee could be grown into a 50k employee by December. A good manager could see these opportunities and take advantage of them. Short term loss, long term gain.
|
|
#
¿
Oct 16, 2015 02:59
|
|
|
MrMoo posted:No shock sensors on the box? I've never seen racks moved without them: The shadier carriers will just rip off the sensors that trip and hope you don't notice.
|
|
#
¿
Nov 18, 2015 02:49
|
|
|
KS posted:It's totally HR. Can anyone say the new hire and termination handoff is as good as it could be in your head? Correct. Marketing begged and pleaded for a NAS that they never used, Sales contacted my boss's boss to explain why his IT issue was more important than anything else I have going on, but HR, week after week, could not understand that if we insist on a week lead time for new hires, we're not budging. "But it makes the company look bad when I hire people on Thursday and they don't have a computer on Monday!"
|
|
#
¿
Dec 15, 2015 05:08
|
|
|
MCSA requirement could be a workplace conflict avoidance strategy. Having a metric or checkbox in place to justify the promotion heads off discussions like "why did Billy Bob get promoted to tier 2 in a month while I didn't?" as "he's not as awful as you" tends to rub people the wrong way.
|
|
#
¿
Dec 23, 2015 16:24
|
|
|
DigitalMocking posted:I don't like it. I've never liked it. I remember sitting in a really pretty auditorium in late '98 or early '99 in the Silicon Valley while a smarmy team of Cisco and IBM sales guys told us all how iSCSI was going to revolutionize the world, super cheap, "just as fast" as FC storage, far superior to SAN fabrics in every way. FEH. What followed was 4 years of complete poo poo as people rushed into it without understanding the real impact on the network, the performance was balls awful, switches didn't have the horsepower to handle it, the first generation IBM iSCSI network cards would loving melt themselves handling the traffic. Lets not even talk about how badly most switches handled the transition to Jumbo Frame support specifically for iSCSI. Still terrible. Our customers requesting iSCSI are the ones least capable of maintaining a stable network, and storage kinda needs to be reliable.
|
|
#
¿
Mar 14, 2016 14:22
|
|
|
Our other division recommended everyone's personal cellphone be on the wireless network with direct access to company assets, to protect the O365 data on the phones. Blocking Hulu/Netflix on that network and leaving it running on the "visitor" network lets the free market sort it out.
|
|
#
¿
Mar 29, 2016 14:17
|
|
|
MC Fruit Stripe posted:You're being facetious, but I've never been nervous at work, I don't think. Someone should regale us with a story about a time that you thought, terrified, to yourself, "well that's it, I'm getting fired". As long as you're okay now and we can look back and laugh. If you're posting from the library, please don't. Here's a wall of text: Iraq, 2003. I noticed a corrupt backup, and then proceeded to overwrite system files with the corrupt backup instead of the other way around (I still blame the awful GUI for that one). Knocked out military phone/data communications for our site and supporting sites, so pretty much all coalition forces operating in the city. Since I just put our platoon out of work, I was volunteered for convoy duty to obtain a replacement drive. Drive up there was uneventful, but in the meantime, a prominent Shiite cleric was assassinated. You know those Walter Mitty types that swear they'd kick some hijacker rear end if it was them on the plane? Well, they're in Iraq too. The town is emptied out as everyone's taken to the streets in a show of force. AKs unslung, sandbags emplacements with RPKs on roofs, meanwhile we're just nudging our trucks through the crowds to get back to camp. Again, this is 2003, so our humvees have canvas for doors and covering instead of armor. Kids start showing off, first by trying to put their finger in the barrel of our rifles, then once they realized we weren't going to start a massacre, the older ones get emboldened and start reaching inside the humvee. I'm trying to play this off the best I can, grabbing their hands and shaking them while pushing them out, while the driver is frantically shouting to do something to get them to stop. Well, when you're surrounded by a mob of angry people, and some of them can empty a drum magazine into your canvas roof, turns out there's not much you can do that doesn't play out like Black Hawk Down. So I spent a few agonizing hours contemplating the notion that if anyone dies, it's on me. We all made it back though. On the bright side, I did see a kid in the crowd, no more than 10, wearing a "legalize weed" tshirt, complete with smiling anthropomorphic pot leaf. How he got that shirt was later a topic of much speculation. 0/10, would not try to replace backups again.
|
|
#
¿
Apr 20, 2016 04:07
|
|
|
psydude posted:Where's the poo poo? Every good Army story involves poo poo in some way, shape, or form. Sorry, no poo poo, only Shiites.
|
|
#
¿
Apr 20, 2016 04:50
|
|
|
GreenNight posted:Just be a shut in with no friends or family, problem solved. That was me at 18--the security guy will make fun of you for not having any friends. Clearance still granted. 
|
|
#
¿
May 11, 2016 00:55
|
|
|
"Backslash is the one next to backspace"--worked for our users.
|
|
#
¿
Jul 27, 2016 20:33
|
|
|
Vargatron posted:Speaking of Polycom phones, has anybody had an issue to where phone to phone calls were clipping and dropping out? We don't have an on-premise server handling our phone traffic. It's all being routed out to the cloud, even for phone to phone communication. The strange thing is that calls to external lines are not affected by this issue. AT&T says it's a vendor issue, but the vendor is saying that it's an AT&T issue. Had a site with a two-node server cluster using multicast and switches that weren't set up for multicast. The raw PPS hitting each phone port as a result was overwhelming them.
|
|
#
¿
Nov 7, 2016 15:23
|
|
|
jaegerx posted:you contribute so much, please elaborate for me. Pretending secret clearance meaning anything is about on par with "I know kung fu so my hands are registered with the police department as lethal weapons."
|
|
#
¿
Feb 20, 2017 08:57
|
|
|
Agrikk posted:No one does. Part of the interview process at Amazon is to get you to a place where you don't know (can't possibly know) the answer and then find out how you react. Do you shuck and jive and try to bullshit your way through the question? No thanks. Can you admit to not knowing something and demonstrate a proven ability to learn and be curious? Come on board. We have plenty of room for you. For firewalls, a good understanding of TCP separates intermediate skill from advanced. You need a solid understanding of how things work to be a good tshooter. Being able to recognize a incomplete or an aborted handshake in a connection table/packet capture gives you significantly more to work with than "it ain't working," which didn't take a network engineer to deduce.
|
|
#
¿
May 4, 2017 06:26
|
|
|
Sickening posted:Interviews that turn into IT trivia are a huge waste of time. I'll cop to using IT trivia. If I ask a 5-year ASA expert the NAT order of precedence, I don't require a flawless regurgitation. I do expect an experienced candidate to have fixed NAT issues in the past, and know what to look for--by their tools ye shall know them. People that don't have a solid understanding generally take longer to solve issues and are more likely to cause them. I try to ask a good mix of questions to cover typical problems, but you'd be surprised how many people think slapping a config on a device for a few years makes them an expert.
|
|
#
¿
Feb 6, 2018 03:52
|
|
"No clue, I would have to look it up or use the help command"
|
Sickening posted:I am the fans and heaps of other junk in there for no reason whatsoever. Our facility manager's office was like this when he quit. Phones from PBXs past, stuff salvaged from cubes, wiring from "we need 40 drops by next Monday."
|
|
#
¿
Mar 19, 2018 18:01
|
|
|
Colonial Air Force posted:It's more about print volume than users Users are important, specifically self-important. If you want to make an enemy, try to take a color printer from an executive assistant.
|
|
#
¿
Apr 2, 2018 21:06
|
|
|
Methanar posted:Always blaming DNS is a lack of creativity of how things can go wrong. The sentiment stems from "it's the network until proven otherwise." If it's not DNS, it's the server not being up. These are things that do not require a network engineer to figure out, and wading uphill through a stream of denials is the icing on the cake. Krispy Wafer posted:Same, but the network. 
Contingency fucked around with this message at 20:26 on May 4, 2018 |
|
#
¿
May 4, 2018 20:23
|
|
|
guppy posted:Particularly as they've waited until a few hours before the event to line this up. Planning, what's that? Pretty much. IT's unstated responsibility is to protect other departments from the consequences of their bad decisions. If you say yes, you're a doormat or "the help;" say no, you're not a team player or difficult to work with. Pay close attention to what happens when they escalate to your boss. If your boss rolls over, your team is weak and overwork is on the horizon.
|
|
#
¿
May 7, 2018 17:57
|
|
|
|
| # ¿ May 29, 2024 23:40 |
|
|
Sickening posted:Graduates have this small window where employers will almost fight over you to get a chance to mold you into something that currently costs them an arm and a leg. Please learn to code or at the very least becomes mediocre at a scripting language before you graduate. The future you will thank me. I can echo this. I did a stint in the military and graduated from college in my late 20s. I fell into that "no experience is better than some experience" trap and even had a recruiter refer to me as "mid-career" at a school job fair. Better to pass on 20 qualified candidates than risk getting a bad one, I guess.
|
|
#
¿
Jul 2, 2018 19:47
|
|