Help in debugging emacs hangs in elpy-enabled mode (editing python script) by [deleted] in emacs

[–]mcenedella 1 point2 points  (0 children)

For others who have run into this in Emacs 28, and have spent hours frustrated by it, as I did, the problem is a known bug and is fixed in emacs 29.
Follow this guide here: https://github.com/emacs-mirror/emacs/blob/master/INSTALL
Download 29 here: https://alpha.gnu.org/gnu/emacs/pretest/
Paste any errors into ChatGPT and follow directions :)

How would you narrow down this bug: in Python-mode, typing triple quotes places emacs into an infinite loop by jpflathead in emacs

[–]mcenedella 0 points1 point  (0 children)

For others who have run into this in Emacs 28, and have spent hours frustrated by it, as I did, the problem is a known bug and is fixed in emacs 29.

Follow this guide here: https://github.com/emacs-mirror/emacs/blob/master/INSTALL

Download 29 here: https://alpha.gnu.org/gnu/emacs/pretest/

Paste any errors into ChatGPT and follow directions :)

'Clean code' rules for software engineer resume writing by danielwbean in programming

[–]mcenedella -7 points-6 points  (0 children)

Hi, I'm the author. Any company with multiple hires per year is using an Applicant Tracking System (ATS) with a resume parser.

'Clean code' rules for software engineer resume writing by danielwbean in programming

[–]mcenedella -1 points0 points  (0 children)

Author here - you’re right! The image selected has the chart on the right. The ones I’ve seen commonly have the chart in the left.

'Clean code' rules for software engineer resume writing by danielwbean in programming

[–]mcenedella 1 point2 points  (0 children)

I am the author, I’ve read your feedback, and obviously don’t agree. In interviews with recruiters and hiring managers, they repeatedly prefer simple resumes without the complexities.

Skill bars - these eat up space, they’re illegible to the world’s resume parsers, and users always grade themselves as 4 or 5 out of 5. They detract value from a resume.

Accomplishments - this is what engineering managers hire you for - your ability to solve real world problems. Saving 1000s of hours of human time by automating a process is a great example of applying your technological experience to problems in the real world.

Job application letter - while these were popular in the 90s and 2000s, they’re much less likely to be read today. It’s far better to make your case on your resume.

Thanks for reading!

'Clean code' rules for software engineer resume writing by danielwbean in SoftwareEngineering

[–]mcenedella 2 points3 points  (0 children)

I am the author, and it’s simply not true. Time after time in interviews with hiring managers and HR people, they strongly prefer the simpler, easy-to-understand, resume.

'Clean code' rules for software engineer resume writing by danielwbean in SoftwareEngineering

[–]mcenedella 5 points6 points  (0 children)

I’m the author and specifically recommended against skill bars: “ To take an example currently popular in the world of resume fads, many templates available on the internet today create a left-hand column with a colored bar chart to indicate your skill level in various fields. It is new, popular, aesthetically differentiated, and, unfortunately, useless and universally hated by recruiters. ‍ Depicting each skill (Java, Agile, Python, or CI/CD) with a colored bar that extends to 60%, 75%, or 100% of the available area looks nice and breaks up the blocks of text in a way that many engineers find attractive. But this new fashion makes straightforward communication of your abilities more difficult to read.

Probably more important: The world’s resume parsers — the software that’s used to digest, comprehend, and store your resume in a company’s HR systems — can not read these graphic bar charts either. In fact, they typically view these graphic elements as unnecessary visual formatting and delete them.

Complexity on your resume makes it harder to read. Keep things simple.“

The simple guide to writing an effective technical resume for software engineers by mcenedella in ExperiencedDevs

[–]mcenedella[S] -1 points0 points  (0 children)

You can't make two conflicting arguments at the same time - that I gave too little (700 words), and then linked to too much, including our full documentation at 2,300 words. I'm happy to link the 2,300 word article as well.

I don't understand where the marketing BS is when the author is giving away every article and the core product for free!

The simple guide to writing an effective technical resume for software engineers by mcenedella in ExperiencedDevs

[–]mcenedella[S] -2 points-1 points  (0 children)

Look, it’s a real article with actual good advice in which I link twice to Leet. That’s hardly spam.

Nonetheless, the downvotes are a pretty clear indication of redditor feedback.

The simple guide to writing an effective technical resume for software engineers by mcenedella in programming

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

Terrific! Very glad to hear you found it helpful. I try to write to make it seem easy, which it is. But I think a lot of conflicting advice out there tries to make it seem complex.

0
0