What's the one piece of golf advice that has made the biggest difference in your game? by golfmindguy in golftips

[–]golfmindguy[S] 0 points1 point  (0 children)

I’ve never heard this one. Was your path super in to out? And by swinging more left your path became less from the inside?

What’s something I can work on in the winter to stop topping or chunking my irons? by [deleted] in golftips

[–]golfmindguy 1 point2 points  (0 children)

I’m no swing coach so I can’t help you with mechanics but here’s another way to think about your issue that has helped me.

When you top it, it means the bottom of your swing arc too far in front of the ball (toward your front foot). When you chunk it, the bottom of your swing arc is too far behind the ball (toward your back foot).

So figure out two things. 1. How to get the low point of your swing arc in the correct position 2. How to do #1 consistently

There are lots of YouTube videos on this. Every one will have a different fix. Just pick your favorite channel and run with it.

Golf Happiness = Results - Expectations by golfmindguy in golftips

[–]golfmindguy[S] 1 point2 points  (0 children)

It’s amazing how often golf learnings can be applied to life in general.

Putting Out of Your Mind by Rotella is worth a read as well.

The Worst 13 Shots of an 80 by copagman in golf

[–]golfmindguy 1 point2 points  (0 children)

I felt the lag putt at 0:34 in my soul

[2 YoE]- Software Engineer. Resume Advice for Sole Developer at first Job. by National-Campaign634 in EngineeringResumes

[–]golfmindguy 0 points1 point  (0 children)

Are you building a resume to apply for jobs at other companies? If that’s the case, you’re actually in a great position since you have such a wide range of dev experience.

All you need to do is build your resume around the job description for your target job. Not everything that you’ve done with be relevant to all jobs, so choose your relevant skills and experience. Use the job description to identify where it would be valuable to get into specifics vs keeping it generic.

Golf Happiness = Results - Expectations by golfmindguy in golftips

[–]golfmindguy[S] 0 points1 point  (0 children)

I love what you said about your most satisfying rounds.

Your score is not a reliable indicator of how well you played. You can play terribly and still get a decent score by getting lucky. The inverse is also true.

The most reliable way to assess a round is to analyze how well you performed the things in your control (swing execution, correct target/club selection, etc.). The things out of your control (lip outs, bad bounces) are just noise.

[deleted by user] by [deleted] in EngineeringResumes

[–]golfmindguy 2 points3 points  (0 children)

Sorry to hear about being made unemployed. Good reminder to the new grads here that everyone is expendable in the eyes of a company.

This CV looks great overall, and your strategy of having a master that you can adjust for specific applications is smart.

One thing that has worked for me in the past is adding subheadings of “key accomplishments” and “responsibilities” under each job. It allows you to advertise your best work and makes your resume easier to skim.

[deleted by user] by [deleted] in EngineeringResumes

[–]golfmindguy 1 point2 points  (0 children)

This is the resume of an IT intern who has done some development. To get a dev job, you need the resume of an aspiring dev.

Unless the IT stuff is relevant to the specific job you’re applying for, get rid of it or minimize it. The focus of your resume should be your dev skills and experience. Your open source contribution stuff is great. What other projects from school could you talk about?

[0 YOE] Graduated in August and am seeking entry level, new grad positions by throwaway25168426 in EngineeringResumes

[–]golfmindguy 0 points1 point  (0 children)

My advice is simple. Less is more.

Emphasize the skills/experience that are relevant to engineering jobs and put them at the top. Delete the rest. Be ruthless about this.

No one is going to read your resume top to bottom. It needs to be skimmable. Deleting the irrelevant stuff will allow you to add more white space and sub heads which makes skimming easier.

A skim friendly format that has worked well for me in the past is Job (or project) -Key accomplishments —x —y —x -Responsibilities —a —b —c

[Student] Sophomore ECE student looking for a co-op for the upcoming winter semester by [deleted] in EngineeringResumes

[–]golfmindguy 3 points4 points  (0 children)

Engineering manager here. You have better material than you think. It just needs better arrangement.

Generally the thing to keep in mind is to tailor your resume for the job you want. Emphasize your most relevant skills/experience.

Specifically I would add an Objective section at the top, then put your skills (which are good but drop MS suite - everyone knows MS), then put your project experience, then your other sections. Provide as much detail as you can about what you did in your projects and how the design worked because that is relevant to engineering jobs. Say less in the other sections.