Was really hoping an article titled 'the greatest resume I've ever seen' would show me the resume... darn
It's linked in the post! https://dsresume.com
whoops! my bad. Good eye and thank you
The greatest resume I've ever seen
21–30 of 157 posts
Re: The greatest resume I've ever seen
#22> His reasoning: "Wherever sewer odor can get in, so can smoke … except we can see smoke with a flashlight." Anyone else get the urge to build a smell detector machine with an arduino or rpi?
Not at all. Not everything needs a digital solution.
Not all things are made because they need to be made. But then those things can be adapted to solve a problem someone needs solved.
Re: The greatest resume I've ever seen
#23Interviewer - "That's impressive Daniel. Now can you invert a binary tree on the whiteboard?"
[deleted]
Re: The greatest resume I've ever seen
#24So... smart and gets things done. Honestly that's all I look for on a resume. You also have to talk about it in an interview. I couldn't care less if you can invert a binary tree. One of the greatest developers I've ever worked with, I hired straight out of college. He graduated with an electrical engineering degree but his senior year he took a course in Java and liked it and decided to be a programmer. Couldn't tel…
[deleted]
Re: The greatest resume I've ever seen
#25> He didn't know he was drawing a cloud architecture diagram.
No, cloud architects don’t know they’re drawing engineered prints.
Re: The greatest resume I've ever seen
#26It’s come full circle. I’ve often heard people (working developers) say over the years that software engineers are basically just digital plumbers. And the job often feels that way. Now we have proof that the skills do in fact overlap quite a bit with plumbing.
> digital plumbers.
I had this realization over last one year, after 17 years of professional life.
Most of my work these days involves plumbing together right libraries and data pipelines to automate business processes. Sometimes I need to fix an existing plumbing to plug a leak here and there.
Now my Twitter handle says Plumber
Re: The greatest resume I've ever seen
#27This is so heavily editorialized. No mention of how he actually learnt to program. But they did smear some stuff on his face before taking that photo.
they need to sell those 49$ books somehow.
Re: The greatest resume I've ever seen
#28"Until I met Daniel, I actually didn't know that "smoke testing" was a term with a literal smoke-related meaning. I'd always heard it used in the context of software tests. Daniel used a tracing technique to follow a problem to its source, instead of just making random guesses."
I've always known "smoke testing" to refer to the mythical magic smoke that makes all electronics work. Smoke testing is turning something on for the first time to see if you're going to let the magic smoke out.
Re: The greatest resume I've ever seen
#29Interviewer - "That's impressive Daniel. Now can you invert a binary tree on the whiteboard?"
Recently I went through a phone screen by a gentleman I imagine to be in his 50s or 60s and it was an immensely pleasant experience. No gotcha questions and any time I mentioned how his problem reminded me of so-and-so tech he would gush in excitement that he also worked in that tech
Compare to a recent interview with the world's best employer (tm): the interviewer was young, was upset that my solution wasn't written in Java (???), and when I described my experience I talked about dashboards and he didn't know what that was. I described it as charts and he didn't know what that was. I described it as graphs and he also didn't know what that was. The interviewer had a bit of an accent so maybe it was a language issue but I had never run into someone who hasn't heard of a chart!
Re: The greatest resume I've ever seen
#30I've seen carpenters at work. I'm not a carpenter myself. Whenever a carpenter would explain their thought process to me it felt like two things: * I don't understand their technical terms. * The way they explain their thought process when something goes wrong, feels very much like software engineers fixing a bug. There are differences but this, to me, was the most striking similarity.
Problem solving is problem solving