The greatest resume I've ever seen

https://cloudirregular.substack.com/p/the-greatest-resume-ive-ever-seen

by forrestbrazeal • 5 years ago

155 145 5 years ago

cloudirregular.substack.com

zohvek2• 5 years ago

Was really hoping an article titled 'the greatest resume I've ever seen' would show me the resume... darn

forrestbrazeal2• 5 years ago

It's linked in the post! https://dsresume.com

zohvek2• 5 years ago

whoops! my bad. Good eye and thank you

mnw21cam• 5 years ago

In fact, it doesn't look like anything is being resumed at all. He's switching to a different job sector, not resuming the old one.

jacurtis• 5 years ago

This might be a confusion around a cultural translation. "The Greatest Resume I've Ever Seen" is referring to an American "Resume" which is what we call our CV (Curriculum Vitae). In the US we use the word "Resume" to describe this 1-2 page document that outlines our skills, job history, and qualifications in order to apply for a job.

So for example in the post, this is the Resume/CV that they are referring to: https://dsresume.com/

So it isn't referencing the verb "to resume", but is instead referencing the noun "Resume", which is an American colloquialism for a CV, which is to be a piece of literature to describe qualifications for a job.

While I am American, i lived in France and England for a while and over there, the term "Resume" was completely foreign, but CV was something everyone understood. So that is why I thought I would shine light on this.

(Unless maybe you were meaning to make a joke, sorry I took the question literally)

jb1991• 5 years ago

It’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.

vishnugupta• 5 years ago

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

darkteflon• 5 years ago

I’ve always liked Joel Spolsky’s “duct-tape programmer”.

tlarkworthy• 5 years ago

There is subversive power in choosing what to connect

josefresco• 5 years ago

My old boss (web development) said in 2003ish that "we're just plumbers" and at the time (I was young) it offended me as I thought as "technologists" we were "special". When I went out on my own, I realized he was right.

HPsquared• 5 years ago

Plumbers are technologists as well, really. Just a different kind of technology...

biggieshellz• 5 years ago

I mean, we have a Linux Plumbers Conference for a reason. The kernel is digital infrastructure.

908B64B197• 5 years ago

I agree with plumbing.

But not residential. That's all pretty standardized.

Think industrial, or a nuclear power plant. Or a spacecraft. Something where everything had to be custom designed.

sleepysysadmin2• 5 years ago

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?

dhosek• 5 years ago

Not at all. Not everything needs a digital solution.

sleepysysadmin2• 5 years ago

Not at all. Not everything needs a digital solution.

Fair enough.

datameta2• 5 years ago

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.

datameta2• 5 years ago

Embedded ML smell detector: https://www.inputmag.com/tech/this-ai-nose-will-help-you-sni...

monster_group• 5 years ago

Interviewer - "That's impressive Daniel. Now can you invert a binary tree on the whiteboard?"

arenaninja• 5 years ago

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!

vxNsr2• 5 years ago

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!

It’s at this point that I would end the interview and let them know it doesn’t feel like it would be a good fit.

moron4hire8• 5 years ago

Jesus christ.

Inverting a binary tree is not hard. That people keep using this as a joke is more a testament to the stubbornness of people believing they shouldn't have to do no learnin' no more than it is bad interviewing practices.

mcntsh4• 5 years ago

shouldn't have to do no learnin'

Expecting engineers to develop skills they don't learn/use in their actual professions to prove they're capable of working a job makes no sense. If these leetcode puzzles were actually relevant, why do so many engineers have to spend time outside of work "grinding" in order to get better at them?

approxim8ion• 5 years ago

The difficulty isn't the point. Your ability to invert a binary tree has very, very little to do with you writing CRUD applications.

recursive3• 5 years ago

Wait, inverting a tree is a real thing? What does that even mean? All the terminal leaf nodes become roots? That can't be right. I thought part of the joke was that it was impossible.

andrei_says_• 5 years ago

I’ve never in my 10+ year career needed to invert a binary tree.

stephenhuey2• 5 years ago

Neither is counting on your fingers in binary, but would you time someone on that with a stopwatch if they would never use such a party trick during the course of a job in your company? Or perhaps we should just test their Spanish pronunciation since that would be about as relevant as inverting binary trees for any position I’ve held in 2 decades of software jobs (I’ve almost done consulting in Latin America which means my Spanish skills would be even more relevant for solving technology problems than inverting binary trees—at least for me).

NikolaeVarius• 5 years ago

The amount of time people spend complaining about solving trivial problems would be better spent studying for those problems in the first place.

If you literally know what questions are being asked in a test, you should probably fucking just learn it an move on.

snarf21• 5 years ago

I think the issue is that the interviewee doesn't always know what is on the "test". It is also a waste of everyone's time. If a company's only data store is SQL of some kind, which do you want: Someone who can barely do joins but has memorized red/black tree function implementations in several languages or some one who knows SQL at a production level and if they had to do something with red/black trees would just have to spend a day or two re-reading how they work? I think the thing this underscores is that we really need an association like the "bar". So you can go study all the things on the test and prove you have the knowledge and ability and then skip that as part of hiring and just focus on experience. The only thing we have today is tech company specific certification which is okay for certain things but not for more general software needs.

irateswami• 5 years ago

"If you know the volume of a toilet bowl 1.3 gallons, how many radii of the earth's rotation would fill the visible universe" - Google interviewer

user_named2• 5 years ago

This 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.

engmgrmgr• 5 years ago

It’s a small sample size, but highly motivated self taught folks who come from tough blue collar careers that I’ve seen have been pretty reliable and committed.

I presume it’s a lot easier to appreciate the working conditions and compensation package, as well as tolerate the political dramas, when you have some perspective on how life is for most other people.

wpietri4• 5 years ago

For sure. My summer jobs were in restaurants and factories. It deeply shaped my notion of what work is. It's been a long time, and I'm still excited I get to work from my house basically solving puzzles.

It has downsides, though. One thing you learn in blue-collar businesses is that the direct work is primary, with other stuff secondary. In a restaurant, nobody shuts down during the lunch rush to talk with everybody. In a factory, everybody understands that the machines keep going; any administration is done very much on the margins.

So it's maddening to me that in most office contexts, my schedule fills up with meetings and I'm expected to get my work done around them. And that nobody sees that as a problem, because that's just office culture.

sdoering4• 5 years ago

Oh wow. Thanks for the distinction. This cleared up something for me that was knocking in the back of my mind.

I had the same feeling having had a lot of blue collar jobs while studying. Discussions/management was scheduled around getting work done.

I was working as a cook once and the real chef (I was studying literature and history at that time) and I were doing reviews of the evening after the kitchen was closed, cleaned and we were sitting at the bar drinking our one final drink of the evening. It was a little bit like a sprint review with the sprint being just an evening long. Sprint planning so to speak happened before guests arrived and the restaurant opened.

We prepared the kitchen, chopped stuff for salads, prepared sauces and stuff and were discussing who would do what when the rush started. So even without knowing the actual ordering of dishes and the amount of every specific dish we roughly knew what to expect (how many orders aka tickets we would have in the sprint/evening).

So we had a sprint planning, a sprint and a (internal) review. And our service people would give us feedback on what went well and what went wrong also, because they had the direct guest feedback.

vxNsr2• 5 years ago

So it's maddening to me that in most office contexts, my schedule fills up with meetings and I'm expected to get my work done around them. And that nobody sees that as a problem, because that's just office culture.

Block out portions of your calendar with recurring work time, and let them schedule their meetings around that.

wpietri4• 5 years ago

This is great. Occasionally I wonder what I'd be doing if I weren't a software developer. I suspect I'd be a mediocre car mechanic. I'd be great at the weird and interesting problems, but bored to tears by the standard, unchallenging work. And crabby about it, of course.

riekus• 5 years ago

That was exactly me as a car mechanic, finding the problem that no one couldn't find? Awesome, but even doing the work to fix it after diagnosed it was boring for me, not to mention the thousands of tire changes, oil changes... So boring.

Sold everything and travelled for 4 years where I worked on projects of my own (programming) and being self taught I planned to be a programmer when I came back (now) but thinking about it... I don't think I would like the day to day work, typing code like a monkey on the que of a superior, it honestly feels like programmers are the new factory workers of the industrial revolution.

Also doesn't help that I am in the Netherlands, where it isn't paid as exceptional as in the US, it maybe would make it bearable.

My big problem now, what am I going to do...

askonomm• 5 years ago

I recommend joining a smaller company or start-up, that way you have plenty of interesting things to work on, and won't be bogged down to being a "code monkey", as you can influence architectural decisions, and so on. It's the bigger companies with a very routine "process" that usually makes you feel like a line worker.

wpietri4• 5 years ago

Plenty of dev jobs are as you describe, but not all of them!

For example, right now I'm working for a non-profit. Meaningful work, smart colleagues, and a fair bit of agency. It doesn't pay as well as a fancy tech company, but I get by.

You should also check out groups that are more niche. For example, a friend of mine is part of the Copenhagen user group for Extreme Programming. That's a method that's focused on a good developer experience. And in my experience, niche methods and languages tend to be used more at non-awful companies.

So stay away from the big, boring companies, or at least the boring parts of them. Look for small, independent groups with clear purposes and close connections to the users.

mettamage• 5 years ago

I'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.

packetlost• 5 years ago

Problem solving is problem solving

stuff4ben6• 5 years ago

So... 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 tell me the first thing about programming but I could tell he had the chops to figure things out and that he had a passion for things getting done.

sdoering4• 5 years ago

I just came of a call with a a potential hire. I recommended her to a second round because of three things:

* She would culturally fit while still bringing something new to the tam * She doesn't know Web Analytics, but has done market research, built html prototypes and has basic knowledge in JS, python, html, SPSS and some other things * She is self motivated and shows this because she actually learned all these skills in her last job because she wanted to and it made her job more easy.

I strongly believe she would learn the technical ins and outs of Google Analytics or Adobe Analytics quite fast. The rest is not important.

I don't care that she has not worked with AA oder GA. If it were my decision I would have hired her on the spot.

stuff4ben6• 5 years ago

The self-motivation aspect you mentioned is also critical. It's these soft questions that reveal so much about a person's character that speak to me as much as or sometimes greater than certifications or degrees do.

It's also why resume screening done by HR drones or worse, AI, are so problematic. Unless I need someone to do an exact thing extremely fast, I'd much prefer a generalist with a sharp mind, proven "gets shit done" attitude and experience, and is motivated to do the right thing.

jasonpeacock• 5 years ago

She would culturally fit

What does this mean? This is a very loaded term, and without qualitative data it results in biased hiring.

Usually, it means "she's young, white, and college educated, just like the rest of us".

People don't need to culturally fit to excel at a role.

strgcmc• 5 years ago

The trouble is, this "je ne sais quoi" that you speak of, that you "could tell he had the chops to figure things out", is unquantifiable and almost totally subjective. To be a bit blunt and cynical, this way of evaluating candidates basically boils down to, "do I like this candidate?" Your criteria for liking someone happens to be that you look for these nebulous "chops for figuring things out". What about the other interviewers at your company? What kind of stuff would they like? Would they evaluate "chops" the same way you do?

Or, just imagine that you're interviewing a hypothetically equivalent candidate who also had the same drive and "chops to figure things out", but who happened to be less fluent in conversational English. Are you so sure that you'd be able to pick up on the same underlying "signal" about their chops, if it was obscured by some language fluency noise?

Hiring is a Hard Problem, and there's a big gap between well-intentioned intuition and translating that into robust processes.

wbsss4412• 5 years ago

There is something to be said about the value of human intuition, though. While it may be fallible, part of what makes hiring a hard problem is that many of the things that distinguish good candidates just aren’t objectively measurable.

Rd6n6• 5 years ago

unquantifiable and almost totally subjective

That’s what intuition and judgment calls are for.

What does your intuition say is a good way to approach hiring? Does it maybe tell you to figure out relevant skills and ask the candidate about those? Yet if you ignore that voice, you end up timing how long it takes them to invert binary trees from memory instead

Everybody on earth who is good at what they do relies utterly on their carefully trained intuition

stuff4ben6• 5 years ago

oh no doubt, getting around implicit bias and all that is hard and is training I've been through and try not to let get in the way. I've interviewed hundreds of people over the course of my career and I've had the greatest success in evaluating the soft skills of an engineer rather than their stated resume skills. For experienced engineers, I still ask technical questions to make sure they're not BSing their way in and have some knowledge of development. But college grads I really want someone with those soft skills.

Yes, it is slightly subjective, but not unquantifiable. You have to have shown me times you've done those things, not just say them.

Kranar4• 5 years ago

Exactly, it's so sad hearing someone not realize that their hiring process is basically discriminatory in nature. Can you tell someone had the chops to figure things out if they came from a different cultural background than one you're familiar with? If they had a different social upbringing from yours? If they presented themselves in a way that you personally misunderstood but someone else would have been completely comfortable with?

Of course not, OP basically hired someone he got along with, and that's fine on a small scale, but it's not something to pride oneself over.

A better approach in my opinion is if you find someone who you get along with, you think they have that kind of fire and passion you're looking for, but they don't know the basics and fundamentals of computer science nor are they familiar with data structures and algorithms, you advise them that if they want to make the most of their potential then they should take some minimal amount of time to really devote themselves to understanding those aspects and then they can reapply for the position at a later date. You can keep in touch with them, even potentially mentor them if you really think they are worth it, but you don't just give someone a pass.

Letting someone get by without that knowledge because you like them doesn't really do anyone any favors.

crispyambulance2• 5 years ago

Hiring is a Hard Problem, and there's a big gap between well-intentioned intuition and translating that into robust processes.

Ultimately, hiring is INTRINSICALLY a subjective process. If it were quantifiable and one could reliably screen based on "objective" criteria, it would have been a solved problem by now and employers could hire "robustly". But it is not and it never will be that way.

That said, hiring and assessing talent takes practice and there are some techniques that work better than others. In particular, behavioral techniques are extremely valuable and sadly often take a back seat to persnickety homework quiz questions. It takes some skill and practice to get good at behavioral interviews (for both parties). But when it's used properly, the candidate has a chance to actually demonstrate "chops" even though they may lack some of the job requirements.

wvenable• 5 years ago

This mysterious robust process that can deterministically fit humans into the "hire" and "no hire" box doesn't exist. Everything you can describe that's negative about human intuition, I can use to describe whatever robust process you can think of.

I want candidates to succeed -- I always start out rooting for them. The interview is not a place to beat people down but it give them opportunities to show their strengths.

Consultant324522• 5 years ago

I've been responsible for hiring for most of the last 20 years. I've literally never had a false positive where I recommended someone and they performed poorly. I have had one case where I said no, was overruled, and then the person turned out to be awful. To be fair, I have no idea how many false negatives I've had where I said no but they would've been great.

I'm always puzzled by people/companies who find this difficult. I don't believe for a second that my intuition is magical. I have a very simple interview process and it works really well. I just ask you what you did, and then I keep asking you increasingly more complex or detailed questions about what you said you did until one of us hits our boundary of knowledge. Then I ask a couple of social questions, usually in the form of "Have you ever dealt with x kind of situation?"

Funny anecdote, I asked one guy if he'd ever had a coworker he had personal issues with. He told me some guy made a racist comment and his response was to ask the guy to step outside to fight. We did not hire that guy.

koonsolo2• 5 years ago

I hired a lot of very good developers, so I was able to rely on my intuition pretty well.

Then one time I hired an excellent candidate, technically very strong. Then it turned out he couldn't figure things out on his own. I had a co-interviewer who also thought he was very strong. In the end we had to fire him after a month since he couldn't pick up the pace (his colleague who started at the same time is actually very good)

I was "very good at hiring", until I hired the wrong person. Even now it's hard for me to tell what actually went wrong there. It was mostly theory and understanding underlying concepts, but now I definitely mix in a lot of practical issues and examples. Sometimes I think we interviewed his twin brother who could actually program ;).

Hiring developers is indeed very difficult. You can only tell when working with them for a few weeks.

bryanrasmussen3• 5 years ago

So... smart and gets things done.

So... young and has no family or other important time-consuming commitments. That's what we're looking for!

stuff4ben6• 5 years ago

So by your reckoning, old people with families and a life outside of work are... stupid and don't do anything? Are you serious? Being smart and showing you have great motivation to get things done in NO WAY relates to how old you are, if you have a family, or a life outside of work.

staysafeanon• 5 years ago

I'm old, have two kids, have other time consuming commitments and I get things done.

Part of being smart and getting things done is properly managing work/life balance.

bryanrasmussen3• 5 years ago

as it is past the edit window I suppose I will just note that the above was in reference to the quote from the article

Over the weeks that followed, Daniel forced himself to sit down at his computer after those 11-hour days. He grappled with Python and Javascript in the back of his work truck. One minute he was wrangling sewer pipelines - the next minute, CI/CD pipelines.

so the guy was able to work 11 hour days and learn to program, two programming languages, to take part in this contest, and his code was evidently solid as well so - I have to assume he did at least 4 hours a day after the 11 hour work days, and then of course the weekends.

Evidently people thought I meant that only young people can be smart and get things done, which I can only think that misunderstanding arose from not having read the article. Because even if I agreed that smart and gets things done was the answer if someone pointed out young and has no family I would immediately think oh yeah, he was definitely pulling some 15 hour days there without distractions.

kcplate• 5 years ago

Frankly I’m not surprised at all that a plumber that is an effective troubleshooter could port that skill to the digital realm in a short period. Being an adept troubleshooter is pretty much the top requirement for the trade (that and a strong resistance to malodorous work environments).

I’d have been much more impressed and surprised to read an article profiling a programmer that became an effective plumber in the same amount of time.

Yep, I’m saying it—y’all just ain’t as smart as the plumbers out there…and most of you are kind of…”soft” in the physical department and probably would run screaming from the physical demands of the gig.

(I am including myself in the negative assessment above)

jeffrallen• 5 years ago

One minute he was wrangling sewer pipelines - the next minute, CI/CD pipelines

I've seen CI/CD configs where you couldn't tell the difference! :)

t-writescode• 5 years ago

Hey now, that’s an insult to indoor plumbing xD

I wish some CI/CD pipelines were as good as sewers

drcode• 5 years ago

The best college application is still from Clyde Tombaugh, who was able to put in "discovered Pluto" when he applied.

Imnimo• 5 years ago

Best grad school application is maybe John Nash. His recommendation later just said that "he is a mathematical genius".

ableal2• 5 years ago

I heard that Sakharov (https://en.wikipedia.org/wiki/Andrei_Sakharov ) just used two lines:

- Hero of the Soviet Union

- Nobel Prize

mosselman• 5 years ago

I think I'll do that as well next time I apply for a job. See where it lands me. If they actually check if I've won a Nobel Prize and find out I haven't, I'll just call it a career hack, that should resonate enough in today's world.

The meanings "Hero" and "Soviet Union" are both up for discussion, so I think I could bluf my way into being believed about that part at least.

taneq• 5 years ago

He didn't know he was drawing a cloud architecture diagram.

No, cloud architects don’t know they’re drawing engineered prints.

JshWright2• 5 years ago

"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.

mattnewton• 5 years ago

This- I knew the electrical sense that early software engineers working on hobby computers probably got it from, where it refers to wiring something up, plugging it in for the first time and seeing if it lights on fire / creates smoke.

I guess there is a dual origin though

https://medium.com/@AikoPath/about-the-origin-of-smoke-testi...

AnIdiotOnTheNet• 5 years ago

That reminds me of a story[0] my digital electronics instructor once told me. He was on a team working on satellite[1] electronics and had the whole thing laid out on breadboard. It wasn't working, and they suspected it was a short, but with so many connections everywhere it would take forever to find. So they decided to crank up the input current until the short started burning and locate it that way. It apparently didn't cause anything to smoke, but eventually someone did notice the orange-hot wire that was causing the problem.

[0] I have a terrible memory so details may be incorrect.

[1] IIRC this guy had worked on geostar satellites and the hubble, but I'm not sure if this story was about either.

madflame991• 5 years ago

Tangential-ish:

I used to live in a place where we had gas resources and gas stoves. Gas pipes would be painted yellow to stand out and people always had some sort of respect and caution around them - you don't mess with gas pipes - I learned that as a kid. At the slightest whif of gas people would light up a match or a lighter and run it along the pipe to check for leaks - I always thought this is what "smoke testing" meant (altho there would't be any smoke). I still don't know if this is safe or would even work or it's just something people did and keep doing... and I have no gas pipes around me anymore.

Forbo• 5 years ago

I remember watching my grandfather spit on pipes to find the source of a leak. It was viscous enough that it would bubble up. Taking flame to a gas pipe sounds absolutely terrifying.

asmos7• 5 years ago

for the love of god if you smell gas please don't light a match to check. Real quick way to blow your house up if you do have a gas leak.

JasonFruit• 5 years ago

Use soapy water instead and watch for bubbles. Less exciting but much safer.

spiketom• 5 years ago

At the slightest whif of gas people would light up a match or a lighter and run it along the pipe to check for leaks

What is this? Some kind of Tom & Jerry show? Light a match near a leaking gas pipe and BOOOM!!!

throwaway5752• 5 years ago

It even pre-dates plumbing - https://en.wikipedia.org/wiki/Smoke_testing_(mechanical) is a good overview.

bradleysmith• 5 years ago

I've also heard 'smoke testing' refer to sending power to a device or component to see if any magic smoke comes out.

But... I've also seen smoke testing used in automotive and engine diagnostics which could predate or parallel this usage in electronics.

https://mechanics.stackexchange.com/questions/26749/what-is-...

I should imagine this method of troubleshooting sealed hollow-body systems of any kind have been around for a long time.

a quick search yielded a wiki article stating the method being used for sewers since at 1875.

https://en.wikipedia.org/wiki/Smoke_testing_(mechanical)#cit...

edit: format

jasonladuke03112• 5 years ago

If companies truly care about diversity of thought as they say they do, there is a massive untapped group who really bring fresh perspectives: older career-changers.

I might be biased as I belong to that group, but I have met some fantastic people from that group.

cvhashim• 5 years ago

I had a tech lead who was once a chef before he switched careers into tech.

0des• 5 years ago

Honestly who hasn't ended a day of cloud work tired, sweating, and covered in shit?

sly010• 5 years ago

Inspiring story if you don't already work "in cloud" but as someone with a decade of experience, it somehow has an opposite effect on me. This story highlights how un-glamorous our job can be: tracking down (memory) leaks, fixing (bit) rotten hardware and obsessing over (code) smells, etc. It makes me want to quit.

eps3• 5 years ago

tl;dr - It's a promo post for a book (at 50% off no less) and its author.

The direct link to the greatest resume on question is this - https://dsresume.com

riffic• 5 years ago

you know the book itself is highly overpriced. It'd be much more worthwhile at the $5 to $10 price point.

someone who just bought a copy to skim through.

JBlue422• 5 years ago

Agreed. It's 133 pages. Content is good for those like myself trying to answer "Where to start" with cloud stuff. Still cheaper than LinuxAcademy/ACloudGuru. If it leads to a six-figure career, a $24 investment is worth it I guess.

nicwolff• 5 years ago

Between "Amazon Web Services" and "Plumbing" he lists "Backflow Prevention and Cross Connection Control Inspector/Tester" and... I'm not quite sure if that's a cloud architecture skill or a plumbing skill!

kerblang• 5 years ago

Just to be clear, running smoke through a sewer line is not a genius move, just standard practice: https://www.youtube.com/watch?v=2IpLABJw2KU

But certainly finding problems in old systems is a valuable skill, and it requires a willingness to do dirty work that many folks turn their nose up at, so to speak.

The greatest resume I've ever seen

Related Stories