Live data from Hacker News

Hire people who aren’t proven

leonardofed.io

361–370 of 460 posts

Re: Hire people who aren’t proven

#361
post #304

Earlier quoted context omitted.

Google loved asking questions relating to the square-cube law. Like "you're shrunken down to the size of a dime and placed in a blender that's going to start in thirty seconds, what do you do?" From what I gather, this is covered in required curriculum in schools like Berkeley, Stanford, MIT, etc. I've never heard of it in my life, and I was one of the top two in my CS graduating class. IMO, this boils down to cultur…

Those questions are no longer asked. Most questions these days come from sites like leetcode, hackerrank and other online judge sites. These companies now specialize in creating online tests. Where in you will have to enter a working program, which takes input through stdin, and has to print output to stdout. There are typically a huge range of tests your program has to pass. Several of those tests are to check if yo…

Before this people (like Microsoft) used to ask riddles. Now, I'm pretty okay at and enjoy riddles, and ridiculously good at multiple choice tests. Bits of this come out in how I approach troubleshooting and debugging.

The last place I interviewed at that did riddles ended up offering me the job, but I teased them even before they asked their riddles about how it wasn't a good interview technique. I could kind of tell they were thinking "oh boy, another guy full of excuses for why he's not gonna pass the interview process". Second riddle, I started talking and had the answer within a single sentence. No pauses, no sentence fragments. Now I had their attention.

Since it was a rapidly growing company I was in the interview pool within three or four months and it took me maybe six months after that to convince all but one person to stop using riddles for interview questions.

Point is, if you disagree with an interview technique but can manage to get through that filter anyway, you owe it to the rest of us to say something. Apply some peer pressure whenever you can.

Re: Hire people who aren’t proven

#362

The problem that has happened at my company is that we take a "chance" on bootcampers or other people who aren't proven, we spend the time and effort to mentor and train them, pay them well, and then they turn around in 9-12 months and leave us for another company with their enhanced experience. It has happened 3 times so far, so we have stopped hiring bootcampers, and fresh grads and instead have started hiring peop…

Conversely, I found it really hard to establish myself as a solid contributor and even a technical leader when I joined a team as a (relatively) newly minted developer.

No matter how far I progressed, or how competent (even excellent) I became, I was still perceived as the "kid", even though my colleagues are only a few years older. I think I've mostly overcome this, but TBH I'm still not certain and I've been here for ~3.5 years in this role, and have been promoted to senior developer. None of that matters to my coworkers.

Moving teams is a much easier way to shed that "newbie" reputation (a path I decided not to take). Is it possible someone is creating this culture at your work that locks people into their role when they join the team?

Re: Hire people who aren’t proven

#363

The problem that has happened at my company is that we take a "chance" on bootcampers or other people who aren't proven, we spend the time and effort to mentor and train them, pay them well, and then they turn around in 9-12 months and leave us for another company with their enhanced experience. It has happened 3 times so far, so we have stopped hiring bootcampers, and fresh grads and instead have started hiring peop…

I think we find a similar thing with people relocating to our city. They are most likely to leave after a year or two.

Re: Hire people who aren’t proven

#364
post #6

I think hiring has become more difficult now that programming has been discovered as a well paying mainstream career. When I started in the 90s most people I worked with had a passion for the craft but now I find we interview a lot of people who have a CS degree just for the career prospects but not out of interest for the craft. I find it much easier to deal with someone who has no relevant experience but cares vs s…

It just seems like false dichotomy to me. The idea that you must project passion the right way else you don't care. I think it did not worked that way on 90ties either.

Also, people who stayed in this industry long do care generally.

There is also something good to he said about people who understand importance of boring tasks and negotiation and planning and process and do those boring tasks.

Re: Hire people who aren’t proven

#365

Earlier quoted context omitted.

Senior is ten years +/- a year depending on what they accomplished in my opinion.

Your opinion is not the established nomenclature. Senior is widely understood to be 4 yr degree + 5 yrs experience. This means you have all the technical training plus enough professional experience to be considered fluent. At ten years you should be absolutely expert in the areas you've worked in. This is staff or senior staff level, if you also have some business acumen, ie the ability to see beyond engineering req…

I don't really care what the established nomenclature is. I was stating what I consider senior and 5 years of industry experience doesn't cut it for me.

Re: Hire people who aren’t proven

#366
post #359

Earlier quoted context omitted.

> It's like a 6 week community college course to become an EMT. There's a test drive for you. There are 2 year programs that will get you a nursing license. EMT and nurse aren’t “mini doctors,” any more than doing video game QA is “mini programming.” It gets you near the profession, it doesn’t put you into the shoes. I don’t know how to articulate this. The job that requires about eight years of post-grad training, i…

What about shadowing a doctor in high school? You literally follow them around all day and get a taste of what they do.

The thing is, the salient bits of being a doctor have to do with the thought process going on in their head, the stresses of responsibility and decision-making, and all the considerations they weigh with each patient. It's just not an "observable" thing. Docs don't really start sharing their internal processes with you until you're in the second half of med school, and even then not commonly. From the outside, it just looks like... guy in a white coat, often at a computer, making pronouncements. And then doing paperwork, which largely consists of documentation to prove to the government and insurers you did everything they decided should have been done for that patient and if not, why not. The combination of accountability and lack of autonomy is a leading cause of physician burnout and, again, is all internal.

The other part it leaves out is the hours. "What do I do with this patient?" is a very different thought process at hours one, eleven, and eighteen respectively, of what should have been a twelve hour shift. One hospital I know of has its trauma/SICU surgeons do 5 days on and 5 days off where they pull 12 hour shifts daily, and they're on call every night. But trauma/SICU doesn't really sleep, so these folks are making critical care decisions at hour one-hundred-and-twenty, of which maybe eight hours involved sleep.

All of these things occur in the internal landscape. Shadowing is ... not effective.

Most med students have done clinical research, shadowed doctors, volunteered in hospitals, etc. Back in the day, I did hospital volunteerism, clinical research, hospital QI, and I worked in health insurance. I'd seen medicine from pretty much every vantage point before I second-careered into being a physician. And every senior med student and resident and physician will tell you, "holy shit, I had absolutely no idea what it would be like." Even the occasional nurse that decides to go to med school, who most commonly think they're halfway to being docs already, will say "omg, I had no idea how much I didn't know, and how much you guys have to do." We had two in my med school class back in the day. When we were in didactics, they were shocked by how much docs had to know. When we got to clerkships (the second half of med school, where you work in hospitals) they were floored by how much was involved in being a physician that simply wasn't visible to nurses. And that's... you know, nurses. Folks who work in our vicinity on a daily basis.

Re: Hire people who aren’t proven

#367

Earlier quoted context omitted.

You're talking about the bad ones, the ones I hate to see. The friends I'm talking about are all excellent professionals. Passion matters.

No, I'm talking about 99% of docs 99% of the time. It's a job. It's a great job sometimes, but it's paperwork most of the time. For every hour we spend rounding in the morning - when we're given at best 2/3 of the time we need to actually do the bare minimum, and half the time we need to really talk to people - we spend another 1-2 hours (minimum) in a windowless room doing a pile of paperwork notating the hell out o…

Would being a doctor be better in a system where there was /only/ a choice of either single payer or bring your own all-cash payment? (No 'insurance' at all.)

Re: Hire people who aren’t proven

#368
post #249

Earlier quoted context omitted.

What tends to be lacking in potential candidates? Dunno if you can know this if you're using a recruiter, but I'd be curious.

YMMV but numbers of them! we offer good salary/benefits etc, but on the whole senior and mid-level devs seem to be contracting for our tech stack (React/Node) and that's a path I'm not particularly keen on going down. edit: if anyone reads this and wants a job, I've put my email in my profile.

Hint: most of them are not contracting because they particularly like the contractor's life. They're contracting because they can be paid more. I think in London the reality is that, if your company is using a new and hot tech stack (say Spark or Kubernetes), then the contractor's rate IS the market salary, as most people how know this stuff are doing contracts. You can find them as full-timers with regular FT salary (60-90k GBP ?) too, but that's more of an exception and a lucky catch I guess. Also, once they figure out how easy it is for them to make more doing the same work, they might leave anyway.

Re: Hire people who aren’t proven

#369
post #41

Earlier quoted context omitted.

Cares about what though? Building simple,solid, maintainable software that does what it is supposed to? Or cares about chasing every new fad, has ten frameworks listed on their resume and is currently midway through the machine learning / blockchain hype? I care about the former, but plenty of people would see that as having little "passion". For example, I don't have any experience using NoSQL databases on my CV, be…

After programming professionally for several years now I'm always shocked to hear that people program for fun in their free time. Once I get home from work, the last thing I want to think about is writing software.

For many, it completely depends on time spent at work and effort spent at work. I've been on both sides. If you spend a lot of time and effort at work (not a bad thing), your desire is diminished outside of work. However if you don't have to spend a bunch of time/effort at work, there is time/effort available. Granted, even that relies on whether you enjoy it over other things, but you shouldn't be shocked.

Re: Hire people who aren’t proven

#370

Earlier quoted context omitted.

No, I'm talking about 99% of docs 99% of the time. It's a job. It's a great job sometimes, but it's paperwork most of the time. For every hour we spend rounding in the morning - when we're given at best 2/3 of the time we need to actually do the bare minimum, and half the time we need to really talk to people - we spend another 1-2 hours (minimum) in a windowless room doing a pile of paperwork notating the hell out o…

Would being a doctor be better in a system where there was /only/ a choice of either single payer or bring your own all-cash payment? (No 'insurance' at all.)

I don't know, to be honest. I know a lot of docs blame insurance for this, but I've worked in health policy and insurance - the problems are bigger than that.

A lot of the documentation is an attempt to create "quality standards". I like that in theory, and it's independent of what kind of payment mechanism is used, but ... docs will have a riot if we're held accountable for final outcomes ("This guy has had 30 docs in 20 years, smokes like a chimney despite my repeatedly trying to get him to stop, and I'm getting my wallet drained because he had a heart attack?").

Alternatively, process measures ("Did you put everyone with high cholesterol on a statin?") kill autonomy, require documentation, destroy nuance (there's a good reason I don't want this patient on a statin) and also calcify medicine (advances in medical knowledge occur faster than Medicare updates its performance metrics).

Unfortunately, "quality care" is also a PR move to cut costs. Create enough metrics over enough things docs have no control over, and a documentation slip-up becomes a good reason to ding us our reimbursement. This documentation is also a way to cut government and insurance budgets: they want the information for their programs, but don't want to pay for anyone to convert unstructured medical notes into structured data. Therefore, it becomes an unfunded mandate plopped onto physician's heads. That's not going to go away, unless all insurance - public and private - go away.

All-cash payment removes documentation because there's no one to be accountable to. There's no central party trying to track your outcomes. But... I like the idea of tracking performance. I like the idea of encouraging quality care. I wouldn't mind if we could divorce quality metrics from centralized payors, and put the cost burden of data entry onto the party using and benefiting from that data rather than physicians.

Some of the paperwork headache won't go away regardless. Primary Care docs spend most of their time doing bullshit paperwork tasks. As often comes up on HN, an employer won't let you bring your own chair to work - unless you get a doctor's note. Family med guys write stupid notes every single day, and it occupies a significant percentage of their workday. It's disheartening, and it's not going anywhere.

Another big thing that's happened is social work. Every issue that society doesn't want to deal with rolls down to healthcare: the homeless, the mentally ill, the uninsured, eventually land in an emergency room. That means we're the central clearing house for social services. Psychiatry - especially ER psychiatry - spend probably as much of their time (or more) networking with social work and the state trying to secure Medicaid and housing for patients than they do addressing their mental health needs. It's work that needs doing, but man is it heartbreaking to train to be a physician just to spend your day trying to arrange housing.

Lastly, even a single payer system has incentives to deny services. That's still a cost borne by the system. Accordingly, docs will still find themselves fighting paperwork battles with the insurer to justify a course of treatment - they'll just be doing it against a single bureaucracy instead of several.

Post reply on HN