mtdvio / every-programmer-should-know Goto Github PK

Histories make men wise.

"Ten Rules for Negotiating a Job Offer" and "How To Interview As a Developer Candidate" are dead.

VanceAI Image Enhancer provides one-click AI solution to improve image quality online.
VanceAI Photo Restorer can help restore old photos 100% automatically by using AI photo restoration technology.

I think that will be a nice topic to add to the list. Making your own compiler really helps you understanding how they work.

Ambos os links estão funcionando para mim. Além disso, o projeto não parece morto para mim, pois várias solicitações de pull foram aceitas (ou recusadas) nos últimos meses: https://github.com/mtdvio/every-programmer-should-know/pulls?q=is% 3Abr+is%3Fechado.
herbert

Hi there,

I think that the System Design: A Primer repository is really cool and I think it's a nice addition to your list.

Cheers,
Ahmad

cancel

Who the hell is Layman? A layman, in this context, is a person without professional or specialized knowledge in a particular subject. It's not a proper noun, for crying out loud.

The video hosted on Vimeo "Inventing on principle" redirects to Vimeo 404

It seems the target page has moved.

Your project is pretty decent, but some addition to it would make it even better. Such as, If you add the Code of Conduct to the root branch and also add a Contribution guideline, then that would make the project more engaging.

If you want, then I can submit a PR including the Code of Conduct. In that case, I need the contact address (email) to enlist that to the Code of Conduct file.

How about adding abstract analogies programmers can practice solving like the Dining Philosophers' for concurrency, etc?

https://arachnoid.com/
There are many fantastic tutorials on it.

It's a free peer to peer platform to help prepare you for technical interviews. Check out pramp.com

Numbers

• Falsehoods Programmers Believe About Phone Numbers

Phonenumbers are not numbers (see the referenced link):

Falsehoods Programmers Believe About Phone Numbers

...
17. Phone numbers contain only digits
In Israel, certain advertising numbers start with a *. In New Zealand, non-urgent traffic incidents can be reported by calling *555 from a mobile phone.
24. Phone numbers are numbers
Never try to store phone numbers as an int or any other kind of numeric data type. You can't do arithmetic on them, and while 007, 07 and 7 are the same number they are not necessarily the same phone number - in some countries a leading 0 is significant and forms part of the number itself (see A leading zero in numbers formatted for domestic usage can always be discarded when dialing from abroad). Moreover, a phone number may contain other diallable characters (see Phone numbers contain only digits) or an extension portion, dialled after waiting for a tone.

Also, not mentioned in the above link, a phonenumber like 1-800 PIZZA (name dialing / phoneword) is valid (translates to 1-800 74992)

Programming guidelines are useful to every programmers both pro and novice

The link Inventing on Principle in the UX/Usability section is broken.

Expected behaviour:
The link is not broken and I can find the resource.

the line in contributing.md:

This is why we strive to having less, but most valuable resources in the list.

should grammatically be:

This is why we strive to having less, but more valuable resources in the list.

or better yet

We strive to have a smaller list of more valuable resources, quality over quantity.

SEO

📄 What Every Programmer Should Know About SEO

There is a dead link named "Some notes about time" under Section "Time".

You may have forgot:

https://www.mjt.me.uk/posts/falsehoods-programmers-believe-about-addresses/

Hello @mr-mig,

This Repo is a good idea! Congrulations!

I have a comment, why don't we a self-conteined Repo? Without links. That mean that instead have link to external web page, we should have information inside the repo.

I could help with Spanish translation if you consider it interesting.

Regard!

Suggest adding an internationalization / text section that includes at least this:

https://www.joelonsoftware.com/2003/10/08/the-absolute-minimum-every-software-developer-absolutely-positively-must-know-about-unicode-and-character-sets-no-excuses/

As important thing for programmers to learn is how the data structures used and implemented in the system.
I do want to know why did you leave it from your list? If you have already added them then please inform me where did i missed it

The Link Professor Frisby's Mostly Adequate Guide to Functional Programming in the Practices section is broken.

Expected behaviour:
The link is not broken and I can find the resource.

Maybe this is the correct link: https://mostly-adequate.gitbook.io/mostly-adequate-guide/

Hi,

Thank you for your project.

I am doing a similar project since some months. It is not that big like yours, but maybe you want to have a look. I am curious and looking for feedback:

https://github.com/guettli/programming-guidelines/

Books, courses, visualizations - everything will do.

• Refactoring
• Debugging
• Design

https://github.com/mr-mig/every-programmer-should-know/blob/master/slides.com/mr-mig/se101

Also, there's a typo in Architecture.

Thanks.

Ideally, something referencing current and historical methodologies:

• Kanban
• Lean
• Scrum
• RUP
• V-Model
• XP
  etc

I think it'd be awesome if we had a big mindmap to organize all the topics and subtopics.