>However, there is a certain level everyone should know Sadly that's still debated and you can only get piecemeal ideas from blogs and job postings. There's n

>However, there is a certain level everyone should know Sadly that's still debated and you can only get piecemeal ideas from blogs and job postings. There's no central authority to approve developer skill levels that says "these skills every programmer should know before joining the profession - after that, it's up to the specific job" and then it's legally enforced via certifications and official exams. Right now, it's up to specific jobs and blogs and you have to figure that out. It's ambiguous and that frustrates people who like exact and measurable goals when learning things. I know it seems like one blog isn't a big deal, but I've read many blogs that add things like "10 things every programmer should know" and this language just never ends. If you took a union set of all the things from every "things programmer should know" article, you'd be studying for about 6-8 years before you got a junior position. >For example, if a successful login generates a session token and it collides with another token, you could reject the login and have the user try again Eh, don't even go back to the user. Collisions should be a rare occurrence that you can make a second call to the token generator and just replace the bad one. If you get common collisions, you need a better token generator.