5 ms·
I think it's more along the lines that most new technology is not fundamentally different from the old solutions. Like how different is HMVC from PAC for exampl
by keithnoizu 8y ago
I think it's more along the lines that most new technology is not fundamentally different from the old solutions. Like how different is HMVC from PAC for example. How different are cool language x's Mixins from Lisp or C#. How different really are channels and message passing in golang compared to erlang.
If a new technology is good or seems like it has potential I dig into it, and due to experience I can generally pick up something to the point of productivity in a day or two that takes junior developers weeks or months to reach. Or at a minimum know enough to figure out how to trouble shoot blocking bugs others can't solve by knowing where to look for solutions and what those solutions might entail. So to an extent I keep up to date in that I read the value propositions and reviews on new technologies so I know when they might be an appropriate tool in my toolbox to tackle some solution or other, on the flip side i'm not in a rush to pick up every flavor of the week framework or library that is more than likely to vanish with out a trace in 3-4 years.
Meanwhile outside of a persistent google recruiter whose been asking to do an onsite for the last year I've gotten dear john'd for something like 3 roles in the last month including one where i'm personal friends with the SVP of engineering. Is it missing keywords on my resume, my age, my career path, education, wth knows but unless the market has tanked it strongly differs from my experience a few years prior.
https://www.dropbox.com/s/haod1gpfjd723lg/Keith-Brings-Resume%20-%20redacted.doc?dl=0 https://www.dropbox.com/s/haod1gpfjd723lg/Keith-Brings-Resum...
- FutureSpec 8y agoI am at lunch and on mobile so I can't get too detailed, but, with respect, I see a number of errors on your resume. You are simultaneously being too broad in your objective and too detailed in the body. It's not telling a coherent, targeted story. You can leave off "references available upon request" because that's assumed. You can just list your school instead of that you only got an associates degree. I would if I were you find a good recruiter and ask them how it reads. Make it more focused and scannable. I put a lot of work into my resume and personal branding on LinkedIn and it pays huge dividends.
- keithnoizu 8y agoappreciated. I haven't polished the thing really in years its a bit rough.
- keithnoizu 8y agoWhat steps do you take for personal branding. I'm really bad with this networking, self selling stuff.
- scarface74 8y agoYour resume reeks of someone who lacks focus. 1. Objectives on resumes are useless fluff. Yours doesn’t add anything useful. It’s so vague, I couldn’t even tell what type of job you are looking for. Project management? Test? Software Development? 2. Your whole summary of skills sections is word soup. I would completely ignore it. Anyone can list technologies they touched once. It’s too unfocused. In your experience section list how you actually used those technologies. Why put you know how to use source control? That’s like listing you know how to type. Why list 8 different languages? Could you handle a deep technical dive in all eight? 3. In your work experience section, you listed your accomplishments, but I have no idea what technologies you used to accomplish anything. You didn’t list the languages you used in any of your jobs since 2007. I wouldn’t call you in for an in person or a phone screen based on your resume. You claim that you can pick up a language in a day or two but I can’t tell from your resume where you feel technically in any specific area. Again, it looks like you think because you can figure out the syntax of a language you’ve avoided learning the ecosystem, the tooling, the frameworks etc. You can ignore picking up popular frameworks but you won’t be competitive with people who have stayed up to date. If you came into an interview saying that you could advise on a technology based on “what you read” and you said you decided not to actually put it into practice, that would be a red flag. I’ve been working for 20 years. I at one point had an encyclopedic knowledge of C and C++, that’s nowhere on my resume, neither is VB6, Perl, or PHP. I don’t want a job in any of those languages and I don’t want to discuss them. My resume for the last 8 years has been entirely focused on telling the story I want to tell. I’m a backend C# developer/architect with some front end Javascript experience. Slowly it’s been morphing into an architect who specializes in “cloud native solutions” with AWS and I’ve added Python and Node and hopefully will be adding the $cool_kids front end stack over the next year or two.
- keithnoizu 8y agoFair feed back. The Summary of Skills is mostly a Keyword hack for passive job hunting I can move it around. I can deep dive into Elixir, Embedded C, C/C++, Java, C#, and PHP. I've used all of these on the job excluding perl, python and ruby in the last 5 years, and python and ruby i've used on side projects or for tutoring a friend on algorithmic programming for a evangelical role google asked her to do a follow up interview on. This is also not a comprehensive list of every language I've ever worked in or touched. I don't list Lisp, F#, Haskell, ActionScript, etc. It probably makes sense to prune out outdated frameworks. And I should probably be updating this with some of the more recent frameworks i've worked with. But the thing is I'm bright, top 1% of the top 1% IQ, inability to write a compelling resume aside. I can pick up frameworks like candy, I read the manual. Further when I want to figure out how to do something that's not initially obvious or covered in the documentation I just read the source code or look it up, which is what everyone does but I do it better. That 2-3 day number includes getting a handle on libraries and frameworks being used on the project. I can pickup just syntax in the 10-90 minutes it takes to glance over existing code and documentation for most languages. For existing code I can usually follow the flow on first read with out knowing the language in advance. I learned C/C++ when I was 14 from reading intermediate level game programming books and reverse engineering it to figure out what the constructs do since there was no internet or other books handy, and the skill stuck with me. So how do I stress that flexibility on my resume, or tell that story with out coming off as braggadocious? P.s. do you mind if I ping you with a modified version in a few days that takes into account your suggestions?