I used to believe this but after my most recent position I no longer do.
A lot of the developers there didn't code outside of work hours, or if they did it was just using the same technologies as the day to day.
When asked what tools we could use to filter for higher quality candidates in open roles I responded:
> Ask them to show you a personal project they're proud of, that will tell if they have any passion for the job.
Maybe it was just the company not being very attractive to talented coders, but after some time of candidates having nothing to show the company gave up and outsourced.
There are simply a lot of uninspired developers who are just in it for the money now.
Maybe some kind of confirmation bias / no true scotsman argument, but if I got that question during an interview my response would be something like
> There are simply a lot of uninspired developers who are just in it for the money now.
Personally I am happy that the industry is maturing to the point where people can just enter it as a career and not a ~~passion~~
This mentality that software devs should have loaded up github repos with side projects and live & breath code all the time is super toxic for the industry.
By the way there are plenty of talented coders who only code at work.
And there are likely plenty of hacks who code all the time, but never learned how to code well, or work with a team or understand how to scale a project or any host of other skills that are necessary for building commercial products.
> but after some time of candidates having nothing to show the company gave up and outsourced. There are simply a lot of uninspired developers who are just in it for the money now.
Or it could be that they really do like making software but they have other hobbies they enjoy much more.
> competitor can't afford to keep buying you out forever
Not saying this is in fact the case, but with trillions of dollars of QE and the Cantillon effect it seems entirely possible that in some industries they could.
There are also some words derived from French but pronounced in a very non-French manner. The t in valet should be fully pronounced. Making the word sound French is a non-U hypercorrection.
> Making the word sound French is a non-U hypercorrection.
I disagree that pronouncing it "VALLay" is hypercorrection. Proper French pronunciation would be "vallAY" (with the emphasis on the second syllable).
At any rate, my language background is upper-middle-class English English, and nobody pronounced the word "valitt". That's an americanism, as far as I'm concerned. As a consequence, I've always struggled with the word when used to mean cleaning e.g. a car interior.
FWIW, I understand that the "U and non-U" thing was meant as a joke, was horribly snobbish, and was anchored in a particular stratum of early 20th-C English society.
It's baffling to me how many "senior web developers" don't have their CV hosted on a website. Regardless of whether it's plain HTML on a CDN or a hectic fully 3d WebGL demo, a senior dev should have a domain with a https secured connection expressly for showing that they can in fact deploy and maintain a production instance.
The recruiter needs a PDF?
Have a version linked to at the top of the document, or let them know that they can just press CTRL+P and your beautiful hand crafted css media queries will lay out an equivalent copy ready to be printed.
Like a lot of the other comments here, a LaTeX resume signals to me that the applicant probably spends more time code-golfing than implementing practical solutions.
> spends more time code-golfing than implementing practical solutions.
Code golfing is a too-frequent requirement for interviews.
Many companies seem happy to miss out on the senior developers who avoid interview requirements to write code to do a fiddly string manipulation test within 2 minutes.
>Regardless of whether it's plain HTML on a CDN or a hectic fully 3d WebGL demo, a senior dev should have a domain with a https secured connection expressly for showing that they can in fact deploy and maintain a production instance.
I just don't think this really tells you anything meaningful. At least not with any certainty. I can setup a site on GitHub pages and push to main and that's all I need to do. Virtually no skill is needed to even do this.
> Like a lot of the other comments here, a LaTeX resume signals to me that the applicant probably spends more time code-golfing than implementing practical solutions.
Do you usually decompile pdfs to find traces of LaTeX to fuel your meaningless spite?
what do the actual rules of the road say the braking point should be for an 8 person minivan with 5 passengers in dry weather?
what about 8 passengers in the wet at night with ice on the roads?
old argument i know, but if a human gets that wrong and plows a pedestrian they wear the consequences, will an auto manufacturer do the same?
my guess is no, and the result of that is that even if we can get a majority of cars to be self driving they are probably not going to be pushing the limits of road capacity any time soon like GP suggests, more likely they will continue to drive super conservatively and fail fast like the videos in the linked article.
you are 30 minutes from home for a 15 minute appointment and do not like waiting for your car.
do you:
- send the car home
no, it would only get halfway home before the end of your appointment
- send it on a rideshare journey
let's say (conservatively, and according to some minimum regulations from the rideshare service) it gets assigned a job after 5 minutes to drive somebody 10 minutes away. it finishes its job at the same time as your appointment ends. you have to wait 10 minutes for it to return to you. again no.
- send it to a parking lot
assuming the parking lot is 5 minutes away and you can tell it to return 5m before your appointment ends this seems reasonable
- drive circles around your appointment
all the benefits of sending it to the parking lot but requires even less effort as you no longer have to remember to tell it your appointment is finishing.
now apply this logic to the general public. what is the most likely outcome?
Exactly. People are already occupying public resources for their private luxury (in the form of parking on public street in front of their house), nobody would think twice just letting the thing circle. Especially in places where parking costs money, which will then only be a thing for people who can't afford self-driving add-ons or need to charge the thing.
> Further analysis of these 15 reports indicated that a two-hour exposure to blue light (460 nm) in the evening suppresses melatonin, the maximum melatonin-suppressing effect being achieved at the shortest wavelengths (424 nm, violet)
> The melatonin concentration recovered rather rapidly, within 15 min from cessation of the exposure, suggesting a short-term or simultaneous impact of light exposure on the melatonin secretion.
I used to believe this but after my most recent position I no longer do. A lot of the developers there didn't code outside of work hours, or if they did it was just using the same technologies as the day to day.
When asked what tools we could use to filter for higher quality candidates in open roles I responded:
> Ask them to show you a personal project they're proud of, that will tell if they have any passion for the job.
Maybe it was just the company not being very attractive to talented coders, but after some time of candidates having nothing to show the company gave up and outsourced. There are simply a lot of uninspired developers who are just in it for the money now.
Maybe some kind of confirmation bias / no true scotsman argument, but if I got that question during an interview my response would be something like
> Which one would you like to hear about first?