Register a SA Forums Account here!
JOINING THE SA FORUMS WILL REMOVE THIS BIG AD, THE ANNOYING UNDERLINED ADS, AND STUPID INTERSTITIAL ADS!!!

You can: log in, read the tech support FAQ, or request your lost password. This dumb message (and those ads) will appear on every screen until you register! Get rid of this crap by registering your own SA Forums Account and joining roughly 150,000 Goons, for the one-time price of $9.95! We charge money because it costs us money per month for bills, and since we don't believe in showing ads to our users, we try to make the money back through forum registrations.
 
  • Locked thread
MononcQc
May 29, 2007

I remember joining a student job and telling them "I can work any night of the week except Monday since I have class that night", them saying "fine", calling me in on a Monday telling me I was scheduled while I was not. I managed to show up there anyway only for them to say "oh sorry you were right you were not scheduled but while you're here why don't you work tonight?"

Then when they gave the schedule for the next week with me scheduled on monday night again; I repeated "nope, I told you I can't work monday nights, I'm not giving up school for a part time job" and they fired me for 'lack of motivation' after 2 weeks.

well that's my story of lovely totally legal and valid reason for being fired.

Adbot
ADBOT LOVES YOU

MononcQc
May 29, 2007

I'm fine with people thinking I do geeksquad stuff. It's not like we'd have deep conversations about the intricacies of whatever network stack during a random encounter. I'll correct them if they ask me to look at their computer but that's it.

MononcQc
May 29, 2007

I have a latex resume because I wanted to learn latex at some point and it turns out it's easy to keep that stuff up to date if you never gently caress with the layout again

MononcQc
May 29, 2007

qirex posted:

does latex still use that janky serif font with the bad geometry by default?

yeah that's the one you have to leave in so the interviewers know you used latex

MononcQc
May 29, 2007

curufinor posted:

Lol at typesetting equations in word

Just lol

surface stuff with a stylus is p. nice

MononcQc
May 29, 2007

JewKiller 3000 posted:

yo that's pretty g drat impressive i must say. it even recognizes your properly crossed z! and your hosed up psis!

I got it on google I haven't tried it for myself, but my windows work computer is a surface book and it is doing pretty drat well at some forms of text recognition. Like I can honestly say that for note taking, one note has exceeded my expectations in pretty much all the ways. text + media + drawing + text recognition + whatever the gently caress you want on infinite pages. It's pretty good. Like I'd consider buying a personal one in the future if it were not about the abysmal terminal situation on there.

MononcQc
May 29, 2007

I use ConEmu but it chokes on vertical splits like an idiot

MononcQc
May 29, 2007

if you want me to worry about the job and the health of the business as much as the CEO does, you'd better be paying me CEO money

MononcQc
May 29, 2007

Carepost:

Stymie posted:

yeah basically if you can't explain what you do, it's not because it's beyond the ken of mortal men, it's that you don't know how to communicate or teach properly

being good at teaching is a learned skill just like anything else and if you haven't bothered to learn it, it's your problem when you can't explain things effectively to others

that really depends on what you do and how much accuracy you want. Some jobs work in obscure corners of industries some people don't even know exist, and some people don't know the difference between "the internet" and outlook.

I found it hard to explain what the hell was going on when I was working on real-time bidding optimization for retargeting campains. Ended up just saying "we run an auction system for the ads you hate on facebook and have to make it fast".

I found it near impossible to explain what my job at Heroku was. Like what the gently caress is a proxy, an HTTP server, or a log router anyway? How do you start to explain certificate management and SSL termination to someone who doesn't even know what a website is? I ended up giving up and saying I worked on hosting websites for other businesses, which was still confusing enough as a concept -- people who knew what a website was and had a brief idea of things thought I managed server racks. Saying just "I'm a programmer" would have carried near 0 information but would have left them with a more accurate picture of my job.


The core of it is that explaining something requires bridging the gap between what the person knows and what you want the person to know. You can do it carefully over a longer period of time so the other person gets all the intricacies, or you can do a fast job going for the broad strokes and outlines. In some cases though the gap is so large that at best the approximation you'll create is going to be so coarse that it's wrong for the vast majority of cases and it will be unclear whether you helped them understand or actually instilled bad concepts.

Take for example explaining the following topics to a 12 years old:

- good: explaining relativity through the "man on a moving train" frame of reference so people get an intuitive feel for it
- okay: showing a subatomic model stopping at protons, neutrons, and electrons (good enough, who needs to know about quarks and leptons and bosons)
- bad: whatever people try to do with explaining quantum physics and you end up with "anything is possible through the magic of entanglement" as a deus ex machina in lovely scifi
- oh god why did you get into this: explaining how quantum computing works

"If you can't explain it in one sentence you don't understand it well enough" is a good rule of thumb, but it has heavy assumptions about the expected background of the person you're explaining it to. The fun part is figuring out at which point trying to give a short and brief explanation harms more than it helps.

To put it another way, even if specialists really understand how to remove an infected appendix with little risk, they won't teach laypeople how to do it, and every regular person will just stick to heimlich and CPR for the most part.

MononcQc fucked around with this message at 13:10 on Jul 20, 2017

MononcQc
May 29, 2007

you wouldn't drag me to work into Trump's US for 300k a year

MononcQc
May 29, 2007

ADINSX posted:

My plan is to get them to talk a lot about their projects. What'd you do, why'd you do it, what benefits did it provide, can you sketch out a rough flowchart or diagram that helps explain the concept?. Basically grade them on their ability to explain this stuff to non experts because thats what we'll be hiring them for, it doesn't do us any good if we bring someone in and they do some black magic and we get a mystery report, because how can we explain its value to customers?
That's a generally good approach. Chances are you're hiring someone who is a bigger expert than you are with one of two goals in mind, possibly being on a spectrum:

1. Grow the expertise you have in your company
2. Get this one employee to do a bunch of specialist work that only they can do

Number 1 is one where you hire and want someone to join your team, be able to teach to coworkers and train them, help hire, and set the baseline of future development for what you have. You'll want to have someone you can trust to explain to non-specialists, and to assess skills of others. So you can get them to do that by evaluating how good they are at explaining poo poo to you, by reputation, or by some referral from someone you trust.

If they come visit you with that role in mind, they will likely want to ask questions about who they'll work with, what the initial timelines are looking like, and probe for the level of commitment the org will have to that specialty or part of the project.

You'll possibly want to ask, on top of what was mentioned above, how they would plan to distribute work and ensure maintainability of a system of which they will (initially) be a central point of failure and contention. But overall, they're unlikely to be a hire you'll want to make based only on their technical capabilities. In fact it may be better to hire someone who is not as much of an expert, but is good to explain and on-board your org and the rest of people. They'll know more and may be able to drive the rest forward.

Number 2, aside from researchy subjects or things with a bunch of optimization work, is not going to work super well without organizational support unless it's a one-off component. Those are possibly a better fit for a consultant or company that knows the tech at hand to develop and ship for you. In case you still want to hire, you do get that problem of 'trusting someone when you don't trust yourself to judge them right'. There you can't do much but expect a higher degree of failure. Interview more people, establish a kind of baseline for what you're seeing, and go accordingly I guess?

MononcQc
May 29, 2007

Are there other jobs prior to these in your resume? Usually, 2-3 short jobs is not a straight up dismissal in the recruiting I've been part of, but it will necessarily bring up questions in the interview itself regarding motivations and to figure out if it's someone who just likes short jobs, can't get along with people, or just seems overall difficult. Or sometimes you get consultants who put each gig on their resume so it looks pretty gnarly, but if they can explain it away why not.

Anyway, it's close to the limit, but at that point I'd say it's yours to lose by poor explanations. Usually things like "got a bigger payday elsewhere", "place ran out of money", and so on are alright and can pretty much be repeated often I'd guess. Things like "they didn't give me fun enough projects" or "I didn't like the team enough" coming up many times raises flags.

MononcQc
May 29, 2007

I once interviewed someone who was leaving after 3 months in the industry because his employer refused to give him the core interesting algorithmic projects while "he had a masters in Math" so he was looking for a place to use him to his full potential.

Yeah sure, new hire with no experience, let's give you the central piece of business everyone in here would enjoy working on, why not. The others can maintain the tests.

MononcQc
May 29, 2007

once interviewed at a place where the technical reviewer was familiar with my work and hated one of my open source libs :toot:

MononcQc
May 29, 2007

Arcsech posted:

actually what i really want to do is get a remote job and live wherever the gently caress i want

it is the best.

MononcQc
May 29, 2007

Sapozhnik posted:

all you 100% remote-work people better be real confident you aren't about to get outsourced to Bulgaria or whatever because there's a lot of really talented and extremely cheap labor out in that neck of the woods

Oh no no, I am the outsourced work. You see, your boss can pay me maybe 30% less than a bay area employee (and even a bunch less since the Canadian dollar is low), and I'll have more than twice as much money left as the bay area employees anyway, and will likely end up in the top 5% salaries of my area. I'll also work reasonably close to your boss's timezone or even the same one, speak the same language, and will be ready to travel on prem from time to time for cheaper than other outsourced work.

The remote employee who lives out of major urban centers but within the country or continent is the premium outsourcing level. The Bulgarian employee is a few steps further.

But more seriously, it's a cultural thing. Back at Heroku, over 50% of the engineering department was remote. Despite having the most expensive offices with all the perks, employee satisfaction was invariably greater for remote employees than on-prem one, albeit by reasonably small fraction. If you're the lone remote employee you're in for a real challenge, but if you're on a full team dedicated to it, it's not that different from OSS work in terms of dynamics. My current workplace is really all local. Like nobody (95% of employees) uses e-mail or chat except to tell people about headlights left on in the parking lot and it's a hell of a bigger challenge.

Sapozhnik posted:

and personally i don't think i could handle working 100% remote without contemplating death because i'm a reclusive enough shut-in as it is :smith:

but that's just me

Yeah that's the big killer. You have to be a) okay with being lonely / having a healthy social network outside of work b) be good at self-discipline because you can't gently caress off and play videogames all day, and c) be good enough at self-discipline to enforce a good schedule and healthy life habits that won't lead to work and personal life melding together.

They're mostly all tied together, but there's nothing worse for the remote worker than to work in underwear around the clock and forget their own life. Contrary to a lot of beliefs, remote workers tend to be working longer and unhealthier hours than local employees. It helps to keep a strict schedule, dress to work, etc.

MononcQc
May 29, 2007

good on her for being an apostle of recursion

MononcQc
May 29, 2007

As one of the only remote employees at <current workplace>, nobody sends me meeting invites unless they really need me there because they all hate getting on a conference call rather than just in a conference room. I don't know if it's a good thing or not so far.

MononcQc
May 29, 2007

Diva Cupcake posted:

if you're just using that job as a 2 year platform for more figgies elsewhere, it's fine. if you want to stay and get promoted from within (lol @ that happening) that's bad.

I'm a systems architect and there's literally nowhere up to go on the technical track aside from taking the role of my direct boss (lead architect) in this company. Above from him are top VPs right under the CEO and I wouldn't get those jobs anyway.

So yeah, more figgies might be had only by switching jobs or the CEO eventually selling the company or buying back options, or cool and good bonuses.

InfrastructureWeek posted:

that's the tldr and it's bad :(

It's not great since a lot of informal talk is missed, but I'm glad I no longer have the 3+ hours of meetings in google hangouts a day I had at Heroku.

MononcQc
May 29, 2007

cis autodrag posted:

Why don't they all go into a conference room and you can call the room phone and they can put it on speaker? This worked fine for me whenever I had to have remote people at meetings.

That's the one thing I never figured out. Any other team in another business uses chat or email or goes to a conference room and are fine just CC'ing other people. These folks (at least in the main office -- satellite offices are fine) really do everything face to face. This is a ~1000 employees company, with maybe 400 developers. I receive nearly no e-mail aside from people telling others that their tires are flat in the parking lot or that a phone has been found on floor 4. They otherwise use Skype for Business for conference calls (every room has giant microsoft surfaces) but most people don't really use them aside as a way to e-mail their whiteboard drawings to each other.

So I can call into the meeting rooms, but I have to be aware there is one first. They seem to be mostly improvised, or the schedule is known by tribal knowledge which you can't get if you're not there.

I've never really seen that kind of thing before at a tech company. If they ever get in a big lawsuit, there's gonna be nearly nothing but kanban boards to subpoena!

That's really made "being the sole remote employee" a lot harder than what it would have been in any other company. I ended up being more focused on their satellite offices because they see the same problems with regards to the mothership, so they're more open to non-face-to-face communication to begin with.

MononcQc fucked around with this message at 20:04 on Aug 23, 2017

MononcQc
May 29, 2007

Punkbob posted:

took new job to get away from boss that blew up on me sometimes.

new boss blew up on me.

am I the problem? am I too argumentative?

Serious response here.

You wait a couple of days for things to cool down, and then you go talk to exploded boss, with something like "hey, so I wanted to figure out a bit what happened for things to escalate between us during the meeting last <day of week> to make sure things go smoothly between us in the future. Do you have a bit of time to talk about it?"

This is not going to be a technical discussion about who is right or not, but about figuring out everyone's state of minds and expectations during the event. The objective is to set up a context where it feels safe to open up and discuss what is really going on; the objective is not to criticize or figure out right or wrong, but to make sure everyone is on the same page with regards to what happened and why it did.

When boss is ready for the conversation, you go and tell them that the vocal reaction you received and the sudden heat of the discussion took you by surprise, and you'd like to figure out what led up to it. You don't tell your point of view yet, you ask them for their vision of things.

You may get anything from them telling you they are under stress for X and they're sorry, or that they have observed a disrespectful pattern Y from you, or that the way you said thing made them feel some way, or just flat out dipshit responses like "you shut up I'm the boss don't second-guess me you junior garbage". If you get the latest, you get up and leave calmly, give your notice and/or switch teams to find a more adult person to work with.

If it's any of the reasonable answers, acknowledge their feelings, and then you may show your point of view. You felt this was a technical argument and did not realize the aspect of the situation that led them to perceive things the way they did, and you worry it might even be a pattern in how you do things. Open up by offering them to call you out a bit earlier on annoying behaviour if you both want things to be corrected. If everyone is in a good environment that they try to improve, this should be no problem to you nor them. You'll be able to move on, and you'll have a much better relationship with your manager going then.

Now this is not likely to yield really amazing results, because if your boss was truly reasonable, they'd have had the experience and emotional intelligence or awareness to do this poo poo with you already without you having had to lead the way at first, but that may have been a lapse that can be fixed.

MononcQc fucked around with this message at 14:27 on Aug 25, 2017

MononcQc
May 29, 2007

Notorious b.s.d. posted:

dude you are turbo-hosed

i would be looking for a new job already, because the first time someone is looking to cut payroll, your rear end is grass

  • 100% remote
  • high rank/pay, but no reports
  • nobody uses conference calls
  • high value placed on face to face interaction
  • all critical employees are in a single office

you put your dick in the beehive on this one

Eh no it's not so bad. I'm involved in 3 high-profile projects and provide training & recruiting in one full office as well. I get some meetings, but only those where I'm actually necessary and won't be sitting alone doing jack poo poo. I'm not extremely worried, but wouldn't expect them to keep me for a million years either, which is fine.

Also at this point I'm not too worries about cutting payroll. They've been growing their market nearly 30% a year for over 10 years non-stop. When it stabilizes and stalls I'll see, but something tells me people, corporations, and governments investing in security and surveillance is not going to become an irrelevant market in a couple of weeks.

MononcQc
May 29, 2007

if you had to use skype for business you would also avoid contacting anyone whatsoever

MononcQc
May 29, 2007

Yeah I always treat it that way (the precariousness and having to demonstrate the value) -- nbsd is right about that. Any employee could benefit to do that[1], but being remote forces you to do it all the time because you do not want to become totally forgotten. Face to face is higher bandwidth, and easier for most people who have a fraction of social capability. It's part for the course and a thing to keep in mind.

If you're remote and people won't talk to you, you have to go talk to them. But I'm fine not going to "let's re-discuss prioritization of sub-tasks A-32" and only being invited to "please help us make sure we designed this protocol right" in terms of meetings. This is easier to do when people publish their work internally company-wide, but these people don't really do it, so you have to go in and ask the teams about some projects, or get involved from day 1.

Training is a bad sign if you're showing basic training like "how to write babbi's first makefile" or "how to use powerpoint" because they're giving you busy work (or maybe training your own replacement), but right now it's "here's a group of 12 people wanting to use <tool you know>, help train them and show them how to ship software with it". The precariousness of that role is limited to a) doing such a good job they never need training again, and b) the org abandoning that tech -- it's closer to consultation which, while short term, can last a decent while in an org with hundreds of engineers.

I would not last very long if this were my first remote job, but I'm at like year 7 of remote work right now and I've seen a few of the patterns around. I'm not too worried and can smell a sinking ship.

[1] That's how you get people up the hierarchy to root for you in perf reviews and to give promotions and raises, particularly when Remote, but even when local. Since you can't advocate for yourself behind the closed doors of directors and/or managers giving reviews, your best way forward is to have any single one of them (hopefully not one seen as an idiot) push on your behalf without being prompted to other managers and/or directors. If you don't have that relationship, you'll never have a promotion outside of union rules if any.

MononcQc
May 29, 2007

I've interviewed at places that won't even give a range until you fly out there for an on-site set of interviews and it's always a huge pain in the rear end. Like give a range or some poo poo.

MononcQc
May 29, 2007

you ask people what they're working on, tell them it's cool, then mention what you are working on, wait for them to say "holy poo poo that's way cooler", then do a 360 and moonwalk your way out of there

MononcQc
May 29, 2007

I unironically keep paper notes of poo poo I do, experiments I run, and meetings I attend at work.

MononcQc
May 29, 2007

the truth is I like fiddling with pens and if I don't take a shitton of notes I'll have the same one for 4 years without any reasonable reason to get new ones.

the other truth is that poo poo works way better for everyone involved if after a meeting you can send people a summary of what was discussed with action items assigned to specific team or people.

MononcQc
May 29, 2007

Progressive JPEG posted:

all it'll take is a quarter with only 20% annualized growth

I think that's already done tbh

MononcQc
May 29, 2007

a manager who knows how to program but refuses to get out of the way and still wants to touch the code is possibly one of the worst kinds of managers possible.

MononcQc
May 29, 2007

which is more invasive, a piss test or a background check through your history

MononcQc
May 29, 2007

From experience, not having a degree hurts when trying to get a job and go through recruiters or HR who take a degree as
mandatory, when consulting (because agencies and those contracting them put on similar requirements) and if you're trying to emigrate anywhere -- not having a degree automatically puts you in the ´unqualified worker' bin no matter how much real world experience you have.

MononcQc
May 29, 2007

cronyism & rep is how I got most jobs so far. you update the resume to hand it off to HR after you've already got to talk to the team that will be hiring you and got temporary offers and off you go.

Adbot
ADBOT LOVES YOU

MononcQc
May 29, 2007

if you change the page count to like 22 and 23, you can align post boundaries until the page shows up

  • Locked thread