News for hackers. Stuff that matters.
Re:Ten years of experience, still failing phone screens by vanusa on Friday December 10, 2021 @08:56PM (#29517683)
This post ought to be the final nail on the coffin of the cult of leetcode/whiteboard style inverviewing.

Just looking at this guy's repo and his writing style -- you'd be foolish to waste his time or yours on leetcode-style hazing. Your conversation should be strictly high-level. If you must, pick a file at random from one his larger projects, and ask a few straightforward quetions ("I'm new to Go - can you explain why I would use this datastructure here?") just to make sure the repo isn't a copy of someone else's, and he isn't outright trolling you. Apologizing as you're doing so, of course ("Sorry, but do you mind if I ask a silly-sounding question or two about something in your repo?").

That's all you need to do. Most candidates won't have work samples that are quite as slam-dunk, of course. But still, your own "smell test" can save you tons and tons of time (and the candidate, agony). It's really, really hard to fake one's way through questions like these -- and really easy to tell if someone is trying to do so.

Put another way, your basic mindset should be: "Trust, but verify". Not: "Joel Spolsky wrote that post 20 years ago claiming that 99.5 percent of all candidates are utterly incompetent. Therefore I need to torture this guy until he confesses."

At least as far as answering the "can he/she code?" question is concerned.

Re:Ten years of experience, still failing phone screens by nijave on Saturday December 11, 2021 @12:16AM (#29518643)
Im not a huge fan of leetcode or work samples but on the receiving end it weeded out a huge number of bad candidates. We'd get tons of copy/pasted together infra as code from top Google results that wasn't even close to runnable (usually being close to runnable with a few small bugs was a good submission and runnable with no bugs was a great submission)
Re:Ten years of experience, still failing phone screens by vanusa on Saturday December 11, 2021 @12:33AM (#29518709)
On the receiving end it weeded out a huge number of bad candidates.

Along with (as was the main point of the original blog post) probably quite a few false negatives, Like the author of that post, for example.

Meanwhile, you can achieve the same filtering benefit by far less obnoxious and more accurate means (a cursory glance at their repo, fore example).

Re:Ten years of experience, still failing phone screens by wiseowise on Saturday December 11, 2021 @01:58AM (#29519077)
I'd rather filter out good candidate than let bad in. It's a domino effect. You let one bad, he will hire more in the future.
Re:Ten years of experience, still failing phone screens by Supermancho on Saturday December 11, 2021 @03:05AM (#29519350)
> You let one bad, he will hire more in the future.

When your organization can recognize a poor investment but cannot act on it, you have an organizational problem. Why would someone get to hire more "bad" (for whatever that means) if you can recognize it? Even if you're doing all the hiring yourself, it's unlikely you'll have a 100% record over time.

Re:Ten years of experience, still failing phone screens by quietbritishjim on Saturday December 11, 2021 @01:32PM (#29523080)
For one thing, in many countries it's hard to get rid of a poor employee unless they're malicious or really exceptionally terrible.

For another, even if "an organisational problem" or inconvenient labour laws don't get in your way, firing employees can have a serious effect on the morale of those left behind. And for good reason! Usually companies that regularly fire people for poor performance has a different sort of culture than companies that don't. In my experience, that's the worse organisational problem.

The right solution is just to be more careful about who you hire in the first place.

Re:Ten years of experience, still failing phone screens by marcinzm on Saturday December 11, 2021 @06:33AM (#29520146)
Most companies have organizational problems. So a system that only works if you don't will fail for the majority of companies.
Re:Ten years of experience, still failing phone screens by vanusa on Saturday December 11, 2021 @08:43AM (#29520772)
Most companies have organizational problems.

Right. But we can't talk about that, of course.

Instead the corrective strategy seems to be: "Let's torture some more candidates. It's cheap and it's easy, after all."

Re:Ten years of experience, still failing phone screens by klipklop on Saturday December 11, 2021 @02:41AM (#29519270)
I always hear this but never seen proof. If they are bad how do they get into a position that lets them make hiring decisions?

Everyone likes to think they are the good candidate and not the bad one that slipped through…

Re:Ten years of experience, still failing phone screens by GoOnThenDoTell on Saturday December 11, 2021 @03:11AM (#29519379)
When they put it in the promo committee calibration doc that X level has done Y interviews per quarter, they end up on interview loops but then feel they must say no to Z% else they’re not “raising the bar”
Re:Ten years of experience, still failing phone screens by wiseowise on Saturday December 11, 2021 @03:05AM (#29519351)
> If they are bad how do they get into a position that lets them make hiring decisions?

We have flat hierarchy. Just volunteer to interview because your voice is on the same level as others.

Re:Ten years of experience, still failing phone screens by sofixa on Saturday December 11, 2021 @03:06AM (#29519358)
Isn't this why there are trial periods ( no idea if it's a thing in the US with the "right to work" thing)?. Over here in the EU a work contract can't be terminated from the company just like that, there needs to be a specific reason ( like downsizing, or a serious error), and you can't quit just like that a mandatory notice period is required ( of course negotiable depending on the situation), usually in the 1-3 months range. Therefore there's a trial period at the beginning, 3-6 months usually, during which any party can end the employment with a very small notice ( a day or two).

So if someone lied their way through interviews, in the first couple of months you should be able to detect that and terminate their trial period.

Re:Ten years of experience, still failing phone screens by Jensson on Saturday December 11, 2021 @03:21AM (#29519417)
> So if someone lied their way through interviews, in the first couple of months you should be able to detect that and terminate their trial period.

Managers hates firing people, it is really uncomfortable. So instead of firing this person to look for a new, they keep the person and say they need even more headcount and hope the next one is better.

Re:Ten years of experience, still failing phone screens by marcos100 on Saturday December 11, 2021 @06:13AM (#29520052)
Totally, it's like admitting that you don't know how to hire. And it's worse if HR is involved.
Re:Ten years of experience, still failing phone screens by marcinzm on Saturday December 11, 2021 @06:31AM (#29520135)
In the US you are always on a trial period. The problem is that firing people is annoying and bad for team morale. More importantly even dealing with a bad coworker is really bad for team morale. No one wants to join a company that is likely to fire them in 3 months because the company f-ed up their own hiring process. No one wants to recommend their connections join a company where that is likely to happen. Made worse due to a lot of compensation is tied to staying a year at a company so leaving early is basically getting paid 50% for that time.
Re:Ten years of experience, still failing phone screens by baskethead on Saturday December 11, 2021 @10:59AM (#29521779)
What is bad for morale is keeping someone around who is a bad fit. Netflix has solved this problem by paying everyone at the top of the scale and firing everyone who doesn’t meet their bar.
Re:Ten years of experience, still failing phone screens by baskethead on Saturday December 11, 2021 @10:57AM (#29521762)
The question is whether or not your interviewing practices filter out bad candidates. If your entire company has no employees then maybe but I find that hard to believe.
Re:Ten years of experience, still failing phone screens by nijave on Saturday December 11, 2021 @09:27AM (#29521067)
A lot of candidates don't have public repos and you need an equal comparison across all candidates (you can introduce a lot of bias trying to gauge two candidates against different sets of criteria)
Re:Ten years of experience, still failing phone screens by vanusa on Saturday December 11, 2021 @12:56PM (#29522830)
A lot of candidates don't have public repos

It doesn't have to be a public repo of course. They can just send zip file.

You need an equal comparison across all candidates.

"We'd like to see a code sample -- something we can build and compile, that you feel is representative of your skill level."

Sounds pretty straightforward and egalitarian to me.

Re:Ten years of experience, still failing phone screens by detaro on Saturday December 11, 2021 @01:04PM (#29522894)
I'm curious, if we exclude all your open-source work (assuming you have some), what did/would you submit when given the question?
Re:Ten years of experience, still failing phone screens by vanusa on Saturday December 11, 2021 @01:45PM (#29523200)
Floppy disk? A printout?

Long before open source was a thing, and repos were even thought of -- I always had a few 1,000+ line personal projects I could dig up and show people.

Re:Ten years of experience, still failing phone screens by detaro on Saturday December 11, 2021 @01:48PM (#29523222)
right, and plenty people don't have large personal projects, or not personal projects that align with their work skillset, and the question is extremely vague what scope you're looking for.
Re:Ten years of experience, still failing phone screens by vanusa on Saturday December 11, 2021 @02:03PM (#29523333)
Right - it's a bar, and some people won't meet that bar. And that said - a pretty minimal bar.

1,000 lines isn't that large, btw - but yeah, maybe 500 would be a better number.

Re:Ten years of experience, still failing phone screens by nijave on Friday December 17, 2021 @06:23PM (#29599548)
Yeah, that's what Leetcode is. A bar. Some people meet it, some don't.

With Leetcode, everyone starts on equal footing (there's no bias towards people who code in their free time)

Yeah, it's extremely irritating as a candidate but it's something

Re:Ten years of experience, still failing phone screens by kevinburke on Saturday December 11, 2021 @12:39AM (#29518748)
People say this but then they reject answers that e.g correctly code the brute force solution or they don’t provide an algorithm to code for, so it’s not just “can you code,” it’s can you find the optimal algorithm and also code it, and usually the algorithm isn’t trivial or one you’d ever run into at work.
Re:Ten years of experience, still failing phone screens by indymike on Saturday December 11, 2021 @09:59AM (#29521289)
This is my experience hiring developers. If I hire without a code screen, it's a 50-50% chance the developer cannot close a ticket in their first month. With a code screen, I've had one developer not work out (personal problems). And I'm talking about "ensure that no trailing spaces are being inserted to the database in this csv import function" kind of tickets.

>usually being close to runnable with a few small bugs was a good submission and runnable with no bugs was a great submission

This is exactly what we do: check the solution, and if it's close we continue the hiring process. There is a huge difference between an almost working solution and what you get 70% of the time: code that will never, ever, ever work, even if it could run.

Re:Ten years of experience, still failing phone screens by gentleman11 on Saturday December 11, 2021 @05:04PM (#29524688)
> weeded out a huge number of bad candidates.

A lot of hiring managers have no concept of experiment design.

You can’t invent a measure (or copy it from a blogs about how other companies hire), look at who it rejects, and conclude they are bad. You don’t know if they were good or bad. You never worked with any of them. You only know that you applied your measure.

The only candidates you have any information about are the ones you hired, yet you are insulting the others on the internet today

Re:Ten years of experience, still failing phone screens by vanusa on Saturday December 11, 2021 @05:49PM (#29524997)
You never worked with any of them. You only know that you applied your measure.

What's interesting is that the people doing all this "weeding out" seem so sure that they're bravely defending the fort against an onslaught of incompetent hordes... and yet they're missing this extremely basic point about the nature of the process they've chosen to use.

Re:Ten years of experience, still failing phone screens by ipaddr on Saturday December 11, 2021 @01:25AM (#29518949)
You wouldn't know if they are bad candidates because you didn't hire them.
Re:Ten years of experience, still failing phone screens by wiseowise on Saturday December 11, 2021 @01:57AM (#29519067)
We do code submission instead of LC. Believe me, most candidate are complete, utter shit. And that's without even hiring them.
Re:Ten years of experience, still failing phone screens by yosito on Saturday December 11, 2021 @06:04AM (#29520027)
Sounds like many competent candidates are dodging a bullet by not being hired by you. What's the turnover rate on your team like?
Re:Ten years of experience, still failing phone screens by wiseowise on Saturday December 11, 2021 @06:13AM (#29520053)
> Sounds like many competent candidates are dodging a bullet by not being hired by you

How so?

> turnover rate on your team like?

2 years since I joined, hired one dev recently, no one left so far.

Re:Ten years of experience, still failing phone screens by aydwi on Saturday December 11, 2021 @08:12AM (#29520636)
Your mention of Joel's post made me curious to find and read it. I assume this is the post in question: https://www.joelonsoftware.com/2006/10/25/the-guerrilla-guid...

I'd say much has changed since he wrote that, and even for the time it contains some odd advice which he tries to force down the throat of the reader, but I'd be more interested to hear other's thoughts on the article.

Re:Ten years of experience, still failing phone screens by rightbyte on Saturday December 11, 2021 @09:47AM (#29521212)
To Joel Spolsky's defense, leet code questions where probably a great idea for him, when it was not an industry wide thing.

He also had this, what seems to me, nightmarish, dev. speed and progress estimation tracking app he made. I don't remember what blog post, but he described it and jokingly wrote that Lisa needed to get the speed up, or something. Fast forward to today and it is a predecessor to our agile nightmare. But I don't think that was his intent.

Re:Ten years of experience, still failing phone screens by chiph on Saturday December 11, 2021 @10:51AM (#29521693)
I remember when he made that post ("Evidence Based Scheduling"), and was also appalled. Yet, here we are today and programmer velocity is a now a measured metric in Agile.

https://www.joelonsoftware.com/2007/10/26/evidence-based-sch...

Re:Ten years of experience, still failing phone screens by rightbyte on Saturday December 11, 2021 @12:05PM (#29522387)
Oh ye thank you that is the one.

The general problem with Scrum like velocity tracking is that devs will start to lie to hit the estimates to keep the commissars of their backs. The best liar gets the straightest graph. And as devs learns to lie, you get the impression of improved estimation.

"Some developers (like Milton in this picture) may be causing problems because their ship dates are so uncertain: they need to work on learning to estimate better."

I mean ... why God. I don't know but maybe poor Milton has the hardest tasks, does not cut corners or what not. Brandon seems to "get it" and has silly narrow error range - I wonder how ...

(I am not bitter. Pinky swear)

Re:Ten years of experience, still failing phone screens by treis on Saturday December 11, 2021 @10:03AM (#29521306)
>Just looking at this guy's repo and his writing style -- you'd be foolish to waste his time or yours on leetcode-style hazing

Perhaps it's just me, but I took a look and I'm not convinced. Nothing jumps out to me as overwhelming proof of programming ability.

Re:Ten years of experience, still failing phone screens by bogwog on Saturday December 11, 2021 @10:27AM (#29521495)
Can you explain why? To me it's obvious that this guy knows how to code, and he's probably better at it than most of the engineers I've met.
Re:Ten years of experience, still failing phone screens by treis on Saturday December 11, 2021 @11:23AM (#29522008)
Hard to explain the absence of something other than it's just not there. The list of projects/accomplishments are fine but the reality is that people lie about stuff like that. I poked around their recent GitHub commits but it was mostly bug reports. Nothing really that points to being obviously great at coding.

I see that on paper they're a great candidate, but the reason that companies do these tests is that often the candidate doesn't measure up to the resume

Re:Ten years of experience, still failing phone screens by vanusa on Saturday December 11, 2021 @04:44PM (#29524549)
Nothing jumps out to me as overwhelming proof of programming ability.

Are you suggesting that leetcode tests provide "overwhelming proof of programming ability"?

Re:Ten years of experience, still failing phone screens by sangnoir on Sunday December 12, 2021 @12:47AM (#29527455)
Not gp, but obviously yes. I'm yet to meet someone who can pass a leetcode-style interview with sober and conscious interviewers, but can't code. Have you?

Leetcode and coding ability is an A -> B but B -/-> A situation: failing leetcode doesn't mean you can't program, but the reverse is absolutely the case.

Leetcode can't filter out other potential issues that may impact success (e.g. poor anger management, or poor judgement).

Re:Ten years of experience, still failing phone screens by vanusa on Sunday December 12, 2021 @12:29PM (#29531530)
I'm yet to meet someone who can pass LC, but can't code.

I should perhaps be clear that by "overwhelming proof of ability" I meant "the ability to program well". Which by definition does intersect with one's capacity for judgement, on a certain level. (Though is largely orthogonal to other behavioral issues, I find).

I see LC as providing proof of, at best, minimal ability. And I've seen plenty of people who can run circles around LC-style tasks, but when it gets to the bigger picture -- you know, writing good, maintainable software -- somehow, it just never comes together right.

We agree that obtaining proof of minimal ability is important. I just think that proof can be obtained in other, far less mutually degrading (and error-prone) ways.

Re:Ten years of experience, still failing phone screens by creamytaco on Saturday December 11, 2021 @11:50AM (#29522240)
Your post ought to be ample proof that subjective opinions (like the one you display here) are not solid grounds for hiring decisions.

When looking at this person's Github page, I -unlike you- see a vast number of trivial projects that can best be described as regurgitations of other people's work. Even worse, if you actually look at his first pinned project (https://github.com/kevinburke/nacl), you'll see that it is nothing but a wrapper with trivial changes/updates... an anti-project.

In the end, I see code that provides the illusion of competence but, when actually inspected, is actually telling me not to hire this person. The fact that pretty much anyone can declare oneself "a software engineer" today and easily present a veneer of competence together with powerful financial incentives, makes it absolutely necessary for any serious engineering team to have objective measures in place in order to evaluate candidates.

There are so many terrible engineers out there (and some even slip through the cracks and land at places like FAANG) that doing anything less is irresponsible.

Re:Ten years of experience, still failing phone screens by vanusa on Saturday December 11, 2021 @01:36PM (#29523118)
I never said you should just hire someone on the basis of their repo.

But rather, if you're looking for a basic smoke test which can answer the question "Can this person actually code? Do I want to spend more time engaging them?" -- there are better ways to do that than expecting them to cram on a list of algorithms to recite over the phone. Like looking at an actual work sample.

The fact that you looked at this work sample -- and came to your own conclusion about whether they would be worth engaging -- validates this very simple and basic point.

Which is your call of course. He may not meet your bar, but it would be absurd to say this guy can't code, and hasn't been around the block in terms of general CS concepts.

That said -- my own subjective opinion is that you're being exquisitely savage in your assessment of his NaCl implementation. Yeah, it's wrapper -- like it says in the Readme, and like a lot of working code out there. It's a pretty established way of solving a problem, in fact -- in some cases a very efficient and elegant way. It's not the same thing as writing 20k of primitives from scratch, of course. But that's not what he's presenting it as. He's not saying it's a "tour de force". He's saying "I think this shows we can talk about other things besides FizzBuzz".

And then other things you're like saying... like "an anti-project"? Wow.

Re:Ten years of experience, still failing phone screens by creamytaco on Saturday December 11, 2021 @02:46PM (#29523648)
Engineering is not about whether someone "can code", but whether someone can _engineer solutions to problems_. Has this person demonstrated that through the projects he chooses to put on display (and advertise as signal for his ability) on Github?

This is also what a lot of those engineering interviews are trying to ascertain, in a quantitative manner. I couldn't care less about someone's degrees or ivy league schools or Github projects (in isolation). These are all secondary -if that- considerations, problem solving ability being primary.

Re:Ten years of experience, still failing phone screens by vanusa on Saturday December 11, 2021 @03:29PM (#29523998)
Has this person demonstrated that through the projects he chooses to put on display (and advertise as signal for his ability) on Github?

Using the example you disparaged (his NaCl implementation), I would say:

"On first appearances, clearly yes. The problem was to adapt the a set of standard Go functions to a foreign interface - something one does quite a lot in an engineering environment. Also, the fact that he's aware of projects like NaCl and seeks to learn from the likes of Bernstein and Lange is a positive signal."

If I wanted to, perhaps I could drill down into the code and/or the NaCl spec itself. I don't know Go, so for all I know, maybe his code is actually horseshit. But all I'm saying is - from first appearances, definitely a positive signal. Infinitely more informative that FizzBuzzing (which would insult both his intelligence and mine).

This is also what a lot of those engineering interviews are trying to ascertain.

I've already made it clear that a glance at a repo does not obviate the need for an actual interview.

Re:Ten years of experience, still failing phone screens by kevinburke on Saturday December 11, 2021 @10:56PM (#29526984)
So I wrote that because a client had a bunch of existing nacl messages that were signed using Python, but the existing Go library uses a different protocol to sign messages than the standard Python library. The existing Go library also didn't support all of the API's supported by nacl, I figured if I was running into this, then other people would too. Clearly based on the number of stars it seems like a lot of people _are_ finding it useful.

I guess in your eyes I should have also done the cryptography, however, I am not a cryptographer or a mathematician and one of the first things that you learn when you start doing work with cryptography is that you shouldn't roll your own crypto.

I decided to make that library prominent because in my consulting practice I saw a lot of clients using cryptographic primitives that were clunky and/or had a lot more overhead, for things like cookies or public key authentication or just sharing messages. nacl is difficult to use incorrectly, and is fast and efficient in terms of overhead. I wanted to promote use of nacl more than the work that I was doing for it in particular.

For that client (a smart lock company), I rewrote the backend, that someone else wrote in C for a specification that did not match the needs of the business. The C software was extremely difficult to read and maintain - socket writes in a callback in one part of the code and socket reads in a completely different part of the code, shelling out to curl, simple Mongo queries that would take 50 lines to set up. As a result the engineering team could hardly make any progress deploying new features. I ended up rewriting the whole backend in Go, a few thousand lines of understanding what the C code was doing, and porting it, to the point where the team could actually release patches and new features on a regular cadence, and figure out what on earth was going on with the Mongo queries and shell-to-curl.

That's not public though, if you're looking for public work, you could look at Logrole (github.com/kevinburke/logrole), a HTML client for your Twilio call, SMS, phone number, and recording data. Of course, you could say "that's just a regurgitation of whoever did the API client", which is true-ish, but I also wrote the API client (github.com/kevinburke/twilio-go). Of course, you could say "that's just a regurgitation of the Twilio API," but I also helped build and maintain the Twilio API, as well as the documentation and information architecture (https://www.youtube.com/watch?v=sQP_hUNCrcE), and the client libraries (https://www.youtube.com/watch?v=C_UJHqR_2Mo).

Most recently I was hired as the first engineer at Meter (meter.com) where I built out the entire backend API, the deployment infrastructure, the CI/CD infrastructure, a pipeline for the in-the-field servers to update themselves, and a method for access points to retrieve configuration from the backend. All in all this was probably about 30-50,000 lines of code over two years. I think the API has had one customer facing error in two years and no downtime.

It is true that anyone can call themselves "a software engineer" but not everyone can get contracts for a sole member consultancy and, crucially, get their contract renewed multiple times at every single client. If I was selling snake oil and not delivering anything, that would not have happened.

Re:Ten years of experience, still failing phone screens by redis_mlc on Friday December 10, 2021 @09:26PM (#29517848)
> This post ought to be the final nail on the coffin of the cult of leetcode/whiteboard style inverviewing.

Looks like he has ADHD. Maybe somebody with more time can go through his blog post line-by-line and figure out what's going on.

Most of my Coderpad stuff compiles and runs the first time, so I don't use his incremental test method, or see a need for it. Maybe he learned programming on heavy-weight IDEs and got trapped mentally in those?

Re:Ten years of experience, still failing phone screens by vanusa on Friday December 10, 2021 @10:00PM (#29518007)
Looks like he has ADHD.

That sounds ad-hominem. I found the post perfectly readable.

Maybe he learned programming on heavy-weight IDEs and got trapped mentally in those?

Maybe he just thinks differently than you do? His body of work is not suggestive of someone "trapped" in an IDE or other dysfunctional midset.

Re:Ten years of experience, still failing phone screens by willcipriano on Friday December 10, 2021 @10:11PM (#29518057)
I generally write some naïve code and if it doesn't work, get out the debugger and fix it from there. I can work a lot faster when everything is laid out and I don't have to guess about what the data structures are going to look like. If it's performance sensitive like some tests I've seen, I'd use a profiler. I often use the jetbrains find and replace tool, as well as the search tool, I also like that I can click into the source code for libraries that I use, so I don't have to guess about the interface or implementation. Stuff like coderpad takes away a good portion of my tools that I would use day to day, I taught myself to code in notepad, but I purchased the full suite of jetbrains tools years ago so I wouldn't have to fumble around with inferior tools.
Re:Ten years of experience, still failing phone screens by google234123 on Saturday December 11, 2021 @01:19AM (#29518921)
A profile can’t suggest a better algorithm.
Re:Ten years of experience, still failing phone screens by nitrogen on Saturday December 11, 2021 @09:17AM (#29521001)
A profiler will tell you whether a O(n log n) algorithm with a very high constant factor is better or worse for your situation than an O(n²) algorithm with a very low constant.
Re:Ten years of experience, still failing phone screens by GoOnThenDoTell on Saturday December 11, 2021 @03:20AM (#29519415)
and a better algorithm can often be over-engineering, so it needs context in the question-giving
Re:Ten years of experience, still failing phone screens by kevinburke on Friday December 10, 2021 @09:59PM (#29518003)
I use Vim, it's just different learning and development styles, I think.

I’m very capable of focusing when there is a lot of money on the line.

Re:Ten years of experience, still failing phone screens by zaptheimpaler on Friday December 10, 2021 @11:26PM (#29518417)
Maybe you're trapped in mentally simulating a compiler and those of us with good dev setups can dedicate brainpower to other concerns?
Re:Ten years of experience, still failing phone screens by wiseowise on Saturday December 11, 2021 @02:03AM (#29519109)
It's the other way around, from my experience. People who can write a program without any setup can solve it even on paper, while people that are hardwired to specific setup or IDE quickly froze when you ask them for something.
Re:Ten years of experience, still failing phone screens by sofixa on Saturday December 11, 2021 @03:10AM (#29519373)
> People who can write a program without any setup can solve it even on paper,

As someone who had courses in C on paper, i can only say that it's a colossal waste of time. Tooling exists to make lives easier, gain time and productivity, why avoid it?

It'd be like saying only the farmer who can do everything by hand without any tools increasing their productivity is a real one. Or an accountant refusing to use Excel/calcuators/ERPs and writing everything on paper.

And before anyone jumps to conclusions, i often write small scripts with vim with a minimal setup, but when I'm doing anything complex i prefer to use an IDE

Re:Ten years of experience, still failing phone screens by wiseowise on Saturday December 11, 2021 @04:20AM (#29519636)
> It'd be like saying only the farmer who can do everything by hand without any tools increasing their productivity is a real one. Or an accountant refusing to use Excel/calcuators/ERPs and writing everything on paper.

You're trying to map manual work onto engineering.

And absolutely I'd rather work with accountnant who can write me on paper without Excel/calculator/ERP his logic.

It's like you're being obtuse just for the sake of the argument. Someone who can clearly express themselves without specific medium, be it paper, IDE or whatever is strictly superior to someone who is tied to one specific medium.

Re:Ten years of experience, still failing phone screens by sofixa on Saturday December 11, 2021 @04:36AM (#29519710)
When one of the mediums actively helps and avoids small human errors, I'd prefer the person knowing using it instead of sticking an old and imperfect method out of pride.
Re:Ten years of experience, still failing phone screens by wiseowise on Saturday December 11, 2021 @06:08AM (#29520041)
> When one of the mediums actively helps and avoids small human errors

How does it actively helps and avoids small human errors in reasoning.

> I'd prefer the person knowing using it instead of sticking an old and imperfect method out of pride.

What does even pride have to do with this?

Re:Ten years of experience, still failing phone screens by sofixa on Sunday December 12, 2021 @10:16AM (#29530240)
> How does it actively helps and avoids small human errors in reasoning.

Because reasoning is only a part of everything to be done. An IDE can help with typos, best practices ( global variables, lack of error checking, etc) which are tedious things that take time. Isn't it better to the things that matter instead?

Re:Ten years of experience, still failing phone screens by wiseowise on Monday December 13, 2021 @02:39PM (#29543505)
> An IDE can help with typos, best practices ( global variables, lack of error checking, etc) which are tedious things that take time.

Which applies to everyone? Take IDE out of equation and what do you have?

Re:Ten years of experience, still failing phone screens by spoils19 on Saturday December 11, 2021 @03:38AM (#29519480)
It's a good thing we're not building solutions for business problems on paper then.
Re:Ten years of experience, still failing phone screens by duxup on Friday December 10, 2021 @10:14PM (#29518066)
His description of how he works sounds heavy weight…by his own design to work efficiently. That’s a good thing.
Re:Ten years of experience, still failing phone screens by EdwardDiego on Friday December 10, 2021 @10:23PM (#29518117)
A lot of devs have ADHD.
Re:Ten years of experience, still failing phone screens by Kye on Friday December 10, 2021 @11:24PM (#29518411)
Re:Ten years of experience, still failing phone screens by MrStonedOne on Friday December 10, 2021 @09:57PM (#29517997)
So a screening system that only allows devs with your writing style in is valid why?

I'm just like them, only my ide is notepad++.

My code never compiles on first attempt, and never runs correctly on the first attempt.

Re:Ten years of experience, still failing phone screens by disgruntledphd2 on Saturday December 11, 2021 @08:09AM (#29520612)
If my code compiles and runs correctly the first time, I spend an inordinate amount of time looking for bugs in it ;)